Outbound calls not working

[Leonardo Santana]

Hello,

We have a E1 R2 and outbound calls are not being established. Inbound calls are ok.

ios:c2951-universalk9-mz.SPA.152-4.M7.bin

Call Flow: IP Phone -> CUCM -> SIP TRUNK -> Voice Gateway -> E1 R2-> TELCO

The debug vpm signal is attached.

What could be the issue?

I have already tested this E1 R2 link in two differents routers.

Regards

Leonardo Santana

[Dennis Mink]

Leonardo,

looking at your debug it seems as if you are dialing "#2#2#1#......" ending with a * ,after this the disconnect takes place, as if options on an IVR are being keyed in.  where does that come from?

[dsobrinho]

Hi  Dennis,

I agree with you, this is strange.

The number dialed was 2217-8631 from extension 3784

E_HTSP_SETUP_REQ DNIS=22178631 ANI=3784

Jan 19 00:18:07.900: r2_reg_generate_digits(0/0/0:0(1)): Tx digit '3'
Jan 19 00:18:08.000: htsp_digit_ready_up(0/0/0:0(1)): Rx digit='1'
Jan 19 00:18:08.000: R2 Outgoing Voice(0/0): DSX (E1 0/0/0:0): STATE: R2_OUT_PROCESS_A R2 Got Event 1
Jan 19 00:18:08.000: r2_reg_generate_digits(0/0/0:0(1)): Tx digit '#'
Jan 19 00:18:08.120: htsp_digit_ready(0/0/0:0(1)): Rx digit='#'
Jan 19 00:18:08.120: R2 Outgoing Voice(0/0): DSX (E1 0/0/0:0): STATE: R2_OUT_PROCESS_A R2 Got Event R2_TONE_OFF
Jan 19 00:18:08.120: r2_reg_generate_digits(0/0/0:0(1)): Tx digit '1'
Jan 19 00:18:08.220: htsp_digit_ready_up(0/0/0:0(1)): Rx digit='1'
Jan 19 00:18:08.220: R2 Outgoing Voice(0/0): DSX (E1 0/0/0:0): STATE: R2_OUT_PROCESS_A R2 Got Event 1
Jan 19 00:18:08.220: r2_reg_generate_digits(0/0/0:0(1)): Tx digit '#'
Jan 19 00:18:08.340: htsp_digit_ready(0/0/0:0(1)): Rx digit='#'
Jan 19 00:18:08.340: R2 Outgoing Voice(0/0): DSX (E1 0/0/0:0): STATE: R2_OUT_PROCESS_A R2 Got Event R2_TONE_OFF
Jan 19 00:18:08.340: r2_reg_generate_digits(0/0/0:0(1)): Tx digit '*'
Jan 19 00:18:08.448: htsp_process_event: [0/0/0:0(1), R2_Q421_OG_SEIZE_ACK, E_DSP_SIG_1000]
Jan 19 00:18:08.448: r2_q421_seize_to(0/0/0:0(1)) Tx CLEAR FWDvnm_dsp_set_sig_state:[R2 Q.421 0/0/0:0(1)] set signal state = 0x8
Jan 19 00:18:08.448: htsp_timer - 1000 msec
Jan 19 00:18:08.448: r2_reg_channel_disconnected(0/0/0:0(1))

[dsobrinho]

Hi Leonardo,

Check the link below. The problem description is the same.The PSTN had configured the circuit as unidirectional configuration.

Like this:

1-15 - incoming calls

17-31 - outgoing calls

https://supportforums.cisco.com/discussion/12178771/outgoing-calls-e1-r2-digital-dont-work

Best regards,

Daniel

[abdel-moniem]

Hi Leandro, 

This might be a bidirectional trunk not setup from the carrier as Daniel's suggestion. I believe as the digits are actually after the Wink being received with acknowledgment  of each digits suggests it might be an outgoing trunk but to double check. However the final "*" is a weird item as well as after that the Caller ID should be sent after the DNIS. Could you post the  cas custom configuration, IOS Version, and also deb vtsp all

Best Regards

Moniem

[Leonardo Santana]

Hello all,

We change for ISDN and it works.

Regards

Leonardo Santana

[dsobrinho]

Hi Leonardo,
 

I am glad know that problem was resolved with this move.

Have nice day

Daniel Sobrinho

[abdel-moniem]

Hello Leandro,

I believe if you get the chance to go for a Digital ISDN PRI alternative option to E1 R2 it is always a better controllable and globally standaridised option. Great that your business is restored.

For my curiosity, would it be possible to know the cas-custom options you configured prior. If not, I am glad that everything is ok

Best Regards,

MonieM

[Leonardo Santana]

Hello Abdel,

This was the E1 R2 config before the change:

controller E1 0/0/0
 framing NO-CRC4 
 line-termination 75-ohm
 ds0-group 0 timeslots 1-15,17-31 type r2-digital r2-compelled ani
 cas-custom 0
  country brazil
  metering
  debounce-time 10
  answer-signal group-b 1
  dnis-digits min 1 max 4
  dnis-complete

This is the new ISDN PRI config that itis working:

controller E1 0/0/0
 framing NO-CRC4
 line-termination 75-ohm
 pri-group timeslots 1-31

interface Serial0/0/0:15
 no ip address
 encapsulation hdlc
 isdn switch-type primary-net5
 isdn incoming-voice voice
 no cdp enable

Regards

Leonardo Santana

[abdel-moniem]

Dear Leandro

Thanks for posting the Configuration.

I am not sure, but I think the default configuration for Brazil was going to make a difference here as most of the carriers accesspt Category 2 and I dont think they need dnis-complete (or metering option) (I think this is the "*" at the end but not sure).

My suggestion was going to be having the following:

controller E1 0/0/0
framing NO-CRC4
line-termination 75-ohm
ds0-group 0 timeslots 1-15,17-31 type r2-digital r2-compelled ani
cas-custom 0
  country brazil use-default
  category 2
  answer-signal group-b 1

However, I believe the ISDN PRI still a better option and easy to manage.
Thanks and Best regards
MonieM