[c-nsp] ISDN Callback Problems II
Sascha E. Pollok
nsp-list at pollok.net
Fri Apr 15 12:30:18 EDT 2005
Folks,
I have analyzed my ISDN callback-problems further. I guess
is that all this is kinda strange. What's happening is that
I call a router, it is NOT rejecting the call using q931
although it should but it is successfully calling back after
the callback timer expired. Now I finally managed to get
some debugging switched on:
*May 24 10:08:07.401: ISDN BR0/0 Q931: RX <- SETUP pd = 8 callref = 0x01
Sending Complete
Bearer Capability i = 0x8890
Standard = CCITT
Transer Capability = Unrestricted Digital
Transfer Mode = Circuit
Transfer Rate = 64 kbit/s
Channel ID i = 0x89
Calling Party Number i = 0x0183, '004940987654321'
Plan:ISDN, Type:Unknown
Called Party Number i = 0x81, '56565656'
Plan:ISDN, Type:Unknown
*May 24 10:08:07.405: ISDN BR0/0 EVENT: process_rxstate: ces/callid 1/0x3FBB
calltype 1 HOST_INCOMING_CALL
*May 24 10:08:07.405: BR0/0:1 DDR: Caller id 004940987654321 matched to profile
*May 24 10:08:07.405: Di1 DDR: Caller id: Callback server starting to 004940987654321
*May 24 10:08:07.409: ISDN BR0/0 **ERROR**: host_incoming_call: DIALER ERROR 0x1:
b channel 0, call id 0x3FBB
*May 24 10:08:07.409: ISDN BR0/0 EVENT: process_rxstate: ces/callid 1/0x3FBB
calltype 1 HOST_DISCONNECT_ACK
*May 24 10:08:07.413: ISDN BR0/0 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x81
Cause i = 0x8095 - Call rejected
*May 24 10:08:08.150: ISDN BR0/0 Q931: RX <- CONNECT_ACK pd = 8 callref = 0x01
*May 24 10:08:27.406: DDR: Callback timer expired
*May 24 10:08:27.406: Di1 DDR: beginning callback to 004940987654321
Ok so what's happening here? From my point of view it looks like it is
correctly rejecting the call (TX -> RELEASE_COMP Cause 0x8095) but then it
still receives a CONNECT_ACK from the switch as if it answered the call
which it did not! (as far as i can see). I expected something like
"RX <- DISCONNECT_ACK" but I find "RX <- CONNECT_ACK" quite surprising.
To my original post I received comments about my dialer-list and stuff
like that which I would like to thank for but my guess is that here is
something else behaving strange.
On the calling-router's side, I see that the 64k connection is coming
up but it can't get any data through (which would match this strange
output).
Is this some kind of .. unearthly event or just something I am misreading?
Thanks
Sascha
More information about the cisco-nsp
mailing list