Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cisco VOIP/PRI/Norstar

Status
Not open for further replies.

SJCBR

Technical User
Sep 30, 2004
11
US
Hi,

Has anybody encountered this problem? I installed a new cisco 2811 router to handle a Norstar PRI but it will not work. I'm assuming it's a software issue with the router. The older 2611 works fine.

Notes from Cisco:
The router/gateway is disconnecting the call because it thinks the Nortel is reporting the wrong call state. After the CONNECT message, the gateway goes to call state 10 (which is correct according to the Q.931 specification). The Nortel then sends us a STATUS message saying "Information element not implemented". In that STATUS message they also tell us that they are in call state 4. Since we are in a different call state, we disconnect the call as allowed by the Q.931 spec.

The problem here is that the Q.931 specification says that the network side (gateway) goes from call state 4 to call state 10 after sending the CONNECT message, but the user side (PBX) doesn't go from call state 4 to call state 10 until after it sends the CONNECT_ACK. In other words, both sides are following the specification correctly.

The 2611 router is not having this problem becasue it does not send any information elements (IE's) in the CONNECT message. This is probably because it is running an older version of IOS that does not support the Facility and Connected Number IE's.

Router trace:
0x8B0100
0xA11A0202010002010280115048494C4950204752414D4D415449434F
Component = Invoke component, Unsupported operation
Progress Ind i = 0x8182 - Destination address is non-ISDN
Connected Number i = 0x0080, '9944070'
.Jan 18 19:37:32.150: ISDN Se0/1/0:23 Q931: RX <- STATUS pd = 8 callref = 0x000
3
Cause i = 0x81E3 - Information element not implemented
Call State i = 0x04
.Jan 18 19:37:32.150: ISDN Se0/1/0:23 **ERROR**: Ux_Status: STATUS call state mi
smatch with invalid cause: cause 0x63, state 0xA, peer state 0x4
.Jan 18 19:37:32.150: ISDN Se0/1/0:23 Q931: RX <- CONNECT_ACK pd = 8 callref =
0x0003
.Jan 18 19:37:32.154: ISDN Se0/1/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x80
03
Cause i = 0xC2E5 - Message not compatible with call state
.Jan 18 19:37:32.182: ISDN Se0/1/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref =
0x0003

Thanks,
SJC
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top