[cisco-voip] Nonworking DID

[Karl Whitson]

Jonathan,

 

I had a case open with the carrier (AT&T) and they pushed it back on me
(big surprise there, huh) stating that they are routing the entire block
of DIDs the same way.  "It is your problem". 

 

I don't disagree with you that it seems to be a gateway or Telco issue.
What I do find odd is that I can not get the gateway to send an
unallocated message when I delete the number entirely from CM.  That
makes me think that it could be something on CM.  The gateway is MGCP.

 

Karl Whitson

CMB Technologies

40 Cape Rd.

Milford, MA  01757

DID:  (508) 422-8413

Cell:  (603) 930-4189

Fax:  (508) 634-8678

Karl.Whitson at cmbtec.com

www.cmbtec.com

TO OPEN A SUPPORT CASE EMAIL SUPPORT at CMBTEC.COM
<mailto:SUPPORT at CMBTEC.COM>  OR CALL (508) 422-8429

  

________________________________

From: Jonathan Charles [mailto:jonvoip at gmail.com] 
Sent: Friday, December 15, 2006 10:55 AM
To: Karl Whitson
Cc: cisco-voip at puck-nether.net
Subject: Re: [cisco-voip] Nonworking DID

 

First off, to determine ISDN disconnect cause codes, go here:

http://www.cisco.com/warp/public/129/isdn_disc_code.html

Here is what yours is: 

"The destination is not reachable because of an interface malfunction.
In addition, a signaling message cannot be delivered. This condition can
be temporary. However, the condition can last for an extended period in
some cases. 

This cause indicates that a signaling message could not be delivered to
the remote user. For example, a physical layer or data link layer fails
at the remote user end, and the user equipment is off-line (turned
off)."

Provide a 'show controllers t1' and a 'show isdn status'

I don't think the issue is with CCM... it is either gateway or telco.




Jonathan



On 12/15/06, Karl Whitson <KWhitson at cmbtec.com> wrote:

I have a single DID (5767) out of a block of 100 numbers (5700 - 5799)
that is not functioning properly.  With this DN configured on a phone I
get "Cause i = 0x809B - Destination out of order" on the Q.931 debug,
see below.  If I dial a non allocated number (5766) I get the normal and
expected "Cause i = 0x8081 - Unallocated/unassigned number".  Yet, if I
delete all instances of 5767, even going into the Num Plan Report and
deleting it there, I still get a "Cause i = 0x809B - Destination out of
order" for that number.  

It seems that Call Manager is storing that number somewhere and is not
clearing it out when it is deleted from the system.  I am thinking that
I need to cycle a service on Call Manager.  Does anyone know which
service I should cycle to try to clear it?  I will reboot the Call
Manager tonight to see if it will clear, but was just wondering if
anyone had seen this before.

 

            Bearer Capability i = 0x8090A2 

                        Standard = CCITT 

                        Transfer Capability = Speech  

                        Transfer Mode = Circuit 

                        Transfer Rate = 64 kbit/s 

            Channel ID i = 0xA98381 

                        Exclusive, Channel 1 

            Progress Ind i = 0x8283 - Origination address is non-ISDN  

            Calling Party Number i = 0x2183, '6039304189' 

                        Plan:ISDN, Type:National 

            Called Party Number i = 0x80, '5767' 

                        Plan:Unknown, Type:Unknown

*Dec 15 08:40:09.104 EST: ISDN Se0/0/0:23 Q931: TX -> RELEASE_COMP pd =
8  callref = 0x800F 

            Cause i = 0x809B - Destination out of order

 

Karl Whitson

CMB Technologies

40 Cape Rd.

Milford, MA  01757

DID:  (508) 422-8413

Cell:  (603) 930-4189

Fax:  (508) 634-8678

Karl.Whitson at cmbtec.com 

www.cmbtec.com

TO OPEN A SUPPORT CASE EMAIL SUPPORT at CMBTEC. C
<mailto:SUPPORT at CMBTEC.COM> OM OR CALL (508) 422-8429

  

 


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



 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20061215/d60ef7a8/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 2318 bytes
Desc: image001.jpg
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20061215/d60ef7a8/attachment-0002.jpe 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 2318 bytes
Desc: image002.jpg
Url : https://puck.nether.net/pipermail/cisco-voip/attachments/20061215/d60ef7a8/attachment-0003.jpe