[cisco-voip] Call out FXO port gives fxols_power_denial_proc

[Nick Matthews]

Depends on your preference.  There aren't too many options here and
these scenarios can go nowhere pretty quick.  Generally TAC will have
you try some commands:

supervisory disconnect anytone
no supervisory disconnect signal
no battery-reversal

Also try:

different port, if the problem is different the problem is with
whichever piece the problem follows
a 2 wire cable instead of 4 cable

If none of this works, TAC will ask for you to contact the provider.
They will probably send a buttset out and tell you everything is fine.

It looks like the provider is sending an onhook signal, for what it's worth.

-nick

On Wed, Sep 9, 2009 at 4:45 PM, Jason Aarons
(US)<jason.aarons at us.didata.com> wrote:
> No luck adding the no sup-disconnect signal...
>
> Would next step be trouble ticket with telco or TAC case?
>
> -----Original Message-----
> From: matthn at gmail.com [mailto:matthn at gmail.com] On Behalf Of Nick Matthews
> Sent: Wednesday, September 09, 2009 12:34 PM
> To: Jason Aarons (US)
> Cc: cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] Call out FXO port gives fxols_power_denial_proc
>
> Try:
>
> voice-port 2/0/8
> no supervisory-disconnect signal
>
> There's a good chance you're detecting a power denial and hanging up
> the call.  The reason the buttset isn't an accurate test for this
> scenario is because your buttset will not disconnect on a power
> denial.
>
> If this configuration does fix your problem, it is only indicative
> that you have other problems.
>
> -nick
>
> On Wed, Sep 9, 2009 at 12:16 PM, Jason Aarons
> (US)<jason.aarons at us.didata.com> wrote:
>> I make a test call and via debug vpm signal I see the following on 2821/FXO
>> controlled via MGCP. If I plug my buttset into this Bell 1FB/POTs line I can
>> make calls fine.
>>
>>
>>
>> ROUTER-2821-01#
>>
>> Sep  9 16:12:56.251: htsp_timer_stop3
>> htsp_setup_req
>>
>> Sep  9 16:12:56.255: htsp_process_event: [2/0/8, FXOLS_ONHOOK,
>> E_HTSP_SETUP_REQ]f
>>
>> xols_onhook_setup
>>
>> Sep  9 16:12:56.255: [2/0/8] set signal state = 0xC timestamp =
>> 0
>>
>> Sep  9 16:12:56.255: htsp_timer - 1300
>> msec
>>
>> Sep  9 16:12:56.507: htsp_process_event: [2/0/8, FXOLS_WAIT_DIAL_TONE,
>> E_DSP_SIG_
>>
>> 1100]fxols_power_denial_proc
>>
>> Sep  9 16:12:56.507: htsp_timer2 - 1000
>> msec
>>
>> Sep  9 16:12:56.507:
>> htsp_timer_stop
>>
>> Sep  9 16:12:57.507: htsp_process_event: [2/0/8, FXOLS_WAIT_DIAL_TONE,
>> E_HTSP_EVE
>>
>> NT_TIMER2]fxols_timer2_proc
>>
>> Sep  9 16:12:57.507:
>> htsp_timer_stop
>>
>> Sep  9 16:12:57.507: htsp_timer_stop2
>>
>>
>> Sep  9 16:12:57.507: [2/0/8] set signal state = 0x4 timestamp =
>> 0
>>
>> Sep  9 16:12:57.511: htsp_process_event: [2/0/8, FXOLS_ONHOOK,
>> E_HTSP_RELEASE_REQ
>>
>> ]fxols_onhook_release
>>
>>
>> ROUTER-2821-01#
>>
>> ________________________________
>>
>> 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.
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
> -----------------------------------------
> 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.
>