For future reference, I don't believe changing the settings within CUCM will do anything unless you've got 'ccm-manager config' enabled on the gateway.<br><br clear="all">Matthew Saskin<br><a href="mailto:msaskin@gmail.com" target="_blank">msaskin@gmail.com</a><br>
203-253-9571<br><br>
<br><br><div class="gmail_quote">On Thu, Oct 21, 2010 at 11:43 PM, Jason Aarons (US) <span dir="ltr"><<a href="mailto:jason.aarons@us.didata.com">jason.aarons@us.didata.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div link="blue" vlink="purple" lang="EN-US"><div><p class="MsoNormal"><span style="color: rgb(31, 73, 125);">After several hours with AT&T Support they told us it was a Megacom T1, we tried to set Megacom in CallManager (bottom of Route Pattern) with no luck, finally setting it in IOS via “ isdn nsf-service megacom”</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> resolved the problem.</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);">interface Serial0/0/1:23</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> description AT&T Voice T1 LD </span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> no ip address</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> encapsulation hdlc</span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> isdn switch-type primary-4ess</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> isdn incoming-voice voice</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> isdn bchan-number-order ascending </span></p>
<p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> isdn nsf-service megacom</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> no cdp enable</span></p><p class="MsoNormal"><span style="color: rgb(31, 73, 125);"> </span></p>
<div><div style="border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; border-width: 1pt medium medium; padding: 3pt 0in 0in;"><p class="MsoNormal"><b><span style="font-size: 10pt;">From:</span></b><span style="font-size: 10pt;"> <a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>] <b>On Behalf Of </b>Jason Aarons (US)<br>
<b>Sent:</b> Thursday, October 21, 2010 11:40 PM<br><b>To:</b> cisco-voip (<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>)<br><b>Subject:</b> [cisco-voip] AT&T Dedicated Long Distance Circuit -Mandatory information element missing</span></p>
</div></div><p class="MsoNormal"> </p><p class="MsoNormal">This is a dedicated LD circuit with AT&T, it’s 4ess but having trouble getting telco to tell us what their D-Channel is seeing? Anyone seen this before?</p><p class="MsoNormal">
</p><p class="MsoNormal">CallManager 8x, same results with h323 and SIP…..we </p><p class="MsoNormal"> </p><p class="MsoNormal">026437: Oct 21 20:39:54.101 EDT: ISDN Se0/0/1:23 Q931: TX -> SETUP pd = 8 callref = 0x01A2</p>
<p class="MsoNormal"> Bearer Capability i = 0x8090A2</p><p class="MsoNormal"> Standard = CCITT</p><p class="MsoNormal"> Transfer Capability = Speech</p><p class="MsoNormal"> Transfer Mode = Circuit</p>
<p class="MsoNormal"> Transfer Rate = 64 kbit/s</p><p class="MsoNormal"> Channel ID i = 0xA98381</p><p class="MsoNormal"> Exclusive, Channel 1</p><p class="MsoNormal"> Calling Party Number i = 0x0081, '9059643123'</p>
<p class="MsoNormal"> Plan:Unknown, Type:Unknown</p><p class="MsoNormal"> Called Party Number i = 0x80, '4047407241'</p><p class="MsoNormal"> Plan:Unknown, Type:Unknown</p><p class="MsoNormal">
026438: Oct 21 20:39:54.151 EDT: ISDN Se0/0/1:23 Q931: RX <- RELEASE_COMP pd = 8 callref = 0x81A2</p><p class="MsoNormal"> Cause i = 0x83E020 - Mandatory information element missing</p><div class="MsoNormal" style="text-align: center;" align="center">
<span style="font-size: 12pt; font-family: "Times New Roman","serif";"><hr align="center" size="1" width="100%"></span></div><p><b>Disclaimer: This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you. </b></p>
</div></div>
<div><p></p><hr size="1">
<p><b>
Disclaimer:
This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only. If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.
</b></p></div><br>_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br></blockquote></div><br>