<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7653.21">
<TITLE>Directory number issue</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">Hello. Although we have a TAC case open, I thought I would get some opinions from this excellent resource.</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">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 SIZE=2 FACE="Arial">*Feb 12 13:44:57.810: ISDN Se0/3/1:23 Q931: RX <- SETUP pd = 8 callref = 0x0A1B</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial"> Bearer Capability i = 0x8090A2</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Standard = CCITT</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Transfer Capability = Speech</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Transfer Mode = Circuit</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Transfer Rate = 64 kbit/s</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Channel ID i = 0xA98386</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Exclusive, Channel 6</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Calling Party Number i = 0x2181, 'sourcenumber'</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Plan:ISDN, Type:National</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Called Party Number i = 0xC1, '</FONT><FONT COLOR="#FF0000" SIZE=2 FACE="Arial">5870</FONT><FONT SIZE=2 FACE="Arial">'</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Plan:ISDN, Type:Subscriber(local)</FONT>
<BR><FONT SIZE=2 FACE="Arial">*Feb 12 13:44:57.926: ISDN Se0/3/1:23 Q931: TX -> CALL_PROC pd = 8 callref = 0x</FONT>
<BR><FONT SIZE=2 FACE="Arial">8A1B</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Channel ID i = 0xA98386</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Exclusive, Channel 6</FONT>
<BR><FONT SIZE=2 FACE="Arial">*Feb 12 13:44:57.926: ISDN Se0/3/1:23 Q931: TX -> DISCONNECT pd = 8 callref = 0</FONT>
<BR><FONT SIZE=2 FACE="Arial">x8A1B</FONT>
<BR><FONT SIZE=2 FACE="Arial"> Cause i = 0x8081 - </FONT><FONT COLOR="#FF0000" SIZE=2 FACE="Arial">Unallocated/unassigned number</FONT>
<BR><FONT SIZE=2 FACE="Arial">*Feb 12 13:44:58.006: ISDN Se0/3/1:23 Q931: RX <- RELEASE pd = 8 callref = 0x0A</FONT>
<BR><FONT SIZE=2 FACE="Arial">1B</FONT>
<BR><FONT SIZE=2 FACE="Arial">*Feb 12 13:44:58.082: ISDN Se0/3/1:23 Q931: TX -> RELEASE_COMP pd = 8 callref =</FONT>
<BR><FONT SIZE=2 FACE="Arial"> 0x8A1B</FONT>
<BR><FONT SIZE=2 FACE="Arial">*Feb 12 13:44:58.614: ISDN Se0/3/1:23 Q931: RX <- SETUP pd = 8 callref = 0x0968</FONT>
</P>
<BR>
<BR>
<P><FONT COLOR="#008080" SIZE=2 FACE="Bodoni MT">John Kienzle</FONT>
<BR><FONT COLOR="#008080" SIZE=2 FACE="Bodoni MT">Senior ITS Analyst</FONT>
<BR><FONT COLOR="#008080" SIZE=2 FACE="Bodoni MT">Anadarko Petroleum/WGR</FONT>
<BR><FONT COLOR="#008080" SIZE=2 FACE="Bodoni MT">1400 E. Lincoln</FONT>
<BR><FONT COLOR="#008080" SIZE=2 FACE="Bodoni MT">Gillette, WY. 82716</FONT>
<BR><FONT COLOR="#008080" SIZE=2 FACE="Bodoni MT">WP - 307.685.5870</FONT>
<BR><FONT COLOR="#008080" SIZE=2 FACE="Bodoni MT">CP - 307.680.1746</FONT>
<BR><FONT COLOR="#008080" SIZE=2 FACE="Bodoni MT">John.Kienzle@anadarko.com</FONT>
</P>
</BODY>
</HTML>
<HTML><BODY>
<br>
<P><hr size=1></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>