<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Directory number issue</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3268" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=156370721-18022008><FONT face=Arial
color=#0000ff size=2>You'll want to look at the CCM traces to see what CM is
doing with the call. Does the DN have a forward no-answer or unregistered
configured? </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=156370721-18022008><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=156370721-18022008><FONT face=Arial
color=#0000ff size=2>Make sure to get traces going back to the last time the
phone received a call. Without these you can find out the current state of
the DN but not how it got that way.</FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/plain format -->
<P><FONT size=2>-Ryan </FONT></P>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Kienzle,
John<BR><B>Sent:</B> Monday, February 18, 2008 2:32 PM<BR><B>To:</B>
cisco-voip@puck.nether.net<BR><B>Cc:</B> Kienzle, John<BR><B>Subject:</B>
[cisco-voip] Directory number issue<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format -->
<P><FONT face=Arial size=2>Hello. Although we have a TAC case open, I thought I
would get some opinions from this excellent resource.</FONT> </P>
<P><FONT face=Arial size=2>We have a CM</FONT> <FONT
face="Times New Roman">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:</FONT></P>
<P><FONT face=Arial size=2>*Feb 12 13:44:57.810: ISDN Se0/3/1:23 Q931: RX <-
SETUP pd = 8 callref = 0x0A1B</FONT> </P>
<P><FONT face=Arial size=2> Bearer
Capability i = 0x8090A2</FONT> <BR><FONT face=Arial
size=2>
Standard = CCITT</FONT> <BR><FONT face=Arial
size=2>
Transfer Capability = Speech</FONT> <BR><FONT face=Arial
size=2>
Transfer Mode = Circuit</FONT> <BR><FONT face=Arial
size=2>
Transfer Rate = 64 kbit/s</FONT> <BR><FONT face=Arial
size=2> Channel ID i = 0xA98386</FONT>
<BR><FONT face=Arial
size=2>
Exclusive, Channel 6</FONT> <BR><FONT face=Arial
size=2> Calling Party Number i =
0x2181, 'sourcenumber'</FONT> <BR><FONT face=Arial
size=2>
Plan:ISDN, Type:National</FONT> <BR><FONT face=Arial
size=2> Called Party Number i = 0xC1,
'</FONT><FONT face=Arial color=#ff0000 size=2>5870</FONT><FONT face=Arial
size=2>'</FONT> <BR><FONT face=Arial
size=2>
Plan:ISDN, Type:Subscriber(local)</FONT> <BR><FONT face=Arial size=2>*Feb 12
13:44:57.926: ISDN Se0/3/1:23 Q931: TX -> CALL_PROC pd = 8 callref =
0x</FONT> <BR><FONT face=Arial size=2>8A1B</FONT> <BR><FONT face=Arial
size=2> Channel ID i = 0xA98386</FONT>
<BR><FONT face=Arial
size=2>
Exclusive, Channel 6</FONT> <BR><FONT face=Arial size=2>*Feb 12 13:44:57.926:
ISDN Se0/3/1:23 Q931: TX -> DISCONNECT pd = 8 callref = 0</FONT>
<BR><FONT face=Arial size=2>x8A1B</FONT> <BR><FONT face=Arial
size=2> Cause i = 0x8081 -
</FONT><FONT face=Arial color=#ff0000 size=2>Unallocated/unassigned
number</FONT> <BR><FONT face=Arial size=2>*Feb 12 13:44:58.006: ISDN Se0/3/1:23
Q931: RX <- RELEASE pd = 8 callref = 0x0A</FONT> <BR><FONT face=Arial
size=2>1B</FONT> <BR><FONT face=Arial size=2>*Feb 12 13:44:58.082: ISDN
Se0/3/1:23 Q931: TX -> RELEASE_COMP pd = 8 callref =</FONT> <BR><FONT
face=Arial size=2> 0x8A1B</FONT> <BR><FONT face=Arial size=2>*Feb 12
13:44:58.614: ISDN Se0/3/1:23 Q931: RX <- SETUP pd = 8 callref =
0x0968</FONT> </P><BR><BR>
<P><FONT face="Bodoni MT" color=#008080 size=2>John Kienzle</FONT> <BR><FONT
face="Bodoni MT" color=#008080 size=2>Senior ITS Analyst</FONT> <BR><FONT
face="Bodoni MT" color=#008080 size=2>Anadarko Petroleum/WGR</FONT> <BR><FONT
face="Bodoni MT" color=#008080 size=2>1400 E. Lincoln</FONT> <BR><FONT
face="Bodoni MT" color=#008080 size=2>Gillette, WY. 82716</FONT> <BR><FONT
face="Bodoni MT" color=#008080 size=2>WP - 307.685.5870</FONT> <BR><FONT
face="Bodoni MT" color=#008080 size=2>CP - 307.680.1746</FONT> <BR><FONT
face="Bodoni MT" color=#008080 size=2>John.Kienzle@anadarko.com</FONT> </P><BR>
<P>
<HR SIZE=1>
<P></P>
<P><STRONG>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.
</STRONG></P></BODY></HTML>