"csim start" command issue

flash2200 · ‎05-12-2008

I am working with a 2811 ISR. The unit is using a single PRI to the PSTN. One small issue is that the customer has only a PVDM16 and therefore not enough DSP's to support the full PRI. I have told them to add another PVDM16. In the mean time I have configured the controller to use only 16 timeslots. When I test the ISR using the "csim start" command to any number I get the error below:

Voice-Lab#csim start 96472891369

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

csim err:csim_do_test invalid major major(16) minor(0)

csim: loop = 1, failed = 0

csim: call attempted = 1, setup failed = 0, tone failed = 0

Voice-Lab#

May 9 13:12:29.470: ISDN Se0/0/0:23 Q931: Applying typeplan for sw-type 0x5 is 0x0 0x0, Called num 6472891369

May 9 13:12:29.470: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8 callref = 0x008A

Bearer Capability i = 0x8090A2

Standard = CCITT

Transfer Capability = Speech

Transfer Mode = Circuit

Transfer Rate = 64 kbit/s

Channel ID i = 0xA98381

Exclusive, Channel 1

Called Party Number i = 0x80, '6472891369'

Plan:Unknown, Type:Unknown

May 9 13:12:29.474: ISDN Se0/0/0:23 Q931: TX -> DISCONNECT pd = 8 callref = 0x008A

Cause i = 0x80AF - Resource unavailable, unspecified

May 9 13:12:29.562: ISDN Se0/0/0:23 Q931: RX <- RELEASE pd = 8 callref = 0x808A

May 9 13:12:29.566: ISDN Se0/0/0:23 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x008A

I have attached my config. Any thoughts as to why this would be happening? TIA!

Brandon Buffin · ‎05-12-2008

What does "show isdn status" indicate?

Brandon

flash2200 · ‎05-12-2008

Up at Layer 2 and 3. (First thing I checked :)

shyamkumar.puppala · ‎07-03-2015

XXXXXX#csim start 91XXXXXXXXX
csim: called number = 91XXXXXXX, loop count = 1 ping count = 0
.
csim: loop = 1, failed = 0
csim: call attempted = 1, setup failed = 0, tone failed = 1

XXXXXXX#

Here tone failed=1.

What does it means whether issue at ISP or at local.

how can we confirm issue at ISP

Carlo Poggiarelli · ‎07-03-2015

Hi.

You have different debug option to use with csim to determine where the issue belongs

In case of isdn debug isdn q931

in case of sip debug ccsip messages

in case of analogue line

debug vpm signal

HTH

Regards

Carlo

Please rate all helpful posts "The more you help the more you learn"

paolo bevilacqua · ‎05-12-2008

They are not taking the call on channel 1, ask telco on which channel they start for your originated calls. You can configure timeslots 16-31 to try anyway.

flash2200 · ‎05-12-2008

Thanks Paolo,

I will check this tomorrow when I am back at the client site.

burb19722 · ‎03-27-2019

this is for paging and isn't working but it seems the csim start command does simulate a call.

md-cumberland-386-rtr-mpls#sh ssh
Connection Version Mode Encryption Hmac         State                 Username
0          2.0     IN   aes256-cbc hmac-sha1    Session started       voyence
0          2.0     OUT aes256-cbc hmac-sha1    Session started       voyence
%No SSHv1 server connections running.
md-cumberland-386-rtr-mpls#debug vpm signal
Voice Port Module signaling debugging is enabled
md-cumberland-386-rtr-mpls#term mon
md-cumberland-386-rtr-mpls#csim start #99
csim: called number = #99, loop count = 1 ping count = 0

csim err:csim_do_test invalid major major(1024) minor(0x0)
csim: loop = 1, failed = 0
csim: call attempted = 1, setup failed = 0, tone failed = 0

md-cumberland-386-rtr-mpls#
Mar 27 10:45:36.291 EDT: htsp_timer_stop3 htsp_setup_req
Mar 27 10:45:36.291 EDT: htsp_process_event: [0/1/3, FXOLS_ONHOOK, E_HTSP_SETUP_REQ]fxols_onhook_setup
Mar 27 10:45:36.291 EDT: [0/1/3] set signal state = 0xC timestamp = 0
Mar 27 10:45:36.291 EDT: htsp_timer - 500 msec
Mar 27 10:45:36.291 EDT: htsp_timer_stop3
Mar 27 10:45:36.291 EDT: htsp_process_event: [0/1/3, FXOLS_WAIT_DIAL_TONE, E_HTSP_RELEASE_REQ]fxols_wait_rel
Mar 27 10:45:36.295 EDT: htsp_timer_stop
Mar 27 10:45:36.295 EDT: [0/1/3] set signal state = 0x4 timestamp = 0
Mar 27 10:45:36.295 EDT: htsp_timer - 2000 msec
Mar 27 10:45:36.567 EDT: htsp_process_event: [0/1/3, FXOLS_GUARD_OUT, E_DSP_SIG_0110]
Mar 27 10:45:38.295 EDT: htsp_process_event: [0/1/3, FXOLS_GUARD_OUT, E_HTSP_EVENT_TIMER]fxols_guard_out_timeout
Mar 27 10:45:38.299 EDT: htsp_process_event: [0/1/3, FXOLS_ONHOOK, E_DSP_SIG_0100]