[cisco-voip] "show voice trace" and "battery-reversal answer"

[Lawrence E. Bakst]

At 9:37 PM -0500 11/9/05, Wes Sisk wrote:
>power denial is just disconnect supervision. this is normal for residential loopstart lines

OK, but I only see this in failure case. See the traces below. I have the following simple outbound dial-peer:

dial-peer voice 701 pots
 description dial 7 for line #2
 destination-pattern 7
 port 0/0/5
!

With the "bad cable" sometimes when I dialed 7 i hear the line go off-hook, it starts to seize (maybe I hear dial tone for < 1s) and then it fails for some reason and goes back on-hook. The cable seemed to work fine with an analog phone on the same line. The hardware is NM-HDA, with the old FXO expansion cards.

Perhaps the FXO port is thinking that the line power drop or reversed with the bad cable?

You shouldn't spend too much more of your valuable time on a bad cable problem that I already fixed. I wasn't even going to post but then I though I saw a similarity to the guy who was having a problem with his FXO/plar and I thought it might be relevant.

>
>"battery-reversal answer" addresses the case of an inbound call is processing, originating from the PSTN, if the originating party disconnects the call 1st, the FXO port stays up. The PSTN uses battery reversal to attempt to signal call disconnect during the ringin state.
>
>Another customer reported that disconnect was still not being detect. Resolution was "supervisory disconnect dualtone mid-call" and "timeouts
>
>answer-release to 1" solved the problem. After adding this config battery reversal at ringin was properly detected.

Thanks for these great answers.

>
>
>As for the bits 0110, 0100, etc.  these are basically the ABCD bits used for T1-CAS (T1, but not pri) just masked to match the state transitions associated with analog signaling.
>
>What version of IOS are you using on this router?

I have a 3640 which is running IOS 12.3(14)T3 and CME 3.3. I believe I am tied into this version by the CME 3.3, correct?

Best,

leb

>
>/Wes
>
>Lawrence E. Bakst wrote:
>
>>1. I had a problem where an outbound voice pots dial-peer fails to "seize" a FXO line. Sometimes I hear dial tone for a very short period, sometimes not at all. Changing the cable fixed it.
>>
>>In the failure case I saw the following differences in "show voice call trace":
>>
>>1385785.956 (FXOLS_OFFHOOK, E_DSP_SIG_0110) ->
>>1385786.232 (FXOLS_CONNECT, E_DSP_SIG_0100) ->
>>1385786.252 (FXOLS_POWER_DENIAL, E_HTSP_RELEASE_REQ) ->
>>
>>Anyone have any info on the states and events for these state machines and what these mean? Cisco and Google have nothing. "Power Denial" and "E_DSP_SIG_0110" would seem to be the clues. The port in question was configured as follows:
>>
>>voice-port 0/0/5
>> trunk-group outbound 3
>> translation-profile incoming add-leading-one
>> battery-reversal answer
>> output attenuation 0
>> no vad
>> connection plar opx 202
>> impedance complex1
>> caller-id enable
>>!
>>
>>See more detailed voice trace info below.
>>
>>
>>2. Does "battery-reversal answer" make sense for a residential ground start POTS line?
>>
>>Best,
>>
>>leb
>>
>>
>>FAILURE CASES:
>>0/0/5 State Transitions: timestamp (state, event) -> (state, event) ...
>>1385785.684 (FXOLS_ONHOOK, E_HTSP_SETUP_REQ) ->
>>1385785.684 (FXOLS_WAIT_DIAL_TONE, E_HTSP_EVENT_TIMER) ->
>>1385785.688 (FXOLS_WAIT_DIAL_DONE, E_DSP_DIALING_DONE) ->
>>1385785.712 (FXOLS_WAIT_CUT_THRU, E_HTSP_VOICE_CUT_THROUGH) ->
>>1385785.956 (FXOLS_OFFHOOK, E_DSP_SIG_0110) ->
>>1385786.232 (FXOLS_CONNECT, E_DSP_SIG_0100) ->
>>1385786.252 (FXOLS_POWER_DENIAL, E_HTSP_RELEASE_REQ) ->
>>1385788.248 (FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER) ->
>>1385788.248 (FXOLS_ONHOOK, E_DSP_SIG_0100) ->
>>chatter#
>>
>>chatter#show voice trace 0/0/5
>>0/0/5 State Transitions: timestamp (state, event) -> (state, event) ...
>>1386742.000 (FXOLS_ONHOOK, E_HTSP_SETUP_REQ) ->
>>1386742.000 (FXOLS_WAIT_DIAL_TONE, E_HTSP_EVENT_TIMER) ->
>>1386742.000 (FXOLS_WAIT_DIAL_DONE, E_DSP_DIALING_DONE) ->
>>1386742.004 (FXOLS_OFFHOOK, E_DSP_SIG_0100) ->
>>1386742.028 (FXOLS_OFFHOOK, E_HTSP_VOICE_CUT_THROUGH) ->
>>1386742.272 (FXOLS_OFFHOOK, E_DSP_SIG_0110) ->
>>1386742.560 (FXOLS_CONNECT, E_DSP_SIG_0100) ->
>>1386742.584 (FXOLS_POWER_DENIAL, E_HTSP_RELEASE_REQ) ->
>>1386744.580 (FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER) ->
>>1386744.580 (FXOLS_ONHOOK, E_DSP_SIG_0100) ->
>>chatter#
>>
>>WORKING CASES:
>>chatter#show voice trace 0/0/5
>>0/0/5 State Transitions: timestamp (state, event) -> (state, event) ...
>>1385832.944 (FXOLS_ONHOOK, E_HTSP_SETUP_REQ) ->
>>1385832.948 (FXOLS_WAIT_DIAL_TONE, E_HTSP_EVENT_TIMER) ->
>>1385832.948 (FXOLS_WAIT_DIAL_DONE, E_DSP_DIALING_DONE) ->
>>1385832.972 (FXOLS_WAIT_CUT_THRU, E_HTSP_VOICE_CUT_THROUGH) ->
>>1385836.000 (FXOLS_OFFHOOK, E_HTSP_RELEASE_REQ) ->
>>1385837.996 (FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER) ->
>>1385837.996 (FXOLS_ONHOOK, E_DSP_SIG_0100) ->
>>chatter#
>>
>>chatter#show voice trace 0/0/5
>>0/0/5 State Transitions: timestamp (state, event) -> (state, event) ...
>>1386742.000 (FXOLS_ONHOOK, E_HTSP_SETUP_REQ) ->
>>1386742.000 (FXOLS_WAIT_DIAL_TONE, E_HTSP_EVENT_TIMER) ->
>>1386742.000 (FXOLS_WAIT_DIAL_DONE, E_DSP_DIALING_DONE) ->
>>1386742.004 (FXOLS_OFFHOOK, E_DSP_SIG_0100) ->
>>1386742.028 (FXOLS_OFFHOOK, E_HTSP_VOICE_CUT_THROUGH) ->
>>1386742.272 (FXOLS_OFFHOOK, E_DSP_SIG_0110) ->
>>1386742.560 (FXOLS_CONNECT, E_DSP_SIG_0100) ->
>>1386742.584 (FXOLS_POWER_DENIAL, E_HTSP_RELEASE_REQ) ->
>>1386744.580 (FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER) ->
>>1386744.580 (FXOLS_ONHOOK, E_DSP_SIG_0100) ->
>>
>>
>>_______________________________________________
>>cisco-voip mailing list
>>cisco-voip at puck.nether.net
>>https://puck.nether.net/mailman/listinfo/cisco-voip
>>