10-15-2002 01:22 AM - edited 03-02-2019 02:04 AM
I have a Cisco AS5300 running IOS 12.2.10a. We do use callback.
The problem is that it calls back to the wrong number adding extra one digit at the end of the specified number !?
For instance, I call in from 9280044,
---
Oct 15 11:34:59.346: %ISDN-6-CONNECT: Interface Serial0:29 is now connected to 9280044
---
it connects and asks for callback number, I put 9280044 (Windows setup: Set by caller). It then disconnects and my Windows stays in "waiting for callback" and never gets the real callback !
When I look at "debug isdn q931" I see something strange :
---
Oct 15 11:35:15.858: Called Party Number i = 0xA1, '92800449', Plan:ISDN, Type:National
---
As You see from the log, there is an extra digit - in this case "9" at the end of the dialed number, I've also seen "4" and "0", maybe others would appear also.
Any idea ?
10-15-2002 06:45 AM
Can you paste some of your configs, as well as trace of debug isdn q931 (full trace).
Also please specify the IOS version.
10-15-2002 11:04 PM
A bit more explanation :
We have 3 pools in our AS5300 -
1) dial to 9310000 without callback;
2) dial to 7773264 and do analog call back;
3) dial to 9310003 and do ISDN V.110 callback.
The problem exists only in third option. Here is the callback script, line and some other configs :
**************************************
version 12.2
boot system flash c5300-is-mz.122-10a.bin
!
spe 1/0 1/9
firmware location mica-modem-pw.2.9.2.0.bin
!
resource-pool enable
!
resource-pool group resource Mica_1/10-19
range port 1/10 1/19
!
resource-pool profile customer LMT-Intranet-isdn
limit base-size all
limit overflow-size 0
resource Mica_1/10-19 V110
dnis group LMT-Intranet-isdn
!
chat-script dialup "" "atdt\T" TIMEOUT 60 CONNECT \c
chat-script offhook "" "ATH1" OK \c
chat-script mica-callback ABORT ERROR ABORT BUSY "" "ATZ" OK "ATDT\T" TIMEOUT 60 CONNECT \c
chat-script mica-v110 ABORT ERROR ABORT BUSY "" "ATZ" OK "ATS29=8S57=38400" OK "ATDI \T" TIMEOUT 60 CONNECT \c
!
interface Serial0:15
no ip address
encapsulation ppp
isdn switch-type primary-net5
isdn incoming-voice modem
isdn map address .* plan isdn type national
isdn calling-number 7773264
isdn outgoing-voice info-transfer-capability 3.1kHz-audio
no isdn v110 padding
no fair-queue
compress mppc
no cdp enable
!
interface Group-Async2
ip unnumbered Ethernet0
no ip proxy-arp
encapsulation ppp
ip tcp header-compression
no ip mroute-cache
async mode interactive
peer default ip address dhcp
no fair-queue
compress mppc
ppp callback accept
ppp authentication ms-chap LMT-Intr-authen
ppp authorization LMT-Intr-author
ppp accounting LMT-Intr-account
group-range 11 20
!
dialer dnis group LMT-Intranet-isdn
number 003
!
line 11 20
access-class 5 in
no flush-at-activation
script modem-off-hook offhook
script callback mica-v110
modem InOut
transport preferred none
transport input all
transport output telnet
autoselect during-login
autoselect ppp
********************************
And the full ISDN Q931 debug (with some extra lines):
as-staff#debug isdn q931
ISDN Q931 packets debugging is on
as-staff#term monit
as-staff#
Oct 16 09:32:56.454: %LINK-5-CHANGED: Interface Async46, changed state to reset
Oct 16 09:32:57.454: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async46, changed state to down
as-staff#
Oct 16 09:33:01.454: %LINK-3-UPDOWN: Interface Async46, changed state to down
Oct 16 09:33:02.206: ISDN Se0:15: RX <- SETUP pd = 8 callref = 0x5953
Oct 16 09:33:02.206: Bearer Capability i = 0x8890214D06BB
Oct 16 09:33:02.206: Channel ID i = 0xA98382
Oct 16 09:33:02.206: Calling Party Number i = 0x21, 0x81, '9280044', Plan:ISDN, Type:National
Oct 16 09:33:02.210: Called Party Number i = 0xA1, '003', Plan:ISDN, Type:National
Oct 16 09:33:02.210: Low Layer Compat i = 0x8890214D00BB
Oct 16 09:33:02.210: Sending Complete
Oct 16 09:33:02.214: ISDN Se0:15: llc valid, speed 64, call type is V.110 speed:13 async:Y rate 0 nic(tx:N rx:N) fc(tx:N rx:N)
Oct 16 09:33:02.214: stop 1 data 3 parity 3
as-staff#
Oct 16 09:33:02.214: ISDN Se0:15: TX -> CALL_PROC pd = 8 callref = 0xD953
Oct 16 09:33:02.214: Channel ID i = 0xA98382
Oct 16 09:33:02.218: ISDN Se0:15: TX -> ALERTING pd = 8 callref = 0xD953
Oct 16 09:33:02.346: ISDN Se0:15: TX -> CONNECT pd = 8 callref = 0xD953
Oct 16 09:33:02.354: ISDN Se0:15: RX <- CONNECT_ACK pd = 8 callref = 0x5953
Oct 16 09:33:02.354: ISDN Se0:15: CALL_PROGRESS: CALL_CONNECTED call id 0x18E8, bchan 1, dsl 0
as-staff#
Oct 16 09:33:08.358: %ISDN-6-CONNECT: Interface Serial0:1 is now connected to 9280044
as-staff#
Oct 16 09:33:08.370: %LINK-3-UPDOWN: Interface Async19, changed state to up
as-staff#
Oct 16 09:33:10.786: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async28, changed state to down
Oct 16 09:33:10.862: ISDN Se0:15: RX <- DISCONNECT pd = 8 callref = 0x579E
Oct 16 09:33:10.862: Cause i = 0x008090 - Normal call clearing
Oct 16 09:33:10.862: %ISDN-6-DISCONNECT: Interface Serial0:24 disconnected from 9407992 , call lasted 1022 seconds
as-staff#
Oct 16 09:33:10.866: ISDN Se0:15: TX -> RELEASE pd = 8 callref = 0xD79E
Oct 16 09:33:10.874: ISDN Se0:15: RX <- RELEASE_COMP pd = 8 callref = 0x579E
as-staff#
Oct 16 09:33:11.178: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async19, changed state to up
as-staff#
Oct 16 09:33:12.894: %LINK-5-CHANGED: Interface Async28, changed state to reset
as-staff#
Oct 16 09:33:16.658: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async19, changed state to down
Oct 16 09:33:16.778: %ISDN-6-DISCONNECT: Interface Serial0:1 disconnected from 9280044 , call lasted 14 seconds
as-staff#
Oct 16 09:33:16.778: ISDN Se0:15: TX -> DISCONNECT pd = 8 callref = 0xD953
Oct 16 09:33:16.778: Cause i = 0x8090 - Normal call clearing
Oct 16 09:33:16.790: ISDN Se0:15: RX <- RELEASE pd = 8 callref = 0x5953
Oct 16 09:33:16.794: Cause i = 0x008090 - Normal call clearing
Oct 16 09:33:16.794: ISDN Se0:15: TX -> RELEASE_COMP pd = 8 callref = 0xD953
Oct 16 09:33:17.894: %LINK-3-UPDOWN: Interface Async28, changed state to down
as-staff#
Oct 16 09:33:18.662: %LINK-5-CHANGED: Interface Async19, changed state to reset
as-staff#
Oct 16 09:33:23.662: %LINK-3-UPDOWN: Interface Async19, changed state to down
as-staff#
Oct 16 09:33:25.902: ISDN Se1:15: TX -> SETUP pd = 8 callref = 0x060F
Oct 16 09:33:25.902: Bearer Capability i = 0x8890214D06BB
Oct 16 09:33:25.902: Channel ID i = 0xA9839F
Oct 16 09:33:25.902: Calling Party Number i = 0xA1, '7773264', Plan:ISDN, Type:National
Oct 16 09:33:25.902: Called Party Number i = 0xA1, '92800440', Plan:ISDN, Type:National
Oct 16 09:33:25.902: Low Layer Compat i = 0x8890214D06BB
Oct 16 09:33:25.922: ISDN Se1:15: RX <- SETUP_ACK pd = 8 callref = 0x860F
Oct 16 09:33:25.922: Channel ID i = 0xA9839F
Oct 16 09:33:25.946: ISDN Se1:15: RX <- DISCONNECT pd = 8 callref = 0x860F
Oct 16 09:33:25.946:
as-staff#Cause i = 0x028081 - Unallocated/unassigned number
Oct 16 09:33:25.950: ISDN Se1:15: TX -> RELEASE pd = 8 callref = 0x060F
Oct 16 09:33:25.958: ISDN Se1:15: RX <- RELEASE_COMP pd = 8 callref = 0x860F
***********************************************************
As You see, this time there is "0" at the end of the called number.
Also I tried to do "debug chat" - it tells dialing the right number, but the call does not come in :
as-staff#debug chat line tty 13
Chat scripts activity debugging is on for line number 13
as-staff#
Oct 16 09:46:32.295: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async13, changed state to down
as-staff#
Oct 16 09:46:32.419: %ISDN-6-DISCONNECT: Interface Serial0:14 disconnected from 9280044 , call lasted 25 seconds
as-staff#
Oct 16 09:46:34.295: %LINK-5-CHANGED: Interface Async13, changed state to reset
as-staff#
Oct 16 09:46:39.295: %LINK-3-UPDOWN: Interface Async13, changed state to down
as-staff#
Oct 16 09:46:41.296: CHAT13: Matched chat script offhook to string offhook
Oct 16 09:46:41.296: CHAT13: Asserting DTR
Oct 16 09:46:41.296: CHAT13: Chat script offhook started
Oct 16 09:46:41.296: CHAT13: Sending string: ATH1
Oct 16 09:46:41.296: CHAT13: Expecting string: OK
Oct 16 09:46:41.332: CHAT13: Input mismatch expecting: OK :: ATH1\015\015\012
Oct 16 09:46:41.332: CHAT13: Input match for: OK:: OK
Oct 16 09:46:41.332: CHAT13: Completed match for expect: OK
Oct 16 09:46:41.332: CHAT13: Sending string: \c
Oct 16 09:46:41.332: CHAT13: Chat script offhook finished, status = Success
Oct 16 09:46:41.332: CHAT13: Matched chat script mica-v110 to string mica-v110
Oct 16 09:46:41.332: CHAT13: Asserting DTR
Oct 16 09:46:41.332: CHAT13: Chat script mica-v110 started
Oct 16 09:46:41.332: CHAT13: Sending string: ATZ
Oct 16 09:46:41.332: CHAT13: Expecting string: OK
Oct 16 09:46:41.360: CHAT13: Input mismatch expecting: OK :: ATZ\015\015\012
Oct 16 09:46:41.376: CHAT13: Input match for: OK:: OK
Oct 16 09:46:41.376: CHAT13: Completed match for expect: OK
Oct 16 09:46:41.380: CHAT13: Sending string: ATS29=8S57=38400
Oct 16 09:46:41.380: CHAT13: Expecting string: OK
Oct 16 09:46:41.380: CHAT13: Input mismatch expecting: OK :: \015\012ATS29=8S57=38400\015\015\012
Oct 16 09:46:41.440: CHAT13: Input match for: OK:: OK
as-staff#
Oct 16 09:46:41.440: CHAT13: Completed match for expect: OK
Oct 16 09:46:41.444: CHAT13: Sending string: ATDI \T<9280044>
Oct 16 09:46:41.444: CHAT13: Expecting string: CONNECT
Oct 16 09:46:41.444: CHAT13: Input mismatch expecting: CONNECT :: \015\012ATDI 9280044\015\015\012NO ANSWER\015\012
as-staff#
***************************
debug chat script in analog callback mode when the call is recieved :
Oct 16 09:48:05.168: %ISDN-6-CONNECT: Interface Serial0:13 is now connected to 9280044
as-staff#
Oct 16 09:48:07.536: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async4, changed state to up
as-staff#debug chat line tty 4
Chat scripts activity debugging is on for line number 4
as-staff#
Oct 16 09:48:24.085: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async4, changed state to down
as-staff#
Oct 16 09:48:24.213: %ISDN-6-DISCONNECT: Interface Serial0:13 disconnected from 9280044 , call lasted 25 seconds
as-staff#
Oct 16 09:48:26.085: %LINK-5-CHANGED: Interface Async4, changed state to reset
as-staff#
Oct 16 09:48:31.085: %LINK-3-UPDOWN: Interface Async4, changed state to down
as-staff#
Oct 16 09:48:33.085: CHAT4: Matched chat script offhook to string offhook
Oct 16 09:48:33.085: CHAT4: Asserting DTR
Oct 16 09:48:33.085: CHAT4: Chat script offhook started
Oct 16 09:48:33.085: CHAT4: Sending string: ATH1
Oct 16 09:48:33.085: CHAT4: Expecting string: OK
Oct 16 09:48:33.101: CHAT4: Input mismatch expecting: OK :: ATH1\015\015\012
Oct 16 09:48:33.117: CHAT4: Input match for: OK:: OK
Oct 16 09:48:33.117: CHAT4: Completed match for expect: OK
Oct 16 09:48:33.117: CHAT4: Sending string: \c
Oct 16 09:48:33.117: CHAT4: Chat script offhook finished, status = Success
Oct 16 09:48:33.117: CHAT4: Matched chat script mica-callback to string mica-callback
as-staff#
Oct 16 09:48:33.117: CHAT4: Asserting DTR
Oct 16 09:48:33.121: CHAT4: Chat script mica-callback started
Oct 16 09:48:33.121: CHAT4: Sending string: ATZ
Oct 16 09:48:33.121: CHAT4: Expecting string: OK
Oct 16 09:48:33.149: CHAT4: Input mismatch expecting: OK :: ATZ\015\015\012
Oct 16 09:48:33.149: CHAT4: Input match for: OK:: OK
Oct 16 09:48:33.149: CHAT4: Completed match for expect: OK
Oct 16 09:48:33.149: CHAT4: Sending string: ATDT\T<9280044>
Oct 16 09:48:33.149: CHAT4: Expecting string: CONNECT
Oct 16 09:48:33.153: CHAT4: Input mismatch expecting: CONNECT :: \015\012ATDT9280044\015
as-staff#
Oct 16 09:48:34.005: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async26, changed state to up
Oct 16 09:48:47.601: %ISDN-6-CONNECT: Interface Serial1:30 is now connected to 9280044
*******************************
10-15-2002 09:26 AM
Not sure what version you are at, but you may want to make sure you have the following fixes:
12.1(9) or later - CSCds47835
12.2 or 12.2T latest due to CSCdu50702
11-08-2002 12:32 AM
Contacting Cisco TAC the problem seems to be found :
Bug ID: CSCdx88731
http://www.cisco.com/cgi-bin/Support/Bugtool/onebug.pl?bugid=CSCdx88731&Submit=Search
Yet have to be tried but the symptom looks exactly like explained in a bug :
************************
Release Notes
Symptoms: The dial string that is passed for a V.110 callback may become
corrupted, and dialout will stop working.
Conditions: This symptom is observed on a Cisco AS5300 universal access
server when the dial string is appended with two more digits. This symptom
affects only V.110 callbacks.
Workaround: There is no workaround.
************************
First Found-in Version 12.2(11.1)
First Fixed-in Version 12.2(11.8), 12.2(11.8)S, 12.2(11.8)T, 12.2(11.8)GLD, 12.2(11.08b)DA
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide