cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
869
Views
5
Helpful
6
Replies

UCM PRI Problem

mstafford
Level 1
Level 1

We are testing an AT&T PRI (Gateway is a 2821) which is controlled by UCM 6.0 via MGCP. We are sending the correct digits - verified by a debug isdn q931 - but get the following error: "Cause i = 0x83E020 - Mandatory information element missing". Anyone seen this error or have an idea of what to look for. We have tried a couple different protocols

NI2 and 4ESS along with various parameters on the gateway with no sucess. Thanks!

1 Accepted Solution

Accepted Solutions

Jaime Valencia
Cisco Employee
Cisco Employee

can u post the debug isdn q931 to look at all the IEs you're sending?

javalenc

HTH

java

if this helps, please rate

View solution in original post

6 Replies 6

Jaime Valencia
Cisco Employee
Cisco Employee

can u post the debug isdn q931 to look at all the IEs you're sending?

javalenc

HTH

java

if this helps, please rate

Correction, this is what we're seeing:

Apr 20 03:53:59: ISDN Se0/0/1:23 Q931: TX -> SETUP pd = 8 callref = 0x0009

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98397

Exclusive, Channel 23

Calling Party Number i = 0x2181, '3037928854'

Plan:ISDN, Type:National

Called Party Number i = 0xA1, '6126643270'

Plan:ISDN, Type:National

Apr 20 03:53:59: ISDN Se0/0/1:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x8009

Cause i = 0x83E020

Sorry, This is all I captured...We tried ISDN, National, International IE's

try unknown, unknown

if still no avail id recommend to give a call to the telco to find out what they want. some telcos expect a specific plan and type for the calls

javalenc

HTH

java

if this helps, please rate

Thanks. That's just what we'll do tomorrow!

Thanks! We tried the "isdn nsf-service sdn" command under the serial interface of the router, but this didn't help with outbound calls. Then we configured the "PRI 4ESS" switch type and "sdn" under the ISDN Parameters [in the long distance route pattern]. That fixed it!

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: