1760V T1 integration with Norstar

[johutchins]

Hi,

One out of 2 calls from a IP phone to this Norstar results in a busy. Calls from the Norstar to the IP phone never a problem.

I running 12.3.4(T3) IOS.

Here is a debug vpm signal:

*Mar 22 18:06:19.958: htsp_timer_stop3 htsp_setup_req

*Mar 22 18:06:19.966: htsp_process_event: [0/0:0(20), EM_ONHOOK, E_HTSP_SETUP_RE

Q]em_onhook_setup

*Mar 22 18:06:19.966: em_offhook (0)[recEive and transMit0/0:0(20)] set signal s

tate = 0x8

*Mar 22 18:06:19.966: htsp_process_event: [0/0:0(20), EM_BRANCH, EM_EVENT_WINK]

*Mar 22 18:06:19.970: em_start_timer: 550 ms

*Mar 22 18:06:19.970: htsp_timer - 550 msec

*Mar 22 18:06:20.178: htsp_process_event: [0/0:0(20), EM_WAIT_WINKUP, E_DSP_SIG_

1100]em_wink_offhook

*Mar 22 18:06:20.178: em_stop_timers

*Mar 22 18:06:20.178: htsp_timer_stop

*Mar 22 18:06:20.178: em_start_timer: 1200 ms

*Mar 22 18:06:20.178: htsp_timer - 1200 msec

*Mar 22 18:06:20.391: htsp_process_event: [0/0:0(20), EM_WAIT_WINKDOWN, E_DSP_SI

G_0000]em_wink_onhook

*Mar 22 18:06:20.391: em_stop_timers

*Mar 22 18:06:20.391: htsp_timer_stop htsp_wink_ind

*Mar 22 18:06:20.391: htsp_timer - 70 msec

*Mar 22 18:06:20.463: htsp_process_event: [0/0:0(20), EM_WAIT_DIALOUT_DELAY, E_H

TSP_EVENT_TIMER]em_imm_send_digits em_send_digits htsp_dial

*Mar 22 18:06:22.883: htsp_process_event: [0/0:0(20), EM_WAIT_DIAL_DONE, E_DSP_D

IALING_DONE]em_offhook_digit_done

*Mar 22 18:06:22.883: htsp_timer_stop2 htsp_progress

*Mar 22 18:06:22.883: htsp_timer2 - 850 msechtsp_call_bridged

*Mar 22 18:06:23.079: htsp_process_event: [0/0:0(20), EM_WAIT_FOR_ANSWER, E_HTSP

_VOICE_CUT_THROUGH]

*Mar 22 18:06:23.079: htsp_timer_stop2 term no mon

Any thoughs?

[Chester Rieman]

Looks like the call actually connects:

tsp_call_bridged

From just looking at this, it looks like the busy signal is coming from the norstar. Is it a regular busy or fast busy(reorder)? When you are hearing the busy signal. do a 'show call voice summ' to see what state the call is in. Are both sides set for E&M wink?

[johutchins]

Both sides are set for e&m-wink-start.

It is a regular busy... what's wierd is if you wait 5 to 10 seconds, you hear dialtone again... you can't dial anything and if you wait long enough again, busy.

A show voice port sum shows that the outgoing is seized, but the incoming is idle (we never see it go seized).

Sometimes it might be the 4th call on the trunk, sometimes it is the only only call on the trunk when this condition occurs.