[cisco-voip] FXO Disconnect Detection

[Esmaeel Saberi]

This link is usefull 😉
https://supportforums.cisco.com/discussion/11127921/fxo-4-voice-ports-always-busy
On Mon, Sep 12, 2016 at 10:34 AM Esmaeel Saberi <esmaeels at gmail.com> wrote:

> Hello
> You must record the sound of busy or congestion tone and define the
> frequency in
> router
>
> On Mon, Sep 12, 2016 at 5:21 AM Sreekanth <sknth.n at gmail.com> wrote:
>
>> Hi Scott,
>>
>> When reaching out to the telco, ask them what kind of disconnect they're
>> doing. Is it:
>> 1. Battery reversal
>> 2. Power denial
>> 3. Supervisory disconnect - tone played by the telco to indicate a
>> disconnect
>>
>> 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.
>> In that case, your DSPs on the router may need a tweak. You can do 2
>> things:
>>
>> 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.
>> 2. Do the ds0-dump on the router and capture the tones, decode them
>> yourself using Audacity and put in the settings.
>>
>> DS0-dump:
>> http://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-system/115749-analyze-pcm-data.html
>>
>> Video for setting up pcm captures and Ds0-dump.
>> https://www.youtube.com/watch?v=HkPjTBvx_YA
>>
>> Cheers!
>>
>> On 12 September 2016 at 05:30, Ryan Huff <ryanhuff at outlook.com> wrote:
>>
>>> Scott,
>>>
>>>
>>> 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.
>>>
>>>
>>> Apologies!
>>>
>>>
>>> Thanks,
>>>
>>>
>>> Ryan
>>>
>>> ------------------------------
>>> *From:* Hughes, Scott GRE-MG <SHughes at GREnergy.com>
>>> *Sent:* Sunday, September 11, 2016 7:13 PM
>>> *To:* Ryan Huff
>>> *Cc:* cisco-voip at puck.nether.net
>>> *Subject:* Re: [cisco-voip] FXO Disconnect Detection
>>>
>>>
>>> :-/ 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.
>>>
>>> Thanks for the suggestion though!
>>>
>>>
>>> On Sep 9, 2016, at 6:21 PM, Ryan Huff <ryanhuff at outlook.com<mailto:
>>> ryanhuff at outlook.com>> wrote:
>>>
>>> EXTERNAL
>>>
>>> You may try enabling support for battery reversal detection on the voice
>>> port;
>>>
>>> voice-port x/x/x
>>> battery-reversal
>>> !
>>>
>>> -Ryan
>>>
>>> On Sep 9, 2016, at 6:57 PM, Hughes, Scott GRE-MG <SHughes at GREnergy.com
>>> <mailto:SHughes at GREnergy.com>> wrote:
>>>
>>> Hi,
>>>
>>> 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"
>>>
>>> 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.
>>>
>>> I suspect that the forwarded calls terminate but both FXO ports in the
>>> hairpin stay off hook indefinitely.
>>>
>>> How can I combat this problem? I can reach out to the telco but need to
>>> know what to ask for.
>>>
>>> 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.
>>>
>>> -Scott
>>>
>>>
>>> NOTICE TO RECIPIENT: The information contained in this message from
>>> Great River Energy and any attachments are confidential and intended
>>> only for the named recipient(s). If you have received this message in
>>> error, you are prohibited from copying, distributing or using the
>>> information. Please contact the sender immediately by return email and
>>> delete the original message.
>>>
>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>>
>>> NOTICE TO RECIPIENT: The information contained in this message from
>>> Great River Energy and any attachments are confidential and intended
>>> only for the named recipient(s). If you have received this message in
>>> error, you are prohibited from copying, distributing or using the
>>> information. Please contact the sender immediately by return email and
>>> delete the original message.
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160912/6c139778/attachment.html>