[Asterisk-Users] Cisco 3620 PRI and Asterisk

Benjamin on Asterisk Mailing Lists benjk.on.asterisk.ml at gmail.com
Wed Sep 29 10:47:35 MST 2004


On Wed, 29 Sep 2004 11:32:44 -0600, Jesse Tyler <jtyler at goarctic.com> wrote:
> Here is an error from my router
> 15:40:45: ISDN Se1/0:23 SERROR: L3_GetUser_NLCB: EVENT 0X45 No NLCB 2
> 15:40:45: ISDN Se1/0:23 **ERROR**: Ux_BadMsg: Invalid Message for call
> state 9, call id 0x253, call ref 0x83DF, event 0x62
> 15:40:45: ISDN Se1/0:23 SERROR: CCPRI_Go: call id 0x254 event 0x57 No
> ccb Source->HOST
> 15:40:45: ISDN  **ERROR**: Module-l3_sdl_u  Function-U19_BadMsg
> Error-Bad message received.
> 15:40:45: ISDN Se1/0:23 SERROR: CCPRI_Go: call id 0x253 event 0x57 No
> ccb Source->HOSTConnection closed by foreign host.
> 
> Here is some data from a SNIFF on port 5060
> 3648.406191 192.168.10.1 -> 192.168.10.2 SIP Status: 200 OK
> 3659.554288 192.168.10.2 -> 192.168.10.1 SIP Request: OPTIONS
> sip:192.168.10.1
> 3659.573166 192.168.10.1 -> 192.168.10.2 SIP/SDP Status: 200 OK, with
> session description
> 3684.730069 192.168.10.1 -> 192.168.10.2 SIP/SDP Request: INVITE
> sip:[my_hidden_phone_number]@192.168.10.2:5060, with session
> description
> 3684.730479 192.168.10.2 -> 192.168.10.1 SIP Status: 100 Trying
> 3684.732364 192.168.10.2 -> 192.168.10.1 SIP Status: 180 Ringing
> 3685.077268 192.168.10.1 -> 192.168.10.2 SIP Request: CANCEL
> sip:[my_hidden_phone_number]@192.168.10.2:5060
> 3685.077617 192.168.10.2 -> 192.168.10.1 SIP Status: 200 OK
> 
> Asterisk
>      -- Executing Goto("SIP/192.168.10.1-0819f7d8", "350|1") in new stack
>      -- Goto (default,350,1)
>      -- Executing Dial("SIP/192.168.10.1-0819f7d8", "SIP/350|20|tr") in
> new stack
>      -- Called 350
>    == Spawn extension (default, 350, 1) exited non-zero on
> 'SIP/192.168.10.1-0819f7d8'
> 
> 350 is my extension on Asterisk
> 192.168.10.1 is the router with the PRI installed and running
> 192.168.10.2 is the asterisk box

Apparently, the Cisco is getting something back from Asterisk which it
thinks is a bad message and as a result of that it sends a CANCEL
request back to Asterisk.

Although I am not sure what that bad message might be, judging by the
fact that the last message Asterisk sent out to the Cisco shortly
before was the RINGING message, I take a guess that there might be
something funny with that. Following that thought, I would try the
dial command without the "r" and also without "t" and without "tr" and
see if that makes any difference.

rgds
benjk

-- 
Sunrise Telephone Systems, 9F Shibuya Daikyo Bldg., 1-13-5 Shibuya,
Tokyo, Japan.

NB: Spam filters in place. Messages unrelated to the * mailing lists
may get trashed.



More information about the asterisk-users mailing list