Environment- Standalone controller, AP and Lync server and Lync SDN version 2.1
Answer-
There won't be any call quality issues when a Lync call is initiated between the two clients however call records won't be
showing up on the UCC Dashboard and CLI of the controller.
Below logs shows "No active call" message even though there was a successful call between these two clients.
STM logs:
Feb 25 14:30:11 stm[3387]: <503188> <DBUG> |stm| |voice| |vm| vm_update_vc_stat_queue: vc 172.19.46.180, bssid 00:24:6c:37:37:a8, 0 report in list
Feb 25 14:30:11 stm[3387]: <503188> <DBUG> |stm| |voice| valid_report: vc 172.19.46.180, No active call.. <<<< -------------------------
Feb 25 14:30:11 stm[3387]: <503188> <DBUG> |stm| |voice| |vm| vm_update_vc_stat_queue: vc 172.19.45.77, bssid 00:24:6c:37:37:a8, 0 report in list
Feb 25 14:30:11 stm[3387]: <503188> <DBUG> |stm| |voice| valid_report: vc 172.19.45.77, No active call.. <<<<< -------------------------
Feb 25 14:33:11 stm[3387]: <503188> <DBUG> |stm| |voice| |vm| vm_update_vc_stat_queue: vc 172.19.45.77, bssid 00:24:6c:37:37:a8, 0 report in list
Feb 25 14:33:11 stm[3387]: <503188> <DBUG> |stm| |voice| valid_report: vc 172.19.45.77, No active call.. <<<<< -------------------------
Feb 25 14:33:21 stm[3387]: <503188> <DBUG> |stm| |voice| VM: get_alg_status:1572 LYNC INFO: ALG status: 1
Feb 25 14:33:21 stm[3387]: <503188> <DBUG> |stm| |voice| VM: get_alg_status:1573 LYNC INFO: Web Lync Port(Lync SDN API) status: 1
Feb 25 14:33:21 stm[3387]: <503188> <DBUG> |stm| |voice| VM: get_alg_status:1572 LYNC INFO: ALG status: 1
Feb 25 14:33:21 stm[3387]: <503188> <DBUG> |stm| |voice| VM: get_alg_status:1573 LYNC INFO: Web Lync Port(Lync SDN API) status: 1
In datapath session table the voice traffic will be prioritized.
ToS bit is set to 46 as per the ACLs been configured on the user-role.
Flags: F - fast age, C - client, H - high prio, P - set prio, T - set ToS, V - VOIP
Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age Destination TAge Packets Bytes Flags
--------------- --------------- ---- ----- ----- ----- ---- --- --- ----------- ---- --------- --------- ---------------
23.74.12.8 172.19.46.180 6 443 54097 0/0 0 24 0 tunnel 18 2 3 120 F
172.19.46.180 172.19.45.77 17 48027 48005 0/0 0 46 0 tunnel 18 ae 141 93830 FHTCV <<<<<----------------------
172.19.128.1 172.19.46.180 17 53 53102 0/0 0 24 0 tunnel 18 2 1 430 FI
172.19.46.180 172.19.131.5 6 54001 5061 0/0 6 24 0 tunnel 18 439 88 29278 TCIG
172.19.46.180 172.19.80.104 6 54023 4282 0/0 0 24 6 tunnel 18 42f 42 4409 TC
172.19.46.180 172.19.115.25 6 53993 65501 0/0 0 24 17 tunnel 18 43b 9 1628 TC
172.19.45.77 172.19.46.180 17 48004 48026 0/0 5 40 0 tunnel 18 2 2 197 FTCIE
172.19.63.251 172.19.46.180 6 5061 53985 0/0 6 24 0 tunnel 18 43c 53 13282 I
172.19.246.103 172.19.46.180 6 80 54096 0/0 0 24 1 tunnel 18 11 0 0 F
172.19.80.104 172.19.46.180 6 4282 54023 0/0 0 24 6 tunnel 18 42f 37 5464
172.19.46.180 23.74.12.8 6 54097 443 0/0 0 24 0 tunnel 18 2 3 152 YTC
172.19.46.180 172.19.115.25 6 53999 65500 0/0 0 24 0 tunnel 18 43a 21 3106 TC
172.19.115.25 172.19.46.180 6 65500 53999 0/0 0 24 0 tunnel 18 43a 26 2644
172.19.46.180 172.19.128.1 17 53102 53 0/0 0 24 0 tunnel 18 2 1 71 FTCI
172.19.46.180 172.19.45.77 17 48026 48004 0/0 0 40 0 tunnel 18 2 3 253 FIE
172.19.131.5 172.19.46.180 6 5061 54001 0/0 6 24 0 tunnel 18 439 116 99530 I
172.19.115.25 172.19.46.180 6 65500 53997 0/0 0 24 2 tunnel 18 43b 190 71852
172.19.46.180 172.19.246.103 6 54096 80 0/0 0 24 1 tunnel 18 11 0 0 FTC
172.19.46.180 172.19.115.25 6 53997 65500 0/0 0 24 2 tunnel 18 43b 87 35260 TC
172.19.45.77 172.19.46.180 17 48005 48027 0/0 5 46 1 tunnel 18 ae 140 97903 FHTV <<<<<<-----------------------
172.19.115.25 172.19.46.180 6 65501 53993 0/0 0 24 17 tunnel 18 43b 10 1268
172.19.46.180 172.19.63.251 6 53985 5061 0/0 6 24 0 tunnel 18 43c 60 12420 TCIG
(Aruba) #show ucc call-info cdrs
CDRS:
-----
CDR ID UCC Call ID Client IP Client MAC Client Name ALG Dir Called to Dur(sec) Orig Time Status Reason Call Type UCC Score Quality Client Health MOS
------ ----------- --------- ---------- ----------- --- --- --------- -------- --------- ------ ------ --------- --------- ------- ------------- ---
(Aruba) #show ucc call-info cdrs detail
CDRS-Detail:
------------
CDR ID UCC Call ID AP Name Re-Assoc Src Port Dest Port Codec UCC Score Quality Delay(msec) Jitter(msec) Packet Loss(%) DSCP Orig DSCP WMM-AC Orig WMM-AC SNR Avg Tx Rate(Mbps) Tx Drop(%) Tx Retry(%) Avg Rx Rate(Mbps) Rx Retry(%)
------ ----------- ------- -------- -------- --------- ----- --------- ------- ----------- ------------ -------------- ---- --------- ------ ----------- --- ----------------- ---------- ----------- ----------------- -----------
(Aruba) #
Lync SDN 2.1 uses Lync SDN XML Schema version C and ArubaOS 6.4.2.3 only supports the Microsoft Lync SDN 2.0 which uses XML Schema version A.
Due to interpretation issue Lync call records are not showing up on the UCC Dashboard and CLI of the controller.
AnswerLT- There won't be any call quality issues when a Lync call is initiated between the two clients however call records won't be
showing up on the UCC Dashboard and CLI of the controller.
Below logs shows "No active call" message even though there was a successful call between these two clients.
STM logs:
Feb 25 14:30:11 stm[3387]: <503188> <DBUG> |stm| |voice| |vm| vm_update_vc_stat_queue: vc 172.19.46.180, bssid 00:24:6c:37:37:a8, 0 report in list
Feb 25 14:30:11 stm[3387]: <503188> <DBUG> |stm| |voice| valid_report: vc 172.19.46.180, No active call.. <<<< -------------------------
Feb 25 14:30:11 stm[3387]: <503188> <DBUG> |stm| |voice| |vm| vm_update_vc_stat_queue: vc 172.19.45.77, bssid 00:24:6c:37:37:a8, 0 report in list
Feb 25 14:30:11 stm[3387]: <503188> <DBUG> |stm| |voice| valid_report: vc 172.19.45.77, No active call.. <<<<< -------------------------
Feb 25 14:33:11 stm[3387]: <503188> <DBUG> |stm| |voice| |vm| vm_update_vc_stat_queue: vc 172.19.45.77, bssid 00:24:6c:37:37:a8, 0 report in list
Feb 25 14:33:11 stm[3387]: <503188> <DBUG> |stm| |voice| valid_report: vc 172.19.45.77, No active call.. <<<<< -------------------------
Feb 25 14:33:21 stm[3387]: <503188> <DBUG> |stm| |voice| VM: get_alg_status:1572 LYNC INFO: ALG status: 1
Feb 25 14:33:21 stm[3387]: <503188> <DBUG> |stm| |voice| VM: get_alg_status:1573 LYNC INFO: Web Lync Port(Lync SDN API) status: 1
Feb 25 14:33:21 stm[3387]: <503188> <DBUG> |stm| |voice| VM: get_alg_status:1572 LYNC INFO: ALG status: 1
Feb 25 14:33:21 stm[3387]: <503188> <DBUG> |stm| |voice| VM: get_alg_status:1573 LYNC INFO: Web Lync Port(Lync SDN API) status: 1
In datapath session table the voice traffic will be prioritized.
ToS bit is set to 46 as per the ACLs been configured on the user-role.
Flags: F - fast age, C - client, H - high prio, P - set prio, T - set ToS, V - VOIP
Source IP Destination IP Prot SPort DPort Cntr Prio ToS Age Destination TAge Packets Bytes Flags
--------------- --------------- ---- ----- ----- ----- ---- --- --- ----------- ---- --------- --------- ---------------
23.74.12.8 172.19.46.180 6 443 54097 0/0 0 24 0 tunnel 18 2 3 120 F
172.19.46.180 172.19.45.77 17 48027 48005 0/0 0 46 0 tunnel 18 ae 141 93830 FHTCV <<<<<----------------------
172.19.128.1 172.19.46.180 17 53 53102 0/0 0 24 0 tunnel 18 2 1 430 FI
172.19.46.180 172.19.131.5 6 54001 5061 0/0 6 24 0 tunnel 18 439 88 29278 TCIG
172.19.46.180 172.19.80.104 6 54023 4282 0/0 0 24 6 tunnel 18 42f 42 4409 TC
172.19.46.180 172.19.115.25 6 53993 65501 0/0 0 24 17 tunnel 18 43b 9 1628 TC
172.19.45.77 172.19.46.180 17 48004 48026 0/0 5 40 0 tunnel 18 2 2 197 FTCIE
172.19.63.251 172.19.46.180 6 5061 53985 0/0 6 24 0 tunnel 18 43c 53 13282 I
172.19.246.103 172.19.46.180 6 80 54096 0/0 0 24 1 tunnel 18 11 0 0 F
172.19.80.104 172.19.46.180 6 4282 54023 0/0 0 24 6 tunnel 18 42f 37 5464
172.19.46.180 23.74.12.8 6 54097 443 0/0 0 24 0 tunnel 18 2 3 152 YTC
172.19.46.180 172.19.115.25 6 53999 65500 0/0 0 24 0 tunnel 18 43a 21 3106 TC
172.19.115.25 172.19.46.180 6 65500 53999 0/0 0 24 0 tunnel 18 43a 26 2644
172.19.46.180 172.19.128.1 17 53102 53 0/0 0 24 0 tunnel 18 2 1 71 FTCI
172.19.46.180 172.19.45.77 17 48026 48004 0/0 0 40 0 tunnel 18 2 3 253 FIE
172.19.131.5 172.19.46.180 6 5061 54001 0/0 6 24 0 tunnel 18 439 116 99530 I
172.19.115.25 172.19.46.180 6 65500 53997 0/0 0 24 2 tunnel 18 43b 190 71852
172.19.46.180 172.19.246.103 6 54096 80 0/0 0 24 1 tunnel 18 11 0 0 FTC
172.19.46.180 172.19.115.25 6 53997 65500 0/0 0 24 2 tunnel 18 43b 87 35260 TC
172.19.45.77 172.19.46.180 17 48005 48027 0/0 5 46 1 tunnel 18 ae 140 97903 FHTV <<<<<<-----------------------
172.19.115.25 172.19.46.180 6 65501 53993 0/0 0 24 17 tunnel 18 43b 10 1268
172.19.46.180 172.19.63.251 6 53985 5061 0/0 6 24 0 tunnel 18 43c 60 12420 TCIG
(Aruba) #show ucc call-info cdrs
CDRS:
-----
CDR ID UCC Call ID Client IP Client MAC Client Name ALG Dir Called to Dur(sec) Orig Time Status Reason Call Type UCC Score Quality Client Health MOS
------ ----------- --------- ---------- ----------- --- --- --------- -------- --------- ------ ------ --------- --------- ------- ------------- ---
(Aruba) #show ucc call-info cdrs detail
CDRS-Detail:
------------
CDR ID UCC Call ID AP Name Re-Assoc Src Port Dest Port Codec UCC Score Quality Delay(msec) Jitter(msec) Packet Loss(%) DSCP Orig DSCP WMM-AC Orig WMM-AC SNR Avg Tx Rate(Mbps) Tx Drop(%) Tx Retry(%) Avg Rx Rate(Mbps) Rx Retry(%)
------ ----------- ------- -------- -------- --------- ----- --------- ------- ----------- ------------ -------------- ---- --------- ------ ----------- --- ----------------- ---------- ----------- ----------------- -----------
(Aruba) #
Lync SDN 2.1 uses Lync SDN XML Schema version C and ArubaOS 6.4.2.3 only supports the Microsoft Lync SDN 2.0 which uses XML Schema version A.
Due to interpretation issue Lync call records are not showing up on the UCC Dashboard and CLI of the controller.