<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div>
<div style="direction: inherit;">Sounds like the carrier has an issue between the central office and the line access multiplier.</div>
<div style="direction: inherit;"><br>
</div>
<div style="direction: inherit;">I would be headed down the SLA path with your carrier ... </div>
<br>
Sent from my iPhone</div>
<div><br>
On Sep 21, 2016, at 5:18 PM, Hughes, Scott GRE-MG <<a href="mailto:SHughes@GREnergy.com">SHughes@GREnergy.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span>Thanks for all the advice. An update on this issue:</span><br>
<span></span><br>
<span>We have been in contact with the carrier. They have indicated that others have had similar issues, all since moving to a “new” softswitch at the CO. The CO tech has apparently verified that the signalling is going out, but doesn’t get passed through the
DSLAM that is somewhere in between the CO and our premise.</span><br>
<span></span><br>
<span>Is there anyone who is knowledgeable about telephone standards & regulations? Is the carrier REQUIRED to do disconnect supervision, or is it merely a courtesy?</span><br>
<span></span><br>
<span>On Sep 12, 2016, at 1:11 AM, Esmaeel Saberi <<a href="mailto:esmaeels@gmail.com">esmaeels@gmail.com</a><<a href="mailto:esmaeels@gmail.com">mailto:esmaeels@gmail.com</a>>> wrote:</span><br>
<span></span><br>
<span>EXTERNAL</span><br>
<span></span><br>
<span>This link is usefull 😉</span><br>
<span><a href="https://supportforums.cisco.com/discussion/11127921/fxo-4-voice-ports-always-busy">https://supportforums.cisco.com/discussion/11127921/fxo-4-voice-ports-always-busy</a></span><br>
<span>On Mon, Sep 12, 2016 at 10:34 AM Esmaeel Saberi <<a href="mailto:esmaeels@gmail.com">esmaeels@gmail.com</a><<a href="mailto:esmaeels@gmail.com">mailto:esmaeels@gmail.com</a>>> wrote:</span><br>
<span>Hello</span><br>
<span>You must record the sound of busy or congestion tone and define the frequency in</span><br>
<span>router</span><br>
<span></span><br>
<span>On Mon, Sep 12, 2016 at 5:21 AM Sreekanth <<a href="mailto:sknth.n@gmail.com">sknth.n@gmail.com</a><<a href="mailto:sknth.n@gmail.com">mailto:sknth.n@gmail.com</a>>> wrote:</span><br>
<span>Hi Scott,</span><br>
<span></span><br>
<span>When reaching out to the telco, ask them what kind of disconnect they're doing. Is it:</span><br>
<span>1. Battery reversal</span><br>
<span>2. Power denial</span><br>
<span>3. Supervisory disconnect - tone played by the telco to indicate a disconnect</span><br>
<span></span><br>
<span>You've mentioned that when the remote party disconnects, the VoIP phone stays off hook. Do you hear a disconnect tone during this period? If so, the telco is using supervisory disconnect.</span><br>
<span>In that case, your DSPs on the router may need a tweak. You can do 2 things:</span><br>
<span></span><br>
<span>1. Take pcm captures on the router to capture the disconnect tone. Then open a case with TAC who can decode this and give you the settings for the supervisory disconnect.</span><br>
<span>2. Do the ds0-dump on the router and capture the tones, decode them yourself using Audacity and put in the settings.</span><br>
<span></span><br>
<span>DS0-dump: <a href="http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-system/115749-analyze-pcm-data.html">
http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-system/115749-analyze-pcm-data.html</a></span><br>
<span></span><br>
<span>Video for setting up pcm captures and Ds0-dump.</span><br>
<span><a href="https://www.youtube.com/watch?v=HkPjTBvx_YA">https://www.youtube.com/watch?v=HkPjTBvx_YA</a></span><br>
<span></span><br>
<span>Cheers!</span><br>
<span></span><br>
<span>On 12 September 2016 at 05:30, Ryan Huff <<a href="mailto:ryanhuff@outlook.com">ryanhuff@outlook.com</a><<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>>> wrote:</span><br>
<span></span><br>
<span>Scott,</span><br>
<span></span><br>
<span></span><br>
<span>You are correct, it is the default. Oddly, what I meant to suggest is that you try disabling (no battery-reversal) but it seems that I suggested you to enable it (in which it has always been enabled). Try disabling the support and see what happens.</span><br>
<span></span><br>
<span></span><br>
<span>Apologies!</span><br>
<span></span><br>
<span></span><br>
<span>Thanks,</span><br>
<span></span><br>
<span></span><br>
<span>Ryan</span><br>
<span></span><br>
<span>________________________________</span><br>
<span>From: Hughes, Scott GRE-MG <<a href="mailto:SHughes@GREnergy.com">SHughes@GREnergy.com</a><<a href="mailto:SHughes@GREnergy.com">mailto:SHughes@GREnergy.com</a>>></span><br>
<span>Sent: Sunday, September 11, 2016 7:13 PM</span><br>
<span>To: Ryan Huff</span><br>
<span>Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><<a href="mailto:cisco-voip@puck.nether.net">mailto:cisco-voip@puck.nether.net</a>></span><br>
<span>Subject: Re: [cisco-voip] FXO Disconnect Detection</span><br>
<span></span><br>
<span></span><br>
<span>:-/ unfortunately, that command must already be a default is IOS 15.5M because it doesn't show up in the running config after I put it in.</span><br>
<span></span><br>
<span>Thanks for the suggestion though!</span><br>
<span></span><br>
<span></span><br>
<span>On Sep 9, 2016, at 6:21 PM, Ryan Huff <<a href="mailto:ryanhuff@outlook.com">ryanhuff@outlook.com</a><<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>><<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a><<a href="mailto:ryanhuff@outlook.com">mailto:ryanhuff@outlook.com</a>>>>
wrote:</span><br>
<span></span><br>
<span>EXTERNAL</span><br>
<span></span><br>
<span>You may try enabling support for battery reversal detection on the voice port;</span><br>
<span></span><br>
<span>voice-port x/x/x</span><br>
<span>battery-reversal</span><br>
<span>!</span><br>
<span></span><br>
<span>-Ryan</span><br>
<span></span><br>
<span>On Sep 9, 2016, at 6:57 PM, Hughes, Scott GRE-MG <<a href="mailto:SHughes@GREnergy.com">SHughes@GREnergy.com</a><<a href="mailto:SHughes@GREnergy.com">mailto:SHughes@GREnergy.com</a>><<a href="mailto:SHughes@GREnergy.com">mailto:SHughes@GREnergy.com</a><<a href="mailto:SHughes@GREnergy.com">mailto:SHughes@GREnergy.com</a>>>>
wrote:</span><br>
<span></span><br>
<span>Hi,</span><br>
<span></span><br>
<span>I have a Cisco 2921 H.323 gateway tied to CUCM 11 with 4 FXO (loop start) ports in a trunk group. Unanswered calls get forwarded to an offsite answering service (hairpinning out of the same set of FXO ports). Ports are setup with "connection plar opx
1000"</span><br>
<span></span><br>
<span>My issue is that ports don't detect when the other end hangs up. When a remote party hangs up, the VoIP phone stays off hook and eventually plays a dial tone, followed by an operator message.</span><br>
<span></span><br>
<span>I suspect that the forwarded calls terminate but both FXO ports in the hairpin stay off hook indefinitely.</span><br>
<span></span><br>
<span>How can I combat this problem? I can reach out to the telco but need to know what to ask for.</span><br>
<span></span><br>
<span>I am located in the US, if that makes a difference. I've read many articles about supervisory disconnection but none really help with troubleshooting steps or timers to tweak.</span><br>
<span></span><br>
<span>-Scott</span><br>
<span></span><br>
<span></span><br>
<span>NOTICE TO RECIPIENT: The information contained in this message from</span><br>
<span>Great River Energy and any attachments are confidential and intended</span><br>
<span>only for the named recipient(s). If you have received this message in</span><br>
<span>error, you are prohibited from copying, distributing or using the</span><br>
<span>information. Please contact the sender immediately by return email and</span><br>
<span>delete the original message.</span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><<a href="mailto:cisco-voip@puck.nether.net">mailto:cisco-voip@puck.nether.net</a>><<a href="mailto:cisco-voip@puck.nether.net">mailto:cisco-voip@puck.nether.net</a><<a href="mailto:cisco-voip@puck.nether.net">mailto:cisco-voip@puck.nether.net</a>>></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span>NOTICE TO RECIPIENT: The information contained in this message from</span><br>
<span>Great River Energy and any attachments are confidential and intended</span><br>
<span>only for the named recipient(s). If you have received this message in</span><br>
<span>error, you are prohibited from copying, distributing or using the</span><br>
<span>information. Please contact the sender immediately by return email and</span><br>
<span>delete the original message.</span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><<a href="mailto:cisco-voip@puck.nether.net">mailto:cisco-voip@puck.nether.net</a>></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
<span></span><br>
<span></span><br>
<span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><<a href="mailto:cisco-voip@puck.nether.net">mailto:cisco-voip@puck.nether.net</a>></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
<span>_______________________________________________</span><br>
<span>cisco-voip mailing list</span><br>
<span><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><<a href="mailto:cisco-voip@puck.nether.net">mailto:cisco-voip@puck.nether.net</a>></span><br>
<span><a href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a></span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span>NOTICE TO RECIPIENT: The information contained in this message from</span><br>
<span>Great River Energy and any attachments are confidential and intended</span><br>
<span>only for the named recipient(s). If you have received this message in </span>
<br>
<span>error, you are prohibited from copying, distributing or using the</span><br>
<span>information. Please contact the sender immediately by return email and</span><br>
<span>delete the original message.</span><br>
<span></span><br>
<span></span><br>
<span></span><br>
</div>
</blockquote>
</body>
</html>