<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<blockquote cite="mid:53F4DAC7.80207@jeff.net" type="cite"> Ok, here
is an intense debug trace. I've replaced the phone numbers to
protect the innocent. The smoking gun seems to be this:<br>
<br>
Ext: 1 Cause: Destination out of order (27)<br>
<br>
Though I have no idea why... calling the same destination from my
cell phone works fine. We only send seven digits for local
"on-island" calls like this, and calls to other carriers work fine
with the same format. I'm starting to doubt there is anything I
can do to fix this... seems like an issue between my telco and
Sprint?<br>
<br>
Cheers,<br>
<br>
j<br>
</blockquote>
<br>
[snip long trace]<br>
<br>
From here <a class="moz-txt-link-freetext" href="http://www.cnes.com/causecodes.html">http://www.cnes.com/causecodes.html</a>:<br>
<br>
<b>Cause No. 27 - destination out of order [Q.850] </b> <br>
This cause indicates that the destination indicated by the user
cannot be reached because the interface to the destination is not
functioning correctly. The term "not functioning correctly"
indicates that a signal message was unable to be delivered to the
remote party; e.g., a physical layer or data link layer failure at
the remote party or user equipment off-line. <br>
<br>
I am betting this is simply what my telco is sending because they
were unable to pass the call on to Sprint. It would be more
informative perhaps to see what kind of trace the telco has of the
handoff to Sprint. I'm going to see if they will give it to me.<br>
<br>
Cheers,<br>
<br>
j<br>
</body>
</html>