04-18-2017 03:56 AM - edited 03-17-2019 10:05 AM
Hi Guys,
Please find the attached snaps.
For International calls we are getting Timeout and S4B (skyp for business) is terminating this call.
If we compare the call scenario for local calls we are getting 183 from Cisco after trying, while for International calls we are not getting 183 which cause Mediation server to Timeout the international call.
Please help to troubleshot this option on Cisco side why we are not getting option 183 for international calls?
Thanx
04-18-2017 05:30 AM
Please collect SIP Traces for both the call scenarios.
You can collect same form CUCM or Voice Gateway ( use debug ccsip messages command)
Thanks
Haris
04-23-2017 09:25 PM
04-25-2017 04:47 AM
Hi Guys ,
Anyone can suggests on the issue ?
04-25-2017 05:36 AM
Waqas,
You need to look at the gateway logs. This is not a CUCM issue. CUCM is sending the call to the gateway over the SIP Trunk..The gateway does not send any progress message to cucm and after 9s sfb sends a CANCEL to the CUCM. So there seem to be an issue with your provider but we can only confirm this when we get the "debug ccsip messages" from the gateway
2017/04/19 14:07:49.179|CC|OFFERED|76124098|76124099|4808|900923004873626|900923004873626|CCE_SIPTRUNK|HQ_SIP_Trunk_TO_Gateway
2017/04/19 14:07:49.179|SIPT|76124099|TCP|OUT|10.68.194.5|5060|HQ_SIP_Trunk_TO_Gateway|10.68.195.12|5060|4,100,14,1.15245^*^*|3523840|9904e00-8f7136f5-80030-5c2440a@10.68.194.5|INVITE
2017/04/19 14:07:49.203|SIPT|76124099|TCP|IN|10.68.194.5|5060|HQ_SIP_Trunk_TO_Gateway|10.68.195.12|5060|4,100,14,158.40213^10.68.195.12^*|3523841|9904e00-8f7136f5-80030-5c2440a@10.68.194.5|100 Trying 2017/04/19 14:07:58.585|SIPT|0|TCP|IN|10.68.194.5|5060|CCE_SIPTRUNK|10.67.234.232|35855|4,100,14,381472.3559^10.67.234.232^*|3523867|1738042523342017231620@10.67.234.232|CANCEL
04-25-2017 06:07 AM
Hi Ayodeji ,
Yes true, call is landing on voice gateway.
From cisco phone same international call is working fine, then why its having issue from Skype for business ?
04-25-2017 07:46 AM
The answer is that until you provide the full call logs we cant know.
We need gateway logs..and we can go from there.
04-25-2017 10:03 PM
04-26-2017 03:48 AM
You need to speak to your telco provider and find out why they are not responding to the call.
Here is summary of what is going on.
++ Gateway receives the call from CUCM at ++
INVITE sip:900923004873626@10.68.195.12:5060 SIP/2.0 Via: SIP/2.0/TCP 10.68.194.5:5060;branch=z9hG4bKb0a646c977cef From: <sip:4808@10.68.194.5>;tag=2339400~74a26699-b584-4827-9983-8c6106227deb-76131406 To: <sip:900923004873626@10.68.195.12> Date: Wed, 26 Apr 2017 04:20:03 GMT Call-ID: 9d59a100-90011ff3-aff99-5c2440a@10.68.194.5
++ The gateway sends sends a setup request to your Telco ++
1574031: Apr 26 08:20:03.940: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x1, Calling num 044384808
1574032: Apr 26 08:20:03.940: ISDN Se0/0/0:15 Q931: Sending SETUP callref = 0x274F callID = 0xA45E switch = primary-net5 interface = User
1574033: Apr 26 08:20:03.940: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x274F
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Calling Party Number i = 0x0181, '044384808'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x81, '00923004873626'
Plan:ISDN, Type:Unknown
++ Telco didnt respond to the call and about 9sec after CUCM sends a CANCEL because it receives a CANCEL from Skype ++
1574044: Apr 26 08:20:08.452: ISDN Se0/0/2:15 Q931: TX -> ALERTING pd = 8 callref = 0x9552
1574045: Apr 26 08:20:13.228: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:
Received:
CANCEL sip:900923004873626@10.68.195.12:5060 SIP/2.0
Via: SIP/2.0/TCP 10.68.194.5:5060;branch=z9hG4bKb0a646c977cef
From: <sip:4808@10.68.194.5>;tag=2339400~74a26699-b584-4827-9983-8c6106227deb-76131406
To: <sip:900923004873626@10.68.195.12>
Date: Wed, 26 Apr 2017 04:20:03 GMT
Call-ID: 9d59a100-90011ff3-aff99-5c2440a@10.68.194.5
You can look at the working call from CUCM and verify that you are sending the correct digit to telco for international calls. Compare the working logs and this one and check that the difference is in terms of the digit that is presented
04-26-2017 04:33 AM
Thanks for your finding .
working digit are same in both cases as below.
Bearer Capability i = 0x8090A3
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Calling Party Number i = 0x0181, '044384808'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x81, '00923004873626'
Plan:ISDN, Type:Unknown
1574123: Apr 26 15:30:25.931: ISDN Se0/0/0:15 Q931: RX <- SETUP_ACK pd = 8 callref = 0xAE80
04-26-2017 05:28 AM
Okay in that case call your telco, find out why they are not responding to your setup request. They should be able to point you in the right direction
04-26-2017 11:36 PM
Thanks Ayodeji
04-30-2017 03:27 AM
Hi Ayodeji,
I have received the following reply from service provider. Please advise
""As discussed we can see the calls are getting disconnected because we are getting ‘DISCONNECT’ signal from your end.
Now why your Skype setup is sending DISCONNECT signal before the calls are being connected, that too only for international calls, has to be checked with your internal setup.""
04-30-2017 08:12 AM
Based on my interpretation of the log it appears telco is correct, after sending the call via PRI:
574033: Apr 26 08:20:03.940: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x274F Bearer Capability i = 0x8090A3 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA98381 Exclusive, Channel 1 Calling Party Number i = 0x0181, '044384808' Plan:ISDN, Type:Unknown Called Party Number i = 0x81, '00923004873626' Plan:ISDN, Type:Unknown
we see SIP cancel message:
1574045: Apr 26 08:20:13.228: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg: Received: CANCEL sip:900923004873626@10.68.195.12:5060 SIP/2.0 Via: SIP/2.0/TCP 10.68.194.5:5060;branch=z9hG4bKb0a646c977cef From: <sip:4808@10.68.194.5>;tag=2339400~74a26699-b584-4827-9983-8c6106227deb-76131406
followed by PRI call disconnect:
1574046: Apr 26 08:20:13.240: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x274F Cause i = 0x8090 - Normal call clearing
It appears to be you are sending the call to CUBE as Delayed Offer as I don't see SDP content in the initial INVITE, nor is SDP getting passed back by CUBE in the reply. Can you try Early Offer from Skype to CUCM, and CUCM to CUBE? For comparison does direct call from Cisco device go out as EO vs. DO?
04-30-2017 10:00 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide