Doubt about Debug vpm signal

Unanswered Question
Aug 19th, 2008

Hi!

I turn on the debug vpm singal

I obtain this events:

RT3845VOICEGWMEX6.40#csim star 3050

csim: called number = 3050, loop count = 1 ping count = 0

*Aug 20 00:29:03.135: htsp_timer_stop3 htsp_setup_req

*Aug 20 00:29:03.135: htsp_process_event: [2/0:0(5), R2_Q421_IDLE, E_HTSP_SETUP_REQ]

*Aug 20 00:29:03.135: r2_q421_seize(2/0:0(5)) E_HTSP_SETUP_REQ DNIS=3050 ANI=

*Aug 20 00:29:03.135: r2_q421_seize(2/0:0(5)) Tx SEIZUREvnm_dsp_set_sig_state:[R2 Q.421 2/0:0(5)] set signal state = 0x0

*Aug 20 00:29:03.135: htsp_timer - 5000 msec

*Aug 20 00:29:03.267: htsp_process_event: [2/0:0(5), R2_Q421_OG_SEIZE, E_DSP_SIG_1100]

*Aug 20 00:29:03.267: r2_q421_seize_ack(2/0:0(5)) Rx SEIZE ACK

*Aug 20 00:29:03.267: htsp_timer_stop

*Aug 20 00:29:03.267: r2_reg_start_dialing(2/0:0(5))

*Aug 20 00:29:03.271: r2_reg_process_event: [2/0:0(5), R2_REG_IDLE, E_R2_REG_START_DIAL(91)]

*Aug 20 00:29:03.271: r2_reg_start_dial_delay(2/0:0(5)) dialout delay 200

*Aug 20 00:29:03.271: r2_reg_timer(2/0:0(5)) 200 msec

*Aug 20 00:29:03.471: r2_reg_process_event: [2/0:0(5), R2_REG_IDLE, E_R2_REG_EVENT_TIMER(84)]

*Aug 20 00:29:03.471: r2_reg_start_dial(2/0:0(5))

*Aug 20 00:29:03.471: R2 Outgoing Voice(2/0): DSX (E1 2/0:4): STATE: R2_OUT_IDLE R2 Got Event R2_START

*Aug 20 00:29:03.471: r2_reg_generate_digits(2/0:0(5)): Tx digit '#'

*Aug 20 00:29:03.471: r2_reg_generate_digits(2/0:0(5)): Tx digit '3'

*Aug 20 00:29:03.643: htsp_digit_ready_up(2/0:0(5)): Rx digit='1'

*Aug 20 00:29:03.643: R2 Outgoing Voice(2/0): DSX (E1 2/0:4): STATE: R2_OUT_PROCESS_A R2 Got Event 1

*Aug 20 00:29:03.643: r2_reg_generate_digits(2/0:0(5)): Tx digit '#'

*Aug 20 00:29:03.719: htsp_digit_ready(2/0:0(5)): Rx digit='#'

*Aug 20 00:29:03.719: R2 Outgoing Voice(2/0): DSX (E1 2/0:4): STATE: R2_OUT_PROCESS_A R2 Got Event R2_TONE_OFF

*Aug 20 00:29:03.719: r2_reg_generate_digits(2/0:0(5)): Tx digit '0'

*Aug 20 00:29:03.875: htsp_digit_ready_up(2/0:0(5)): Rx digit='1'

*Aug 20 00:29:03.875: R2 Outgoing Voice(2/0): DSX (E1 2/0:4): STATE: R2_OUT_PROCESS_A R2 Got Event 1

*Aug 20 00:29:03.875: r2_reg_generate_digits(2/0:0(5)): Tx digit '#'

*Aug 20 00:29:03.971: htsp_digit_ready(2/0:0(5)): Rx digit='#'

*Aug 20 00:29:03.971: R2 Outgoing Voice(2/0): DSX (E1 2/0:4): STATE: R2_OUT_PROCESS_A R2 Got Event R2_TONE_OFF

*Aug 20 00:29:03.971: r2_reg_generate_digits(2/0:0(5)): Tx digit '5'

*Aug 20 00:29:04.111: htsp_digit_ready_up(2/0:0(5)): Rx digit='1'

*Aug 20 00:29:04.111: R2 Outgoing Voice(2/0): DSX (E1 2/0:4): STATE: R2_OUT_PROCESS_A R2 Got Event 1

*Aug 20 00:29:04.111: r2_reg_generate_digits(2/0:0(5)): Tx digit '#'

