[cisco-voip] What could cause a "buzzing" rather than call progress tones?
James Edmondson
biged7600 at gmail.com
Wed Jan 21 10:18:43 EST 2009
I had a smiliar issue awhile back and it ended up being and ios issue.
We heard buzzing instead of ringback. However it was a H323 vgw not
mgcp. What ios are you running?
On 1/21/09, Robert Kulagowski <rkulagow at gmail.com> wrote:
> Over in the U.K., I've got an Adtran Atlas 830 terminating two PRIs from
> BT and sending 2 PRIs to a 2851 VGW running MGCP. CM is 4.1.3. A 3rd
> PRI is generated to a Codian 3241.
>
> Outbound calls are generating a "buzzing" sound rather than actual call
> progress tones (like Ring, busy, etc). I called Adtran tech support and
> we went over the configuration of the Adtran. From the logs, the Adtran
> is just passing ISDN setup messages over the D channel like it's
> supposed to, and the audio path isn't established until the called party
> goes off-hook.
>
> Here's the traces from the Adtran:
>
> |1|3| is the E-1 to the 2851. So here's the Adtran receiving an
> outbound call setup from the 2851 to the PSTN
>
> 13:22:36 lon [ADT]:|1|3|Recd = Sapi:00 C/R:R Tei:00
> 13:22:36 lon [ADT]:|1|3| Ctl:INFO Ns:44 Nr:36
> 13:22:36 lon [ADT]:|1|3| Prot:08 CRL:2 CRV:0017
> 13:22:36 lon [ADT]:|1|3| M - 05 SETUP
> 13:22:36 lon [ADT]:|1|3| IE - A1 SENDING COMPLETE Len=0
> 13:22:36 lon [ADT]:|1|3| IE - 04 BEARER CAPABILITY Len=3
> 13:22:36 lon [ADT]:|1|3| 80 Xfer Cap.:SPEECH
> 13:22:36 lon [ADT]:|1|3| 90 Xfer Rate:64k
> 13:22:36 lon [ADT]:|1|3| A3 Layer 1:G.711 A-Law
> 13:22:36 lon [ADT]:|1|3| IE - 18 CHANNEL ID Len=3
> 13:22:36 lon [ADT]:|1|3| A9 Primary Rate
> 13:22:36 lon [ADT]:|1|3| Intfc ID:IMPLICIT
> 13:22:36 lon [ADT]:|1|3| Pref/Excl:EXCLUSIVE
> 13:22:36 lon [ADT]:|1|3| D-Chan Indicated:NO
> 13:22:36 lon [ADT]:|1|3| Chan. Sel:FOLLOWS
> 13:22:36 lon [ADT]:|1|3| 83 Numb/Map:NUMBER
> 13:22:36 lon [ADT]:|1|3| 9f Channel:31
> 13:22:36 lon [ADT]:|1|3| IE - 6C CALLING PARTY # Len=8
> 13:22:36 lon [ADT]:|1|3| 00 Numb. Type:UNKNOWN
> 13:22:36 lon [ADT]:|1|3| Numb. Plan:UNKNOWN
> 13:22:36 lon [ADT]:|1|3| A1 Presentation:RESTRICTED
> 13:22:36 lon [ADT]:|1|3| Ph.# 504955
> 13:22:36 lon [ADT]:|1|3| IE - 70 CALLED PARTY # Len=14
> 13:22:36 lon [ADT]:|1|3| 80 Numb. Type:UNKNOWN
> 13:22:36 lon [ADT]:|1|3| Numb. Plan:UNKNOWN
> 13:22:36 lon [ADT]:|1|3| Ph.# 0013123963808
> 13:22:36 lon [ADT]:ISDN|1|3|Call to ATLAS:'0013123963808'.
> 13:22:36 lon [ADT]:|1|3|==========
> 13:22:36 lon [ADT]:|1|3|Sent = Sapi:00 C/R:C Tei:00
> 13:22:36 lon [ADT]:|1|3| Ctl:INFO Ns:36 Nr:45
> 13:22:36 lon [ADT]:|1|3| Prot:08 CRL:2 CRV:8017
> 13:22:36 lon [ADT]:|1|3| M - 02 CALL_PROC
> 13:22:36 lon [ADT]:|1|3| IE - 18 CHANNEL ID Len=3
> 13:22:36 lon [ADT]:|1|3| A9 Primary Rate
> 13:22:36 lon [ADT]:|1|3| Intfc ID:IMPLICIT
> 13:22:36 lon [ADT]:|1|3| Pref/Excl:EXCLUSIVE
> 13:22:36 lon [ADT]:|1|3| D-Chan Indicated:NO
> 13:22:36 lon [ADT]:|1|3| Chan. Sel:FOLLOWS
> 13:22:36 lon [ADT]:|1|3| 83 Numb/Map:NUMBER
> 13:22:36 lon [ADT]:|1|3| 9f Channel:31
>
> |1|2| is the PRI to BT
>
> 13:22:36 lon [ADT]:|1|2|==========
> 13:22:36 lon [ADT]:|1|2|Sent = Sapi:00 C/R:R Tei:00
> 13:22:36 lon [ADT]:|1|2| Ctl:INFO Ns:21 Nr:24
> 13:22:36 lon [ADT]:|1|2| Prot:08 CRL:2 CRV:0017
> 13:22:36 lon [ADT]:|1|2| M - 05 SETUP
> 13:22:36 lon [ADT]:|1|2| IE - A1 SENDING COMPLETE Len=0
> 13:22:36 lon [ADT]:|1|2| IE - 04 BEARER CAPABILITY Len=3
> 13:22:36 lon [ADT]:|1|2| 80 Xfer Cap.:SPEECH
> 13:22:36 lon [ADT]:|1|2| 90 Xfer Rate:64k
> 13:22:36 lon [ADT]:|1|2| A3 Layer 1:G.711 A-Law
> 13:22:36 lon [ADT]:|1|2| IE - 18 CHANNEL ID Len=3
> 13:22:36 lon [ADT]:|1|2| A1 Primary Rate
> 13:22:36 lon [ADT]:|1|2| Intfc ID:IMPLICIT
> 13:22:36 lon [ADT]:|1|2| Pref/Excl:PREFERRED
> 13:22:36 lon [ADT]:|1|2| D-Chan Indicated:NO
> 13:22:36 lon [ADT]:|1|2| Chan. Sel:FOLLOWS
> 13:22:36 lon [ADT]:|1|2| 83 Numb/Map:NUMBER
> 13:22:36 lon [ADT]:|1|2| 9f Channel:31
> 13:22:36 lon [ADT]:|1|2| IE - 6C CALLING PARTY # Len=8
> 13:22:36 lon [ADT]:|1|2| 00 Numb. Type:UNKNOWN
> 13:22:36 lon [ADT]:|1|2| Numb. Plan:UNKNOWN
> 13:22:36 lon [ADT]:|1|2| A1 Presentation:RESTRICTED
> 13:22:36 lon [ADT]:|1|2| Ph.# 504955
> 13:22:36 lon [ADT]:|1|2| IE - 70 CALLED PARTY # Len=14
> 13:22:36 lon [ADT]:|1|2| 80 Numb. Type:UNKNOWN
> 13:22:36 lon [ADT]:|1|2| Numb. Plan:UNKNOWN
> 13:22:36 lon [ADT]:|1|2| Ph.# 0013123963808
> 13:22:36 lon [ADT]:ISDN|1|2|Dialing '0013123963808' from '504955'.
> 13:22:36 lon [ADT]:Switchboard|1|3|0013123963808 Pri. accepted: slot
> 1, port 2
> 13:22:37 lon [ADT]:|1|2|==========
> 13:22:37 lon [ADT]:|1|2|Recd = Sapi:00 C/R:C Tei:00
> 13:22:37 lon [ADT]:|1|2| Ctl:INFO Ns:24 Nr:22
> 13:22:37 lon [ADT]:|1|2| Prot:08 CRL:2 CRV:8017
> 13:22:37 lon [ADT]:|1|2| M - 02 CALL_PROC
> 13:22:37 lon [ADT]:|1|2| IE - 18 CHANNEL ID Len=3
> 13:22:37 lon [ADT]:|1|2| A9 Primary Rate
> 13:22:37 lon [ADT]:|1|2| Intfc ID:IMPLICIT
> 13:22:37 lon [ADT]:|1|2| Pref/Excl:EXCLUSIVE
> 13:22:37 lon [ADT]:|1|2| D-Chan Indicated:NO
> 13:22:37 lon [ADT]:|1|2| Chan. Sel:FOLLOWS
> 13:22:37 lon [ADT]:|1|2| 83 Numb/Map:NUMBER
> 13:22:37 lon [ADT]:|1|2| 81 Channel:1
> 13:22:37 lon [ADT]:ISDN|1|2|Gate opened to name by Proceeding Msg.
> 13:22:40 lon [ADT]:|1|2|==========
> 13:22:40 lon [ADT]:|1|2|Recd = Sapi:00 C/R:C Tei:00
> 13:22:40 lon [ADT]:|1|2| Ctl:INFO Ns:25 Nr:22
> 13:22:40 lon [ADT]:|1|2| Prot:08 CRL:2 CRV:8017
> 13:22:40 lon [ADT]:|1|2| M - 01 ALERTING
> 13:22:40 lon [ADT]:|1|2| IE - 1E PROGRESS INDICATOR Len=2
> 13:22:40 lon [ADT]:|1|2| 84 Location:RLN
> 13:22:40 lon [ADT]:|1|2| 82 Description:DEST. NOT ISDN
> 13:22:40 lon [ADT]:ISDN|1|2|Call to '0013123963808' ringing.
> 13:22:40 lon [ADT]:|1|3|==========
> 13:22:40 lon [ADT]:|1|3|Sent = Sapi:00 C/R:C Tei:00
> 13:22:40 lon [ADT]:|1|3| Ctl:INFO Ns:37 Nr:45
> 13:22:40 lon [ADT]:|1|3| Prot:08 CRL:2 CRV:8017
> 13:22:40 lon [ADT]:|1|3| M - 01 ALERTING
> 13:22:42 lon [ADT]:|1|2|==========
>
>
> So up to now this is all strictly D-channel ISDN signalling; it's not
> until the CONNECT that we get a audio path. During this ALERTING phase
> the person who made the outbound call is hearing a buzz rather than
> "RING RING" cadence.
>
> 13:22:42 lon [ADT]:|1|2|Recd = Sapi:00 C/R:C Tei:00
> 13:22:42 lon [ADT]:|1|2| Ctl:INFO Ns:26 Nr:22
> 13:22:42 lon [ADT]:|1|2| Prot:08 CRL:2 CRV:8017
> 13:22:42 lon [ADT]:|1|2| M - 07 CONNECT
> 13:22:42 lon [ADT]:ISDN|1|2|Call to '0013123963808' connected.
> 13:22:42 lon [ADT]:ISDN|1|3|Call to '0013123963808' connected.
> 13:22:42 lon [ADT]:|1|2|==========
> 13:22:42 lon [ADT]:|1|2|Sent = Sapi:00 C/R:R Tei:00
> 13:22:42 lon [ADT]:|1|2| Ctl:INFO Ns:22 Nr:27
> 13:22:42 lon [ADT]:|1|2| Prot:08 CRL:2 CRV:0017
> 13:22:42 lon [ADT]:|1|2| M - 0F CONNECT_ACK
> 13:22:42 lon [ADT]:|1|3|==========
> 13:22:42 lon [ADT]:|1|3|Sent = Sapi:00 C/R:C Tei:00
> 13:22:42 lon [ADT]:|1|3| Ctl:INFO Ns:38 Nr:45
> 13:22:42 lon [ADT]:|1|3| Prot:08 CRL:2 CRV:8017
> 13:22:42 lon [ADT]:|1|3| M - 07 CONNECT
> 13:22:42 lon [ADT]:|1|3|==========
> 13:22:42 lon [ADT]:|1|3|Recd = Sapi:00 C/R:R Tei:00
> 13:22:42 lon [ADT]:|1|3| Ctl:INFO Ns:45 Nr:39
> 13:22:42 lon [ADT]:|1|3| Prot:08 CRL:2 CRV:0017
> 13:22:42 lon [ADT]:|1|3| M - 0F CONNECT_ACK
>
> And now there's a bi-directional audio path which has been ACKed by both
> the Adtran and the Cisco.
>
> Adtran TAC is saying that it's not them. Thoughts?
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
--
Sent from my mobile device
James
More information about the cisco-voip
mailing list