[cisco-voip] Anyway to stop ISDN NOTIFY message?
Erick Bergquist
erickbe at yahoo.com
Thu Aug 3 23:32:18 EDT 2006
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