*Aug 20 00:29:04.191: htsp_digit_ready(2/0:0(5)): Rx digit='#'

*Aug 20 00:29:04.191: R2 Outgoing Voice(2/0): DSX (E1 2/0:4): STATE: R2_OUT_PROCESS_A R2 Got Event R2_TONE_OFF

*Aug 20 00:29:04.191: r2_reg_generate_digits(2/0:0(5)): Tx digit '0'

*Aug 20 00:29:04.323: htsp_digit_ready_up(2/0:0(5)): Rx digit='3'

*Aug 20 00:29:04.323: R2 Outgoing Voice(2/0): DSX (E1 2/0:4): STATE: R2_OUT_PROCESS_A R2 Got Event 3

*Aug 20 00:29:04.323: r2_reg_generate_digits(2/0:0(5)): Tx digit '#'

*Aug 20 00:29:04.423: htsp_digit_ready(2/0:0(5)): Rx digit='#'

*Aug 20 00:29:04.423: R2 Outgoing Voice(2/0): DSX (E1 2/0:4): STATE: R2_OUT_PROCESS_B R2 Got Event R2_TONE_OFF

*Aug 20 00:29:04.423: r2_reg_generate_digits(2/0:0(5)): Tx digit '2'

*Aug 20 00:29:04.559: htsp_digit_ready_up(2/0:0(5)): Rx digit='1'

*Aug 20 00:29:04.559: R2 Outgoing Voice(2/0): DSX (E1 2/0:4): STATE: R2_OUT_PROCESS_B R2 Got Event 1

*Aug 20 00:29:04.559: r2_reg_generate_digits(2/0:0(5)): Tx digit '#'

*Aug 20 00:29:04.643: htsp_digit_ready(2/0:0(5)): Rx digit='#'

Do you know a link of Cisco where I can found the meaning of the this debug???

Thanks

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (0 ratings)
raul-santiago Tue, 08/19/2008 - 16:49

We would to know what do the Rx digit '1'and Tx digit '#' mean, for example:

*Aug 20 00:29:03.643: htsp_digit_ready_up(2/0:0(5)): Rx digit='1'

:

*Aug 20 00:29:03.643: r2_reg_generate_digits(2/0:0(5)): Tx digit '#'

Which appears between the digit 3 and 0...

Thanks...

Jaime Valencia Tue, 08/19/2008 - 18:50

we don't have links that explain what each line on a debug means, this is all the info available at CCO

debug vpm signal

http://www.cisco.com/en/US/products/sw/iosswrel/ps1826/products_feature_guide_chapter09186a0080087097.html#xtocid6

you can buy this book if you need further explanation:

Troubleshooting Cisco IP Telephony By Paul Giralt

Cisco Voice Gateways and Gatekeepers may also give you more information

HTH

java

if this helps, please rate

pcameron Sun, 08/24/2008 - 19:21

The call flow is as follows -

The router sent a Seize ABCD bit signal

The Telco responded with Seize ACK

The router then went into R2 register processing, meaning it sends particular tones and expects certain responses from the exchange.

When the debugs print out TX and RX '#', this actually is a IOS description for tone off, or no tone generated or received.

This relates to the way E1R2 works in that each side is Compelled to send a tone until the other side responds with an ACK tone, then they stop sending this particular tone.

To send the Call out, the router sends the 1st DNIS digit until it recieves the ack tone. Then it stops sending the digit, the exchange stops sending the ack tone and it then repeats the process for all the digits.

So in the trace above, the tones went as follows -

TX silence

TX 3 (1st DNIS digit)

RX 1 (Telco ack for 1st DNIS digit)

TX silence

RX silence

TX 0 (2nd DNIS digit)

RX 1 (Telco ack for 2nd DNIS digit)

TX silence

RX silence

TX 5 (3rd DNIS digit)

RX 1 (Telco ack for 3rd DNIS digit)

TX silence

RX silence

TX 0 (4th DNIS digit)

RX 3 (Telco has enough digits to route the call, so sends sends B3 tone

TX silence

RX silence

TX 2 (Router sends category 2 signal)

RX 1 (Telco sends B1 - answer signal)

TX silence

RX silence

This call looks like it worked fine - the called number was 3050 and it appeared to be accepted by the telco and was answered.

The problem with E1 R2 is that there are many different country specific variants and a debug for one country does not necessarily apply to another. In the case above, it appears the E1 R2 was running the Telmex variant.

Actions

Login or Register to take actions

This Discussion

Posted August 19, 2008 at 4:45 PM
Stats:
Replies:3 Avg. Rating:
Views:1458 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard