cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
368
Views
0
Helpful
4
Replies

SIP Communications Issues (One way audio and Disconnection)

JustForVoice_2
Level 4
Level 4

Hello,

 

I have the following Scenario:

IP Phone >> CUCM>> SIP Trunk >> CUBE >> SIP Service Provider

Making a call from Telco to IP Phone: One way Audio from Telco to IP Phone.

Making a call from IP Phone to Telco: Call disconnect after 19 seconds and no audio. Error code 102.

 

I attached the debug. Could you please help?

 Thanks

 

1 Accepted Solution

Accepted Solutions

Vivek Batra
VIP Alumni
VIP Alumni

For outgoing call from IP phone to Telco, issue is because of incorrect SIP binding in CUBE.

Seems that Telco facing interface is 172.22.32.226.

CUCM facing interface is 10.11.3.11. That is what you would have configured in CUCM as CUBE address. This can be verified from INVITE recieved by CUBE from CUCM;

INVITE sip:00448878978@10.11.3.11:5060 SIP/2.0

Now when CUBE is sending 200 OK to CUCM, it's using different interface viz 10.10.15.5. This might be the reason why CUCM is not responding with ACK (in response of 200 OK) and call is being dropped after couple of seconds (timeout);

o=CiscoSystemsSIP-GW-UserAgent 452 5706 IN IP4 10.10.15.5

Please let us know which is correct interface of CUBE facing CUCM viz 10.11.3.11 or 10.10.15.5? Depends on your requirement, we will bind the inbound dial peer in CUBE with correct interface and your issue should get resolved.

- Vivek

View solution in original post

4 Replies 4

Hi,

For calls to IP Phone

Please share your CUBE config along with the output for show call active voip brief.

For calls from IP Phone

Please share the output of debug ccsip message from CUBE along with calling/called numbers

Vivek Batra
VIP Alumni
VIP Alumni

For outgoing call from IP phone to Telco, issue is because of incorrect SIP binding in CUBE.

Seems that Telco facing interface is 172.22.32.226.

CUCM facing interface is 10.11.3.11. That is what you would have configured in CUCM as CUBE address. This can be verified from INVITE recieved by CUBE from CUCM;

INVITE sip:00448878978@10.11.3.11:5060 SIP/2.0

Now when CUBE is sending 200 OK to CUCM, it's using different interface viz 10.10.15.5. This might be the reason why CUCM is not responding with ACK (in response of 200 OK) and call is being dropped after couple of seconds (timeout);

o=CiscoSystemsSIP-GW-UserAgent 452 5706 IN IP4 10.10.15.5

Please let us know which is correct interface of CUBE facing CUCM viz 10.11.3.11 or 10.10.15.5? Depends on your requirement, we will bind the inbound dial peer in CUBE with correct interface and your issue should get resolved.

- Vivek

For incoming call from Telco to IP phone, all signaling seems fine. I have just a doubt on SIP bind interface again.

For this flow, CUBE is now using 10.10.15.5 interface. Please confirm which interface you want to use between CUCM and CUBE viz 10.10.15.5 or 10.11.3.11?

- Vivek

Thank you :)