[cisco-voip] MCI PRI Signalling and CallManager 3.3(4)

Voll, Scott Scott.Voll at wesd.org
Wed Dec 22 16:13:24 EST 2004


Also look at your plan type.  It may need to be set to ISDN National on
both calling and called.

Just a stab in the dark.

Scott

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Wednesday, December 22, 2004 12:17 PM
To: nikola at spamcop.net
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] MCI PRI Signalling and CallManager 3.3(4)

What do you have the PRI protocol type set to?  If they are doing 5ESS 
you should set it to 5E8 I believe in the CM web page.  If that still 
doesn't work see if they can drop the 5ESS emulation and do DMS100.

-Ryan
On Dec 22, 2004, at 2:53 PM, nikola at spamcop.net wrote:

> 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
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



More information about the cisco-voip mailing list