cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1099
Views
0
Helpful
6
Replies

Oneway voice over sip trunk between cisco and Grandstream.

waqas sardar
Level 1
Level 1

Hi Team,

 

Please find the attached logs.

 

One-way voice sip trunk between Cisco (192.168.200.10) and Grandstream 192.168.200.13.

Calling Ext 4003  Called Ext 1125

 

Ext 4003 is registered with grandstream and can hear voice.

 

Thanks

1 Accepted Solution

Accepted Solutions

Oohhh, this is a really old system, correct? Like v8 or something? The files are in a much older format where SDI and SDL are sperate, whereas today, they are all in SDL.

I see the call at 11:06:41.095.

Looks like the grandstream rtp media address will be 192.168.200.13 and the cisco side media address will be 192.168.111.30.

It also looks like the codec of choice is g729, despite grandstream offering better codecs to use.

So the traffic from 192.168.111.30 can reach 192.168.200.13....
And the traffic from 192.168.200.13 cannot reach 192.168.111.30....

I would suspect the routing from grandstream to the cisco side is not complete, and if you have access to the grandstream system, you can try to ping the cisco side and I'd imagine it would fail.

View solution in original post

6 Replies 6

Anthony Holloway
Cisco Employee
Cisco Employee
I didn't see any SIP messages in your log file. Make sure your traces are set to debug level on cucm.

Also, most common scenario for one-way audio is routing. Make sure the endpoints involved in the rtp media path can layer 3 route to each other's advertised ip addresses (shown in the SIP SDP body)

 

 

@Anthony Holloway Previously Attached logs are details logs. I can see the Error below :

 

16:04:37.988 |//SIP/SIPHandler/ccbId=0/scbId=0/getCodecAndFramesFromSDP: -- Error!!!!! Cannot convert SDP pt=2 to CM payload type.|1,100,230,1.1243^192.168.200.13^*
16:04:37.988 |//SIP/SIPHandler/ccbId=0/scbId=0/getCodecAndFramesFromSDP: -- Error!!!!! Cannot convert SDP pt=5 to CM payload type.|1,100,230,1.1243^192.168.200.13^*
16:04:37.988 |//SIP/SIPHandler/ccbId=0/scbId=0/convertStackSDPtoCmSDP: ***SIPSdp=4738 bytes|1,100,230,1.1243^192.168.200.13^*
16:04:37.988 |//SIP/SIPHandler/ccbId=0/scbId=0/_ccsip_api_call_setup_ind: sdppresent? 1 1|1,100,230,1.1243^192.168.200.13^*
16:04:37.988 |//SIP/SIPHandler/ccbId=0/scbId=0/getCalledNumberUri: SIP URL 1125@192.168.200.10:5060|1,100,230,1.1243^192.168.200.13^*
16:04:37.988 |//SIP/SIPHandler/ccbId=0/scbId=0/sendSetupInd: bearerless? 1 1|1,100,230,1.1243^192.168.200.13^*
16:04:37.988 |//SIP/SIPHandler/ccbId=0/scbId=0/parseContactHeader: Incoming Contact=[<sip:4003@192.168.200.13:5060>]|1,100,230,1.1243^192.168.200.13^*
16:04:37.988 |//SIP/SIPD(1,73,4)/ccbId=5711/scbId=0/restart0_SIPSetupInd: mTsp.deviceName[Grandstream-Trunk]|1,100,230,1.1243^192.168.200.13^*

Please attach full cucm sdl logs and include call details, calling, called num and time of call

Please rate all useful posts

@Ayodeji Okanlawon @Anthony Holloway 

 

 

I have attached the details logs including all details. . Please check for troubleshooting..

 

Thanks

Oohhh, this is a really old system, correct? Like v8 or something? The files are in a much older format where SDI and SDL are sperate, whereas today, they are all in SDL.

I see the call at 11:06:41.095.

Looks like the grandstream rtp media address will be 192.168.200.13 and the cisco side media address will be 192.168.111.30.

It also looks like the codec of choice is g729, despite grandstream offering better codecs to use.

So the traffic from 192.168.111.30 can reach 192.168.200.13....
And the traffic from 192.168.200.13 cannot reach 192.168.111.30....

I would suspect the routing from grandstream to the cisco side is not complete, and if you have access to the grandstream system, you can try to ping the cisco side and I'd imagine it would fail.

It was routing issue. Thanks