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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Issues with Windstream and NI-2 (And DMS 100)

Status
Not open for further replies.

chiden

Vendor
Dec 27, 2006
178
US
We have two sites with MICS. One a 4.1. Other 5.0.
Windstream brought in a 100 Mbps fiber with fiber handoff. When we try and use NI-2, can't make or receive any calls. Per Windstream. They are seeing. "protocol mismatch error".
Tried DMS 100. Was able to make calls. But had intermittent incoming calls. From what we think is going on, calls originating from SIP service are not being completed. Did see call flash on the programmed A&R target line.
Here is what Windstream provided on those calls.

Aug 3 17:03:23.264 GMT: ISDN Se0/0/0:23 Q931: Applying typeplan for sw-type 0x5 is 0x2 0x1, Calling num 3197348435
Aug 3 17:03:23.264 GMT: ISDN Se0/0/0:23 Q931: Sending SETUP callref = 0x00A9 callID = 0x802A switch = primary-dms100 interface = Network
Aug 3 17:03:23.264 GMT: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x00A9
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Display i = 0xB1, 'Chris Yeater ACD'
Calling Party Number
clubcorp-ClubCorp-6777270# i = 0x2180, '3197348435'
Plan:ISDN, Type:National
Called Party Number i = 0xA1, '662'
Plan:ISDN, Type:National
Aug 3 17:03:23.368 GMT: ISDN Se0/0/0:23 Q931: RX <- STATUS pd = 8 callref = 0x80A9
Cause i = 0x81E4 - Invalid information element contents
Call State i = 0x06
Aug 3 17:03:23.368 GMT: ISDN Se0/0/0:23 **ERROR**: Ux_Status: STATUS call state mismatch with invalid cause: cause 0x64, state 0x1, peer state 0x6
Aug 3 17:03:23.368 GMT: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x00A9
Cause i = 0x82EF - Protocol error; unspecified
Aug 3 17:03:23.404 GMT: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x80A9
Aug 3 17:03:23.488 GMT: ISDN Se0/0/0:23 Q931: Applying typeplan for sw-type 0x5 is 0x2 0x1, Calling num 3197348435
Aug 3 17:03:23.488 GMT: ISDN Se0/0/0:23 Q931: Sending SETUP callref = 0x00AA callID = 0x802B switch = primary-dms100 interface = Network
Aug 3 17:03:23.488 GMT: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x00AA
Bearer Capability i = 0x8090A2
Standard = CCITT
Transfer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98381
Exclusive, Channel 1
Display i = 0xB1, 'Chris Yeater ACD'
Calling Party Number
clubcorp-ClubCorp-6777270# i = 0x2180, '3197348435'
Plan:ISDN, Type:National
Called Party Number i = 0xA1, '662'
Plan:ISDN, Type:National
Aug 3 17:03:23.592 GMT: ISDN Se0/0/0:23 Q931: RX <- STATUS pd = 8 callref = 0x80AA
Cause i = 0x81E4 - Invalid information element contents
Call State i = 0x06
Aug 3 17:03:23.592 GMT: ISDN Se0/0/0:23 **ERROR**: Ux_Status: STATUS call state mismatch with invalid cause: cause 0x64, state 0x1, peer state 0x6
Aug 3 17:03:23.592 GMT: ISDN Se0/0/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x00AA
Cause i = 0x82EF - Protocol error; unspecified
Aug 3 17:03:23.648 GMT: ISDN Se0/0/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x80AA
clubcorp-ClubCorp-6777270#

Any thoughts or recommendations would be greatly appreciated.
 
Post your PRI programming setup on both systems.
If they say there is a mismatch you need to make sure your settings matches theirs.



________________________________________

Add me to LinkedIN

small-logo-sig.png

=----(((((((((()----=
Toronto, CAN
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top