[cisco-voip] MCI PRI Signalling and CallManager 3.3(4)
nikola at spamcop.net
nikola at spamcop.net
Wed Dec 22 14:53:15 EST 2004
If anyone on this list has any experience with setting up MCI-provided T1 PRIs
using CallManager and IOS MGCP gateway (3640 with HDV and MFT-T1 in this case),
I would greatly appreciate your help. MCI does not use NI signalling - according
to their tech, it is a "DMS-100 switch emulating 5ESS" (that was the extent of
MCI help).
Incoming calls on the PRI work fine (they get redirected into Unity handler);
outgoing calls get terminated with an '0x80E4 - Invalid information element
contents' error message. I did try several calling party/plan options, to no
avail.
Any help would be appreciated!
Nikola
P. S.: Here is a complete debug isdn q931:
*May 23 21:40:49.455: ISDN Se2/0:23 Q931: TX -> SETUP pd = 8 callref = 0x000A
Bearer Capability i = 0x8090A2
Standard = CCITT
Transer Capability = Speech
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0xA98397
Exclusive, Channel 23
Net Specific Fac i = 0x00E6
Display i = 'Nikola Stojsin'
Calling Party Number i = 0x0081, '732[...]'
Plan:Unknown, Type:Unknown
Called Party Number i = 0xA1, '7324188900'
Plan:ISDN, Type:National
*May 23 21:40:49.519: ISDN Se2/0:23 Q931: RX <- STATUS pd = 8 callref = 0x800A
Cause i = 0x80AB28 - Access information discarded
Call State i = 0x01
*May 23 21:40:49.523: ISDN Se2/0:23 Q931: TX -> STATUS pd = 8 callref = 0x000A
Cause i = 0x80E4 - Invalid information element contents
Call State i = 0x01
*May 23 21:40:49.567: ISDN Se2/0:23 Q931: RX <- CALL_PROC pd = 8 callref =
0x800A
Channel ID i = 0xA98397
Exclusive, Channel 23
*May 23 21:40:49.615: ISDN Se2/0:23 Q931: RX <- DISCONNECT pd = 8 callref =
0x800A
Cause i = 0x80E4 - Invalid information element contents
*May 23 21:40:49.651: ISDN Se2/0:23 Q931: TX -> RELEASE pd = 8 callref = 0x000A
*May 23 21:40:49.715: ISDN Se2/0:23 Q931: RX <- RELEASE_COMP pd = 8 callref =
0x800A
More information about the cisco-voip
mailing list