[cisco-voip] ringback issues
Ryan Ratliff
rratliff at cisco.com
Wed Jan 6 09:40:57 EST 2010
Does your H.323 gateway have access to annunciator resources in CUCM? From the signaling something wants to play ringback in-band (either the gw or CUCM) and for CUCM to do it then it will need to use an annunciator.
You can also play with the CUCM service parameter "Send H225 User Info Message".
-Ryan
On Jan 6, 2010, at 9:11 AM, Leslie Meade wrote:
That is correct only from the PSTN to CUCM, and to the same number. (but it can happen to any)
Works all the time with our carrier and their cell phones, but it is very hit and miss with anyone else
Also I am a he :)
-----Original Message-----
From: Peter Slow [mailto:peter.slow at gmail.com]
Sent: Wednesday, January 06, 2010 12:23 AM
To: Mike Thompson
Cc: Ryan Ratliff; Leslie Meade; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] ringback issues
I beleive leslie is talkign about the other direction - shes not
hearing ringback on calls FROM the PSTN TO the CUCM. the Q.931 setup
messages were inbound.
Leslie, is that correct?
If so, this most likelyhas nothing to do with RTP and is a pure
signaling issue. the only other thing it might be is failure to
provide inband ringback after the call has gone connected and then
been transferred, but now im just making things up.
Leslie, when you say hit/miss from one carrier, are the calls you're
testing all to the same number on the CUCM?
-Peter
On Tue, Jan 5, 2010 at 12:43 PM, Mike Thompson <mthompson729 at gmail.com> wrote:
> This is all but a 'recommended default' command as it can also impact how
> calls go through to 911.
>
>
>
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
> Sent: Tuesday, January 05, 2010 9:50 AM
> To: Leslie Meade
> Cc: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] ringback issues
>
>
>
> Do you have 'voice rtp send-recv' applied on the router? This is a global
> command and necessary for the router to cut audio through early, which you
> are trying to do.
>
>
>
> -Ryan
>
>
>
> On Jan 4, 2010, at 9:01 PM, Leslie Meade wrote:
>
> PSTN calls are not getting ring back, sometimes it works. I have gone
> through cisco reading doc's and all they say to put progress and tone
> ringbacks, but I still have intermittent issues
>
> I have a H323 gateway with two CallManager clusters. The capture all dial
> peer goes to one and specific numbers to the other. I have no issues with
> calls going to the default VOIP Peer
>
> Calls from one carrier (our provider) always get a ring back , but calls
> from others are a hit and miss.
>
> What debugs can I run to tell me for sure it is a carrier issue and not me,
> or the other way around
>
>
>
> My voip dial peer for example is
>
>
>
> dial-peer voice 5076 voip
>
> tone ringback alert-no-PI
>
> destination-pattern 5076
>
> progress_ind setup enable 3
>
> session target ipv4:172.16.1.20
>
> dtmf-relay h245-alphanumeric
>
> codec g711ulaw
>
> The CallManager server has the flag set for progress as false
>
> <image001.jpg>
>
> debug of q931 with no ringback
>
>
>
> 2224938: *Jan 5 01:25:20.097 UTC: ISDN Se0/0/1:23 Q931: RX <- SETUP pd = 8
> callref = 0x60CD
>
> Bearer Capability i = 0x8090A2
>
> Standard = CCITT
>
> Transfer Capability = Speech
>
> Transfer Mode = Circuit
>
> Transfer Rate = 64 kbit/s
>
> Channel ID i = 0xA98381
>
> Exclusive, Channel 1
>
> Progress Ind i = 0x8283 - Origination address is non-ISDN
>
> Calling Party Number i = 0x2183, '7787726009'
>
> Plan:ISDN, Type:National
>
> Called Party Number i = 0x80, '5076'
>
> Plan:Unknown, Type:Unknown
>
> 2224939: *Jan 5 01:25:20.117 UTC: ISDN Se0/0/1:23 Q931: TX -> CALL_PROC pd
> = 8 callref = 0xE0CD
>
> Channel ID i = 0xA98381
>
> Exclusive, Channel 1
>
> 2224940: *Jan 5 01:25:20.233 UTC: ISDN Se0/0/1:23 Q931: TX -> ALERTING pd =
> 8 callref = 0xE0CD
>
> Progress Ind i = 0x8188 - In-band info or appropriate now available
>
> Voice-GW-01#
>
> 2224941: *Jan 5 01:25:25.333 UTC: ISDN Se0/0/1:23 Q931: RX <- DISCONNECT pd
> = 8 callref = 0x60CD
>
> Cause i = 0x8090 - Normal call clearing
>
> 2224942: *Jan 5 01:25:25.337 UTC: ISDN Se0/0/1:23 Q931: TX -> RELEASE pd =
> 8 callref = 0xE0CD
>
> 2224943: *Jan 5 01:25:25.349 UTC: ISDN Se0/0/1:23 Q931: RX <- RELEASE_COMP
> pd = 8 callref = 0x60CD
>
>
>
> With a ring back
>
>
>
> 2224964: *Jan 5 01:27:07.801 UTC: ISDN Se0/0/1:23 Q931: RX <- SETUP pd = 8
> callref = 0x60D3
>
> Bearer Capability i = 0x8090A2
>
> Standard = CCITT
>
> Transfer Capability = Speech
>
> Transfer Mode = Circuit
>
> Transfer Rate = 64 kbit/s
>
> Channel ID i = 0xA98381
>
> Exclusive, Channel 1
>
> Calling Party Number i = 0x2183, '7789910549'
>
> Plan:ISDN, Type:National
>
> Called Party Number i = 0x80, '5076'
>
> Plan:Unknown, Type:Unknown
>
> 2224965: *Jan 5 01:27:07.817 UTC: ISDN Se0/0/1:23 Q931: TX -> CALL_PROC pd
> = 8 callref = 0xE0D3
>
> Channel ID i = 0xA98381
>
> Exclusive, Channel 1
>
> Voice-GW-01#
>
> 2224966: *Jan 5 01:27:07.933 UTC: ISDN Se0/0/1:23 Q931: TX -> ALERTING pd =
> 8 callref = 0xE0D3
>
> Progress Ind i = 0x8188 - In-band info or appropriate now available
>
> 2224967: *Jan 5 01:27:18.817 UTC: ISDN Se0/0/1:23 Q931: TX -> CONNECT pd =
> 8 callref = 0xE0D3
>
> 2224968: *Jan 5 01:27:18.837 UTC: ISDN Se0/0/1:23 Q931: RX <- CONNECT_ACK
> pd = 8 callref = 0x60D3
>
> 2224970: *Jan 5 01:27:19.661 UTC: ISDN Se0/0/1:23 Q931: RX <- DISCONNECT pd
> = 8 callref = 0x60D3
>
> 2224972: *Jan 5 01:27:19.661 UTC: ISDN Se0/0/1:23 Q931: TX -> RELEASE pd =
> 8 callref = 0xE0D3
>
> 2224973: *Jan 5 01:27:19.677 UTC: ISDN Se0/0/1:23 Q931: RX <- RELEASE_COMP
> pd = 8 callref = 0x60D3
>
>
>
>
>
> Leslie
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
More information about the cisco-voip
mailing list