Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Calls fail from VG 200 to Analogue 3640 Gateway

I have a setup with 2 VG200 digital gateways. The first is on ISDN with Q931. The 2nd is connected to a customer PBX using QSIG When I make calls from the PBX to the Analogue 3640 Gateway they fail, However calls from the ISDN via the other gateway are OK.

Calls from the PBX to the ISDN VG200 are OK as are calls from the ISDn VG200 to the Analogue 3640. I also have calls from the PBX to an AVVID setup and these are also OK as are calls from AVVID to the Anaolgue Gateway.

The only difference between the 2 VG 200 gw's is that the PBX is QSIG compared with Q931, When calls are received the only other differnece is that the Prog Ind shows reserved value and numbering plan is private compared with unknown on the working

Any ideas?

Progress Ind i = 0xA090 - Reserved value

*Mar 1 05:27:23.074: Calling Party Number i = 'I', 0x83, '01418876170',

Plan:Private, Type:Subscriber(local)

*Mar 1 05:27:23.078: Called Party Number i = 0xC9, '4756', Plan:Private

, Type:Subscriber(local)

3 REPLIES
Cisco Employee

Re: Calls fail from VG 200 to Analogue 3640 Gateway

So you are saying that you have 3 gateways in all - (2) VG200 and (1) 3640 and the only problem is that calls fail from the QSIG VG200 to the 3640? Just want to make sure I have that straight. Can you send the output of the entire 'debug isdn q931' for whatever call scenario it is that fails? In particular I would want to see an entire SETUP and DISCONNECT or RELEASE_COMP message from the scenario that doesn't work, and one that does.

New Member

Re: Calls fail from VG 200 to Analogue 3640 Gateway

The problem seems to be that the VG200 never sends an alerting to the PBX resulting in a disconnect by the PBX. I have reconfigured the VG200 to PRI-Net5 and exactly as the VG200 which works but it makes no difference. The only other difference is that the Q931 show as Plan:Private, Type:Subscriber(local) whereas the working one is showing as unknown.

I had some Debug with Voip also. I have hopefully left in all the Q931.

CH-VG200-PBX#

*Mar 1 05:27:23.066: ISDN Se1/0:15: RX <- SETUP pd = 8 callref = 0x0704

*Mar 1 05:27:23.070: Sending Complete

*Mar 1 05:27:23.070: Bearer Capability i = 0x9090A3

*Mar 1 05:27:23.070: Channel ID i = 0xA9839E

*Mar 1 05:27:23.074: Progress Ind i = 0xA090 - Reserved value

*Mar 1 05:27:23.074: Calling Party Number i = 'I', 0x83, '01418876170',

Plan:Private, Type:Subscriber(local)

*Mar 1 05:27:23.078: Called Party Number i = 0xC9, '4756', Plan:Private

, Type:Subscriber(local)

*Mar 1 05:27:23.246: ISDN Se1/0:15: TX -> PROGRESS pd = 8 callref = 0x8704

*Mar 1 05:27:23.250: Progress Ind i = 0x8188 - In-band info or appropri

ate now available

*Mar 1 05:27:28.038: ISDN Se1/0:15: RX <- DISCONNECT pd = 8 callref = 0x0704

*Mar 1 05:27:28.038: Cause i = 0x809F - Normal, unspecified

*Mar 1 05:27:28.050: ISDN Se1/0:15: TX -> RELEASE pd = 8 callref = 0x8704

*Mar 1 05:27:28.070: ISDN Se1/0:15: RX <- RELEASE_COMP pd = 8 callref = 0x070

4

*Mar 1 05:27:34.978: ISDN Se1/0:15: RX <- DISCONNECT pd = 8 callref = 0x0701

*Mar 1 05:27:34.978: Cause i = 0x8090 - Normal call clearing

*Mar 1 05:27:34.990: ISDN Se1/0:15: TX -> RELEASE pd = 8 callref = 0x8701

*Mar 1 05:27:35.014: ISDN Se1/0:15: RX <- RELEASE_COMP pd = 8 callref = 0x070

1

Cisco Employee

Re: Calls fail from VG 200 to Analogue 3640 Gateway

I am beginning to think that you may need to work with TAC on this one if you are not already.

It could be as you suggested that the PBX is expecting an ALERTING message. You can try to configure interface Serial1/0:15 and enable isdn send-alerting to see if we send it and whether it makes a difference.

93
Views
0
Helpful
3
Replies
CreatePlease to create content