[cisco-voip] Anyway to stop ISDN NOTIFY message?
Erick Bergquist
erickbe at yahoo.com
Wed Aug 9 21:56:42 EDT 2006
Thanks Wes. Changing to PRI NI2 fixed up this issue.
----- Original Message ----
From: Wes Sisk <wsisk at cisco.com>
To: Erick Bergquist <erickbe at yahoo.com>
Cc: ciscovoip <cisco-voip at puck.nether.net>
Sent: Friday, August 4, 2006 8:24:58 AM
Subject: Re: [cisco-voip] Anyway to stop ISDN NOTIFY message?
This is typically an ISDN switch type mismatch. But there is one known
caveat:
For DMS NA11 or earlier release, we choose PRI DMS 100 protocol.
This is the 1998 version DMS 100 specification CCM supports for PRI
DMS 100.
Digital Switching Systems
ISDN Primary Rate User-Network
Interface Specification
NA011 Standard 08.01 August 1998
========================================================
For DMS NA12 and later releases, we should choose PRI NI2
protocol. CCM doesn't support 1999 version DMS 100 specification.
1999 version is more close to national ISDN PRI protocol. So for
DMS NA14, please try to set to PRI NI2 protocol for this PRI trunk.
Digital Switching Systems
NT-NI Primary Rate User-Network
Interface Specification
NA012 Standard 05.03 Aug. 3, 1999
/Wes
Erick Bergquist wrote:
> Does anyone know if there is a way to stop call manager from sending out a NOTIFY message on a DMS-100 PRI MGCP Setup? Apparently the telco does not like this since we get a message type not implemented back and I'm wondering if this may be causing problem. Telco doesn't see anything wrong with the call on their side other then it is disconnecting for some reason.
>
> The problem trying to figure out, is that on inbound calls that go to unity then get transferred back to the receptionist then blind transferred to another IP Phone extension the IP phone rings once then fast busy. The q931 has protocol error at that point. A warm/consulted transfer works just fine however. We have tried both DMS 100 and DMS 250 switchtype (same results) and all the extra options on gateway setup are unchecked.
>
> This is on a CCM 4.1(3)sr3b system.
>
> *Jul 31 20:31:07.228: ISDN Se0/0/0:23 Q931: TX -> NOTIFY pd = 8 callref
> = 0x988E
> Connected Address i = 0x80, '4554'
> Notification Ind i = 0xF1
>
> *Jul 31 20:31:07.236: ISDN Se0/0/0:23 Q931: TX -> NOTIFY pd = 8 callref
> = 0x988E
> Connected Address i = 0x80, '4554'
> Notification Ind i = 0xF1
>
> *Jul 31 20:31:07.296: ISDN Se0/0/0:23 Q931: RX <- STATUS pd = 8 callref
> = 0x188E
> Cause i = 0x80E16E - Message type not implemented
> Call State i = 0x0A
>
> *Jul 31 20:31:07.300: ISDN Se0/0/0:23 Q931: RX <- STATUS pd = 8 callref
> = 0x188E
> Cause i = 0x80E16E - Message type not implemented
> Call State i = 0x0A
>
> *Jul 31 20:31:07.304: ISDN Se0/0/0:23 Q931: RX <- DISCONNECT pd = 8
> callref = 0x188E
> Cause i = 0x80EF - Protocol error; unspecified
More information about the cisco-voip
mailing list