[cisco-voip] Directory number issue

[Moataz Mamdouh]

Reagrding your debug of the isdn q.931 , of this cause code unllocated/unassigned number  . this tells you that the router could  find the  dial-peer matching  for this number  ( like it's not configured or not able to receive any calls as u said)
you should have an reply from the TAC regarding the problem because it doesn't work within your cluster  also  . 
 

Jonathan Charles <jonvoip at gmail.com> wrote: Sorry, didn't read everything...

Delete the number from the system, delete it off of the phone, then go
to Route Plan Report and delete it from the unassigned DN... then
re-add it. I ran into the same issue with CCM 5.1 last week.



Jonathan

On Feb 18, 2008 5:39 PM, Jonathan Charles  wrote:
> Is ext 5870 assigned to a phone? The unallocated/unassigned number
> means that the gateway tried to send the call to CCM and CCM said 'I
> don't have that anywhere...'
>
> So, do this:
>
> Add it to a phone in a partition accessible by the Calling Search
> Space accessible by the gateway and try again.
>
>
>
> Jonathan
>
>
> On Feb 18, 2008 1:32 PM, Kienzle, John  wrote:
> >
> >
> >
> > Hello. Although we have a TAC case open, I thought I would get some opinions
> > from this excellent resource.
> >
> > We have a CM 5.1.2.2000-3 cluster in our company. One of our sites was
> > recently migrated from a standalone legacy CM 4.2 cluster to our new
> > corporate 5.x CM cluster. The only issue We have had was after a few days,
> > one of our phones stopped receiving calls. DID calls, local LAN calls by
> > direct extension, calls over the WAN by direct extension - all of them give
> > a fast busy tone. The behavior is similar to an unused or unassigned
> > directory number. The phone registers to CM just fine and can place calls
> > in/out of network just fine. We've tried completely removing the phone/DN
> > from CM and adding it back again with no luck. Also, if you assign the phone
> > a different DN it works fine. Phone and line configuration has been
> > verified. The problem definitely follows the suspect DN. A debug ISDN q931
> > give the following when calling the DN over our PRI:
> >
> > *Feb 12 13:44:57.810: ISDN Se0/3/1:23 Q931: RX <- SETUP pd = 8  callref =
> > 0x0A1B
> >
> >         Bearer Capability i = 0x8090A2
> >                 Standard = CCITT
> >                 Transfer Capability = Speech
> >                 Transfer Mode = Circuit
> >                 Transfer Rate = 64 kbit/s
> >         Channel ID i = 0xA98386
> >                 Exclusive, Channel 6
> >         Calling Party Number i = 0x2181, 'sourcenumber'
> >                 Plan:ISDN, Type:National
> >         Called Party Number i = 0xC1, '5870'
> >                 Plan:ISDN, Type:Subscriber(local)
> > *Feb 12 13:44:57.926: ISDN Se0/3/1:23 Q931: TX -> CALL_PROC pd = 8  callref
> > = 0x
> > 8A1B
> >         Channel ID i = 0xA98386
> >                 Exclusive, Channel 6
> > *Feb 12 13:44:57.926: ISDN Se0/3/1:23 Q931: TX -> DISCONNECT pd = 8  callref
> > = 0
> > x8A1B
> >         Cause i = 0x8081 - Unallocated/unassigned number
> > *Feb 12 13:44:58.006: ISDN Se0/3/1:23 Q931: RX <- RELEASE pd = 8  callref =
> > 0x0A
> > 1B
> > *Feb 12 13:44:58.082: ISDN Se0/3/1:23 Q931: TX -> RELEASE_COMP pd = 8
> > callref =
> >  0x8A1B
> > *Feb 12 13:44:58.614: ISDN Se0/3/1:23 Q931: RX <- SETUP pd = 8  callref =
> > 0x0968
> >
> >
> >
> > John Kienzle
> > Senior ITS Analyst
> > Anadarko Petroleum/WGR
> > 1400 E. Lincoln
> > Gillette, WY. 82716
> > WP - 307.685.5870
> > CP - 307.680.1746
> > John.Kienzle at anadarko.com
> >
> >
> >
> > ________________________________
> >
> >
> >  Anadarko Confidentiality Notice: This electronic transmission and any
> > attached documents or other writings are intended only for the person or
> > entity to which it is addressed and may contain information that is
> > privileged, confidential or otherwise protected from disclosure. If you have
> > received this communication in error, please immediately notify sender by
> > return e-mail and destroy the communication. Any disclosure, copying,
> > distribution or the taking of any action concerning the contents of this
> > communication or any attachments by anyone other than the named recipient is
> > strictly prohibited.
> > _______________________________________________
> > 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


       
---------------------------------
Looking for last minute shopping deals?  Find them fast with Yahoo! Search.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080218/8c64b955/attachment.html