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)<br><span class="content"></span>you should have an reply from the TAC regarding the problem because it doesn't work within your cluster also . <br> <br><br><b><i>Jonathan Charles <jonvoip@gmail.com></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> Sorry, didn't read everything...<br><br>Delete the number from the system, delete it off of the phone, then go<br>to Route Plan Report and delete it from the unassigned DN... then<br>re-add it. I ran into the same issue with CCM 5.1 last week.<br><br><br><br>Jonathan<br><br>On Feb 18, 2008 5:39 PM, Jonathan Charles <jonvoip@gmail.com> wrote:<br>> Is ext 5870
assigned to a phone? The unallocated/unassigned number<br>> means that the gateway tried to send the call to CCM and CCM said 'I<br>> don't have that anywhere...'<br>><br>> So, do this:<br>><br>> Add it to a phone in a partition accessible by the Calling Search<br>> Space accessible by the gateway and try again.<br>><br>><br>><br>> Jonathan<br>><br>><br>> On Feb 18, 2008 1:32 PM, Kienzle, John <John.Kienzle@anadarko.com> wrote:<br>> ><br>> ><br>> ><br>> > Hello. Although we have a TAC case open, I thought I would get some opinions<br>> > from this excellent resource.<br>> ><br>> > We have a CM 5.1.2.2000-3 cluster in our company. One of our sites was<br>> > recently migrated from a standalone legacy CM 4.2 cluster to our new<br>> > corporate 5.x CM cluster. The only issue We have had was after a few days,<br>> > one of our phones stopped receiving calls. DID calls, local
LAN calls by<br>> > direct extension, calls over the WAN by direct extension - all of them give<br>> > a fast busy tone. The behavior is similar to an unused or unassigned<br>> > directory number. The phone registers to CM just fine and can place calls<br>> > in/out of network just fine. We've tried completely removing the phone/DN<br>> > from CM and adding it back again with no luck. Also, if you assign the phone<br>> > a different DN it works fine. Phone and line configuration has been<br>> > verified. The problem definitely follows the suspect DN. A debug ISDN q931<br>> > give the following when calling the DN over our PRI:<br>> ><br>> > *Feb 12 13:44:57.810: ISDN Se0/3/1:23 Q931: RX <- SETUP pd = 8 callref =<br>> > 0x0A1B<br>> ><br>> > Bearer Capability i = 0x8090A2<br>> > Standard = CCITT<br>> > Transfer Capability = Speech<br>> >
Transfer Mode = Circuit<br>> > Transfer Rate = 64 kbit/s<br>> > Channel ID i = 0xA98386<br>> > Exclusive, Channel 6<br>> > Calling Party Number i = 0x2181, 'sourcenumber'<br>> > Plan:ISDN, Type:National<br>> > Called Party Number i = 0xC1, '5870'<br>> > Plan:ISDN, Type:Subscriber(local)<br>> > *Feb 12 13:44:57.926: ISDN Se0/3/1:23 Q931: TX -> CALL_PROC pd = 8 callref<br>> > = 0x<br>> > 8A1B<br>> > Channel ID i = 0xA98386<br>> > Exclusive, Channel 6<br>> > *Feb 12 13:44:57.926: ISDN Se0/3/1:23 Q931: TX -> DISCONNECT pd = 8 callref<br>> > = 0<br>> > x8A1B<br>> > Cause i = 0x8081 - Unallocated/unassigned number<br>> > *Feb 12 13:44:58.006: ISDN Se0/3/1:23 Q931: RX <- RELEASE pd = 8 callref =<br>> > 0x0A<br>> >
1B<br>> > *Feb 12 13:44:58.082: ISDN Se0/3/1:23 Q931: TX -> RELEASE_COMP pd = 8<br>> > callref =<br>> > 0x8A1B<br>> > *Feb 12 13:44:58.614: ISDN Se0/3/1:23 Q931: RX <- SETUP pd = 8 callref =<br>> > 0x0968<br>> ><br>> ><br>> ><br>> > John Kienzle<br>> > Senior ITS Analyst<br>> > Anadarko Petroleum/WGR<br>> > 1400 E. Lincoln<br>> > Gillette, WY. 82716<br>> > WP - 307.685.5870<br>> > CP - 307.680.1746<br>> > John.Kienzle@anadarko.com<br>> ><br>> ><br>> ><br>> > ________________________________<br>> ><br>> ><br>> > Anadarko Confidentiality Notice: This electronic transmission and any<br>> > attached documents or other writings are intended only for the person or<br>> > entity to which it is addressed and may contain information that is<br>> > privileged, confidential or otherwise protected from disclosure. If you
have<br>> > received this communication in error, please immediately notify sender by<br>> > return e-mail and destroy the communication. Any disclosure, copying,<br>> > distribution or the taking of any action concerning the contents of this<br>> > communication or any attachments by anyone other than the named recipient is<br>> > strictly prohibited.<br>> > _______________________________________________<br>> > cisco-voip mailing list<br>> > cisco-voip@puck.nether.net<br>><br>> > https://puck.nether.net/mailman/listinfo/cisco-voip<br>> ><br>> ><br>><br>_______________________________________________<br>cisco-voip mailing list<br>cisco-voip@puck.nether.net<br>https://puck.nether.net/mailman/listinfo/cisco-voip<br></John.Kienzle@anadarko.com></jonvoip@gmail.com></blockquote><br><p> 
<hr size=1>Looking for last minute shopping deals? <a href="http://us.rd.yahoo.com/evt=51734/*http://tools.search.yahoo.com/newsearch/category.php?category=shopping">
Find them fast with Yahoo! Search.</a>