Mailing List Archive

modem not negotiating when receive ANI on ISDN/PRI
Cisco 5300

2 ISDN/PRI with ANI. When a call comes in with ANI blocked then
connection establishes without problem. If ANI is NOT blocked, the
modem will not initiate negotiation. Sometimes the modem will
immediately return to onhook state. Other times the modem will stay in
call setup for an indefinite period.

My thought is that this is related to modemcap but could find no
supporting documentation. Does anyone have a suggestion?

TIA
Re: modem not negotiating when receive ANI on ISDN/PRI [ In reply to ]
That's very odd. The router shouldn't care what the
ANI is.

I'd get:

debug isdn q931
debug csm modem
debug modem

conf term
service timestamp debug date msec
modem call-record terse

Let's see what a good and a bad call look like. Also
check "show run", "show ver", "show modem ver".

Cheers,

Aaron

---

>Cisco 5300
>
>2 ISDN/PRI with ANI. When a call comes in with ANI blocked then
>connection establishes without problem. If ANI is NOT blocked, the
>modem will not initiate negotiation. Sometimes the modem will
>immediately return to onhook state. Other times the modem will stay in
>call setup for an indefinite period.
>
>My thought is that this is related to modemcap but could find no
>supporting documentation. Does anyone have a suggestion?
>
>TIA
>
>
>_______________________________________________
>cisco-nas mailing list
>cisco-nas@puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nas
>
>
Re: modem not negotiating when receive ANI on ISDN/PRI [ In reply to ]
Aaron,

Thanks for the reply. I ran show run, show ver and show modem ver
first. Followed by debugging with a bad call then a good call.

c5300#show run
Building configuration...

Current configuration : 3079 bytes
!
version 12.2
no parser cache
no service single-slot-reload-enable
service timestamps debug datetime msec
service timestamps log uptime
no service password-encryption
!
hostname c5300
!
logging rate-limit console 10 except errors
aaa new-model
aaa session-mib disconnect
aaa authentication login default group radius local
aaa authentication login console none
aaa authentication ppp default group radius local
aaa authorization network default group radius local
aaa accounting exec default start-stop group radius
aaa accounting connection default start-stop group radius
aaa accounting system default start-stop group radius
enable secret 5 xxxxxxxxxxx
enable password xxxxxxxxxxx
!
spe 1/0 1/8
firmware location flash:mica-modem-pw.2.9.5.0.bin
spe 2/0 2/8
firmware location flash:mica-modem-pw.2.9.5.0.bin
!
!
resource-pool disable
!
modem call-record terse
modem startup-test
modem country mica usa
ip subnet-zero
ip domain-name xxxxx
ip name-server x.x.x.x
ip name-server x.x.x.x
!
no ip dhcp-client network-discovery
async-bootp dns-server x.x.x.x x.x.x.x
isdn switch-type primary-ni
!
!
controller T1 0
framing esf
clock source line primary
linecode b8zs
ds0-group 0 timeslots 1-24 type e&m-fgb dtmf dnis
!
controller T1 1
framing esf
clock source line secondary 1
linecode b8zs
ds0-group 0 timeslots 1-24 type e&m-fgb dtmf dnis
!
controller T1 2
framing esf
clock source line secondary 2
linecode b8zs
pri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 2
!
controller T1 3
framing esf
clock source line secondary 3
linecode b8zs
pri-group timeslots 1-24 nfas_d backup nfas_int 1 nfas_group 2
!
!
interface Ethernet0
ip address x.x.x.x x.x.x.x
!
interface Serial0
no ip address
shutdown
no fair-queue
clockrate 2015232
!
interface Serial1
no ip address
shutdown
no fair-queue
clockrate 2015232
!
interface Serial2
no ip address
shutdown
no fair-queue
clockrate 2015232
!
interface Serial3
no ip address
shutdown
no fair-queue
clockrate 2015232
!
interface Serial2:23
ip unnumbered Ethernet0
encapsulation ppp
ip tcp header-compression passive
dialer-group 1
isdn switch-type primary-ni
isdn incoming-voice modem
peer default ip address pool setup_pool
ppp authentication pap
!
interface FastEthernet0
no ip address
shutdown
duplex auto
speed auto
!
interface Group-Async1
ip unnumbered Ethernet0
encapsulation ppp
ip tcp header-compression passive
async mode interactive
peer default ip address pool setup_pool
ppp authentication pap
group-range 1 96
!
ip local pool setup_pool x.x.x.x x.x.x.x
ip classless
ip route 0.0.0.0 0.0.0.0 x.x.x.x
ip http server
!
dialer-list 1 protocol ip permit
dialer-list 1 protocol ipx permit
radius-server host x.x.x.x auth-port 1645 acct-port 1646
radius-server retransmit 3
radius-server directed-request
radius-server key xxxxxxxxxx
!
line con 0
logging synchronous
line 1 96
modem InOut
autoselect during-login
autoselect ppp
line aux 0
line vty 0 4
password xxxxxx
!
scheduler interval 1000
end



c5300#show ver
Cisco Internetwork Operating System Software
IOS (tm) 5300 Software (C5300-I-M), Version 12.2(2)XA, EARLY DEPLOYMENT
RELEASE SOFTWARE (fc1)
TAC:Home:SW:IOS:Specials for info
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Wed 27-Jun-01 00:12 by hwcheng
Image text-base: 0x600089B0, data-base: 0x60996000

ROM: System Bootstrap, Version 12.0(2)XD1, EARLY DEPLOYMENT RELEASE
SOFTWARE (fc1)
BOOTFLASH: 5300 Software (C5300-I-M), Version 12.2(2)XA, EARLY
DEPLOYMENT RELEASE SOFTWARE (fc1)

c5300 uptime is 4 days, 3 hours, 14 minutes
System returned to ROM by reload at 11:33:44 UTC Fri Jun 10 2005
System image file is "flash:c5300-i-mz.122-2.XA.bin"

cisco AS5300 (R4K) processor (revision A.32) with 32768K/16384K bytes of
memory.
Processor board ID 11689597
R4700 CPU at 150Mhz, Implementation 33, Rev 1.0, 512KB L2 Cache
Bridging software.
X.25 software, Version 3.0.0.
Primary Rate ISDN software, Version 1.1.
Backplane revision 2
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x30,
Board Hardware Version 1.80, Item Number 800-2544-03,
Board Revision A0, Serial Number 11689597,
PLD/ISP Version 0.0, Manufacture Date 7-May-1999.
1 Ethernet/IEEE 802.3 interface(s)
1 FastEthernet/IEEE 802.3 interface(s)
100 Serial network interface(s)
96 terminal line(s)
4 Channelized T1/PRI port(s)
128K bytes of non-volatile configuration memory.
8192K bytes of processor board System flash (Read/Write)
8192K bytes of processor board Boot flash (Read/Write)

Configuration register is 0x2102



c5300#show modem ver

Codes:
d - DSP software download is required for achieving K56flex connections

Modem module Firmware Boot DSP
Mdm Number Rev Rev Rev
1/0 0 2.9.5.0
1/1 0 2.9.5.0
1/2 0 2.9.5.0
1/3 0 2.9.5.0
1/4 0 2.9.5.0
1/5 0 2.9.5.0
1/6 1 2.9.5.0
1/7 1 2.9.5.0
1/8 1 2.9.5.0
1/9 1 2.9.5.0
1/10 1 2.9.5.0
1/11 1 2.9.5.0
1/12 2 2.9.5.0
1/13 2 2.9.5.0
1/14 2 2.9.5.0
1/15 2 2.9.5.0
1/16 2 2.9.5.0
1/17 2 2.9.5.0
1/18 3 2.9.5.0

Modem module Firmware Boot DSP
Mdm Number Rev Rev Rev
1/19 3 2.9.5.0
1/20 3 2.9.5.0
1/21 3 2.9.5.0
1/22 3 2.9.5.0
1/23 3 2.9.5.0
1/24 4 2.9.5.0
1/25 4 2.9.5.0
1/26 4 2.9.5.0
1/27 4 2.9.5.0
1/28 4 2.9.5.0
1/29 4 2.9.5.0
1/30 5 2.9.5.0
1/31 5 2.9.5.0
1/32 5 2.9.5.0
1/33 5 2.9.5.0
1/34 5 2.9.5.0
1/35 5 2.9.5.0
1/36 6 2.9.5.0
1/37 6 2.9.5.0
1/38 6 2.9.5.0
1/39 6 2.9.5.0
1/40 6 2.9.5.0
1/41 6 2.9.5.0

Modem module Firmware Boot DSP
Mdm Number Rev Rev Rev
1/42 7 2.9.5.0
1/43 7 2.9.5.0
1/44 7 2.9.5.0
1/45 7 2.9.5.0
1/46 7 2.9.5.0
1/47 7 2.9.5.0
2/0 0 2.9.5.0
2/1 0 2.9.5.0
2/2 0 2.9.5.0
2/3 0 2.9.5.0
2/4 0 2.9.5.0
2/5 0 2.9.5.0
2/6 1 2.9.5.0
2/7 1 2.9.5.0
2/8 1 2.9.5.0
2/9 1 2.9.5.0
2/10 1 2.9.5.0
2/11 1 2.9.5.0
2/12 2 2.9.5.0
2/13 2 2.9.5.0
2/14 2 2.9.5.0
2/15 2 2.9.5.0
2/16 2 2.9.5.0

Modem module Firmware Boot DSP
Mdm Number Rev Rev Rev
2/17 2 2.9.5.0
2/18 3 2.9.5.0
2/19 3 2.9.5.0
2/20 3 2.9.5.0
2/21 3 2.9.5.0
2/22 3 2.9.5.0
2/23 3 2.9.5.0
2/24 4 2.9.5.0
2/25 4 2.9.5.0
2/26 4 2.9.5.0
2/27 4 2.9.5.0
2/28 4 2.9.5.0
2/29 4 2.9.5.0
2/30 5 2.9.5.0
2/31 5 2.9.5.0
2/32 5 2.9.5.0
2/33 5 2.9.5.0
2/34 5 2.9.5.0
2/35 5 2.9.5.0
2/36 6 2.9.5.0
2/37 6 2.9.5.0
2/38 6 2.9.5.0
2/39 6 2.9.5.0
Modem module Firmware Boot DSP
Mdm Number Rev Rev Rev
2/40 6 2.9.5.0
2/41 6 2.9.5.0
2/42 7 2.9.5.0
2/43 7 2.9.5.0
2/44 7 2.9.5.0
2/45 7 2.9.5.0
2/46 7 2.9.5.0
2/47 7 2.9.5.0

Modem board HW version info:

Slot 1:
Carrier card:
number_of_ports= 48, max_modules= 10
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x4C,
Board Hardware Version 1.0, Item Number 800-3680-01,
Board Revision A0, Serial Number 11690648,
PLD/ISP Version 2.2, Manufacture Date 3-May-1999.

Modem Module 0
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 13994666,
PLD/ISP Version <unset>, Manufacture Date 12-May-1999.

Modem Module 1
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14004950,
PLD/ISP Version <unset>, Manufacture Date 12-May-1999.

Modem Module 2
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14004939,
PLD/ISP Version <unset>, Manufacture Date 12-May-1999.

Modem Module 3
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14004942,
PLD/ISP Version <unset>, Manufacture Date 12-May-1999.

Modem Module 4
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14004943,
PLD/ISP Version <unset>, Manufacture Date 12-May-1999.

Modem Module 5
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14004949,
PLD/ISP Version <unset>, Manufacture Date 12-May-1999.

Modem Module 6
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14004936,
PLD/ISP Version <unset>, Manufacture Date 12-May-1999.

Modem Module 7
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14004371,
PLD/ISP Version <unset>, Manufacture Date 12-May-1999.

Modem Module 8

Modem Module 9


Slot 2:
Carrier card:
number_of_ports= 48, max_modules= 10
Manufacture Cookie Info:
EEPROM Type 0x0001, EEPROM Version 0x01, Board ID 0x4C,
Board Hardware Version 1.0, Item Number 800-3680-01,
Board Revision A0, Serial Number 11690743,
PLD/ISP Version 2.2, Manufacture Date 3-May-1999.

Modem Module 0
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14003892,
PLD/ISP Version <unset>, Manufacture Date 11-May-1999.

Modem Module 1
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14004189,
PLD/ISP Version <unset>, Manufacture Date 11-May-1999.

Modem Module 2
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14004192,
PLD/ISP Version <unset>, Manufacture Date 11-May-1999.

Modem Module 3
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14004180,
PLD/ISP Version <unset>, Manufacture Date 11-May-1999.

Modem Module 4
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14003899,
PLD/ISP Version <unset>, Manufacture Date 11-May-1999.

Modem Module 5
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14003887,
PLD/ISP Version <unset>, Manufacture Date 11-May-1999.

Modem Module 6
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14003886,
PLD/ISP Version <unset>, Manufacture Date 11-May-1999.

Modem Module 7
Manufacture Cookie Info:
EEPROM Type 0x0101, EEPROM Version 0x01, Board ID 0x06,
Board Hardware Version 1.0, Item Number 73-2522-02,
Board Revision C48, Serial Number 14003883,
PLD/ISP Version <unset>, Manufacture Date 11-May-1999.

Modem Module 8

Modem Module 9

c5300#debug isdn q931
ISDN Q931 packets debugging is on
c5300#debug csm modem
Modem Management Call Switching Module debugging is on
c5300#debug modem
Modem control/process activation debugging is on
c5300#


###### BEGIN BAD CALL ##################

*Jun 14 15:00:00.711: ISDN Se2:23: RX <- SETUP pd = 8 callref = 0x0242
*Jun 14 15:00:00.711: Bearer Capability i = 0x8090A2
*Jun 14 15:00:00.711: Channel ID i = 0xA98381
*Jun 14 15:00:00.711: Progress Ind i = 0x8283 - Origination
address is non-ISDN
*Jun 14 15:00:00.715: Calling Party Number i = 0x2180,
'7162842717', Plan:ISDN, Type:National
*Jun 14 15:00:00.715: Called Party Number i = 0x80, '0569',
Plan:Unknown, Type:Unknown
*Jun 14 15:00:00.719: VDEV_ALLOCATE: 2/1 is allocated
*Jun 14 15:00:00.719: EVENT_FROM_ISDN::dchan_idb=0x61E2F720,
call_id=0x6A, ces=0x1
bchan=0x0, event=0x1, cause=0x0

*Jun 14 15:00:00.719: dev in call to isdn : set dnis_collected & fap_notify

*Jun 14 15:00:00.719: EVENT_FROM_ISDN:(006A): DEV_INCALL at slot 2 and
port 1

*Jun 14 15:00:00.719: EVENT_FROM_ISDN: decode:calling 0ct3 0x21, called
oct3 0x80, oct3a 0x80,mask 0x3F
called oct3 0x80, oct3a 0x80,mask 0x3F: csm_call_info:calling 0ct3 0x21,
*Jun 14 15:00:00.719: CSM_PROC_IDLE: CSM_EVENT_ISDN_CALL at slot 2, port 1
*Jun 14 15:00:00.719: Mica Modem(2/1): Configure(0x1 = 0x0)
*Jun 14 15:00:00.719: Mica Modem(2/1): Configure(0x23 = 0x0)
*Jun 14 15:00:00.719: Mica Modem(2/1): Call Setup
*Jun 14 15:00:00.719: csm_connect_pri_vdev: TS allocated at bp_stream 1,
bp_Ch 0,vdev_common 0x613A9618
*Jun 14 15:00:00.723: ISDN Se2:23: TX -> CALL_PROC pd = 8 callref = 0x8242
*Jun 14 15:00:00.723: Channel ID i = 0xA98381
*Jun 14 15:00:00.723: ISDN Se2:23: TX -> ALERTING pd = 8 callref = 0x8242
*Jun 14 15:00:00.771: Mica Modem(2/1): State Transition to Call Setup
*Jun 14 15:00:00.771: Mica Modem(2/1): Went offhook
*Jun 14 15:00:00.771: CSM_PROC_IC2_RING: CSM_EVENT_MODEM_OFFHOOK at slot
2, port 1
*Jun 14 15:00:00.771: CSM_RX_CAS_EVENT_FROM_NEAT:(006A):
EVENT_CALL_IDLE at slot 2 port 1 cause 201
*Jun 14 15:00:00.771: CSM_PROC_IC3_WAIT_FOR_RES_RESP:
CSM_EVENT_DSX0_DISCONNECTED at slot 2, port 1
*Jun 14 15:00:00.771: Mica Modem(2/1): Soft Reset
*Jun 14 15:00:00.775: CSM(2/1): Enter csm_enter_disconnecting_state
*Jun 14 15:00:00.775: VDEV_DEALLOCATE: slot 2 and port 1 is deallocated

*Jun 14 15:00:00.787: Mica Modem(2/1): State Transition to Terminating
*Jun 14 15:00:00.803: Mica Modem(2/1): State Transition to Idle
*Jun 14 15:00:00.803: Mica Modem(2/1): Went onhook
*Jun 14 15:00:00.803: CSM_PROC_IC8_OC8_DISCONNECTING:
CSM_EVENT_MODEM_ONHOOK at slot 2, port 1
*Jun 14 15:00:00.803: CSM(2/1): Enter csm_enter_idle_state
*Jun 14 15:00:52.403: TTY0: timer type 1 expired
*Jun 14 15:00:52.403: TTY0: Exec timer (continued)
c5300#
*Jun 14 15:01:23.095: ISDN Se2:23: RX <- DISCONNECT pd = 8 callref =
0x0242
*Jun 14 15:01:23.095: Cause i = 0x8490 - Normal call clearing
*Jun 14 15:01:23.099: EVENT_FROM_ISDN::dchan_idb=0x61E2F720,
call_id=0x6A, ces=0x1
bchan=0x0, event=0x0, cause=0x10

*Jun 14 15:01:23.099: ISDN Se2:23: TX -> RELEASE pd = 8 callref = 0x8242
*Jun 14 15:01:23.115: ISDN Se2:23: RX <- RELEASE_COMP pd = 8 callref =
0x0242
*Jun 14 15:01:23.115: EVENT_FROM_ISDN::dchan_idb=0x61E2F720,
call_id=0x6A, ces=0x1
bchan=0x0, event=0x0, cause=0x0





##### BEGIN GOOD CALL ###############################


c5300#
*Jun 14 15:02:29.963: VDEV_ALLOCATE: 2/25 is allocated
*Jun 14 15:02:29.963: 1.starting digit collect: reset dnis_collected &
fap_notify

*Jun 14 15:02:29.963: CSM_RX_CAS_EVENT_FROM_NEAT:(cid0A70):
EVENT_CALL_DIAL_IN at slot 2 and port 25
*Jun 14 15:02:29.963: CSM_PROC_IDLE: CSM_EVENT_START_DIGIT_COLLECT at
slot 2, port 25
*Jun 14 15:02:29.967: Mica Modem(2/25): Configure(0x1 = 0x0)
*Jun 14 15:02:29.967: Mica Modem(2/25): Configure(0x23 = 0x2)
*Jun 14 15:02:29.967: Mica Modem(2/25): Call Setup
*Jun 14 15:02:29.967: csm_connect_pri_vdev: TS allocated at bp_stream 1,
bp_Ch 2,vdev_common 0x613D3CD8
c5300#
*Jun 14 15:02:29.967: to NEAT:(cid0A70) EVENT_CHANNEL_LOCK for slot0
ctlr0 chan21
*Jun 14 15:02:30.023: Mica Modem(2/25): State Transition to Call Setup
*Jun 14 15:02:30.023: Mica Modem(2/25): Went offhook
*Jun 14 15:02:30.023: CSM_PROC_IC1_COLLECT_ADDR_INFO:
CSM_EVENT_MODEM_OFFHOOK (DNIS=, ANI=) at slot 2, port 25

*Jun 14 15:02:30.339: CSM_RX_CAS_EVENT_FROM_NEAT:(0A70):
EVENT_START_RX_TONE at slot 2 and port 25
*Jun 14 15:02:30.535: Mica Modem(2/25): Rcvd Digit detected(0)
*Jun 14 15:02:30.535: CSM_PROC_IC1_COLLECT_ADDR_INFO:
CSM_EVENT_DIGIT_COLLECTED (DNIS=, ANI=) at slot 2, port 25

*Jun 14 15:02:30.535: Device(2/25): Rcvd Digit detected(0)
*Jun 14 15:02:30.667: Mica Modem(2/25): Rcvd Digit detected(1)
*Jun 14 15:02:30.667: CSM_PROC_IC1_COLLECT_ADDR_INFO:
CSM_EVENT_DIGIT_COLLECTED (DNIS=0280, ANI=) at slot 2, port 25

*Jun 14 15:02:30.667: Device(2/25): Rcvd Digit detected(1)
*Jun 14 15:02:30.803: Mica Modem(2/25): Rcvd Digit detected(7)
*Jun 14 15:02:30.803: CSM_PROC_IC1_COLLECT_ADDR_INFO:
CSM_EVENT_DIGIT_COLLECTED (DNIS=0180, ANI=) at slot 2, port 25

*Jun 14 15:02:30.803: Device(2/25): Rcvd Digit detected(7)
*Jun 14 15:02:30.939: Mica Modem(2/25): Rcvd Digit detected(6)
*Jun 14 15:02:30.939: CSM_PROC_IC1_COLLECT_ADDR_INFO:
CSM_EVENT_DIGIT_COLLECTED (DNIS=0170, ANI=) at slot 2, port 25

*Jun 14 15:02:30.939: Device(2/25): Rcvd Digit detected(6)
*Jun 14 15:02:31.735: ISDN Se2:23: RX <- SETUP pd = 8 callref = 0x0243
*Jun 14 15:02:31.735: Bearer Capability i = 0x8090A2
*Jun 14 15:02:31.735: Channel ID i = 0xA98381
*Jun 14 15:02:31.735: Progress Ind i = 0x8283 - Origination
address is non-ISDN
*Jun 14 15:02:31.735: Calling Party Number i = 0x21A0,
Plan:ISDN, Type:National
*Jun 14 15:02:31.735: Called Party Number i = 0x80, '0569',
Plan:Unknown, Type:Unknown
*Jun 14 15:02:31.739: VDEV_ALLOCATE: 1/32 is allocated
*Jun 14 15:02:31.743: EVENT_FROM_ISDN::dchan_idb=0x61E2F720,
call_id=0x6B, ces=0x1
bchan=0x0, event=0x1, cause=0x0

*Jun 14 15:02:31.743: dev in call to isdn : set dnis_collected & fap_notify

*Jun 14 15:02:31.743: EVENT_FROM_ISDN:(006B): DEV_INCALL at slot 1 and
port 32

*Jun 14 15:02:31.743: EVENT_FROM_ISDN: decode:calling 0ct3 0x21, called
oct3 0x80, oct3a 0xA0,mask 0x3F
*Jun 14 15:02:31.743: EVENT_FROM_ISDN: csm_call_info:calling 0ct3 0x21,
called oct3 0x80, oct3a 0xA0,mask 0x3F
*Jun 14 15:02:31.743: CSM_PROC_IDLE: CSM_EVENT_ISDN_CALL at slot 1, port 32
*Jun 14 15:02:31.743: Mica Modem(1/32): Configure(0x1 = 0x0)
*Jun 14 15:02:31.743: Mica Modem(1/32): Configure(0x23 = 0x0)
*Jun 14 15:02:31.743: Mica Modem(1/32): Call Setup
*Jun 14 15:02:31.743: csm_connect_pri_vdev: TS allocated at bp_stream 2,
bp_Ch 8,vdev_common 0x612C2C2C
*Jun 14 15:02:31.743: ISDN Se2:23: TX -> CALL_PROC pd = 8 callref = 0x8243
*Jun 14 15:02:31.743: Channel ID i = 0xA98381
*Jun 14 15:02:31.743: ISDN Se2:23: TX -> ALERTING pd = 8 callref = 0x8243
*Jun 14 15:02:31.823: Mica Modem(1/32): State Transition to Call Setup
*Jun 14 15:02:31.823: Mica Modem(1/32): Went offhook
*Jun 14 15:02:31.823: CSM_PROC_IC2_RING: CSM_EVENT_MODEM_OFFHOOK at slot
1, port 32
*Jun 14 15:02:31.827: ISDN Se2:23: TX -> CONNECT pd = 8 callref = 0x8243
*Jun 14 15:02:31.843: ISDN Se2:23: RX <- CONNECT_ACK pd = 8 callref =
0x0243
*Jun 14 15:02:31.847: ISDN Se2:23: CALL_PROGRESS: CALL_CONNECTED call id
0x6B, bchan 0, dsl 0
*Jun 14 15:02:31.847: EVENT_FROM_ISDN::dchan_idb=0x61E2F720,
call_id=0x6B, ces=0x1
bchan=0x0, event=0x4, cause=0x0

*Jun 14 15:02:31.847: EVENT_FROM_ISDN:(006B): DEV_CONNECTED at slot 1
and port 32

*Jun 14 15:02:31.847: CSM_PROC_IC6_WAIT_FOR_CONNECT:
CSM_EVENT_ISDN_CONNECTED at slot 1, port 32
*Jun 14 15:02:31.847: Mica Modem(1/32): Link Initiate
4d03h: %ISDN-6-CONNECT: Interface Serial2:0 is now connected to N/A N/A
*Jun 14 15:02:31.939: CSM_PROC_IC1_COLLECT_ADDR_INFO:
CSM_EVENT_ADDR_INFO_COLLECTED (DNIS=0176, ANI=) at slot 2, port 25

*Jun 14 15:02:31.939: csm_call_info->dnis_collected is 1

*Jun 14 15:02:31.939: cas_group=0, service=2
*Jun 14 15:02:31.939: csm_res_response: service_type =0, fax_call=0,
fap_notify=0

*Jun 14 15:02:31.939: CSM_PROC_IC3_WAIT_FOR_RES_RESP:
CSM_EVENT_RESOURCE_OK at slot 2, port 25
*Jun 14 15:02:31.939: CSM_SEND_NEAT_CAS_EVENT(2/25): EVENT_END_RX_TONE
*Jun 14 15:02:32.915: Mica Modem(1/32): State Transition to Connect
*Jun 14 15:02:33.043: CSM_RX_CAS_EVENT_FROM_NEAT:(0A70):
EVENT_CHANNEL_CONNECTED at slot 2 and port 25
*Jun 14 15:02:33.043: CSM_PROC_IC6_WAIT_FOR_CONNECT:
CSM_EVENT_DSX0_CONNECTED at slot 2, port 25
*Jun 14 15:02:33.047: Mica Modem(2/25): Link Initiate
*Jun 14 15:02:34.119: Mica Modem(2/25): State Transition to Connect
c5300#
c5300#
*Jun 14 15:02:38.067: Mica Modem(1/32): State Transition to Link
c5300#
*Jun 14 15:02:39.315: Mica Modem(2/25): State Transition to Link
c5300#
*Jun 14 15:02:48.323: Mica Modem(2/25): State Transition to Trainup
c5300#
*Jun 14 15:02:49.763: Mica Modem(2/25): State Transition to EC Negotiating
*Jun 14 15:02:50.483: Mica Modem(2/25): State Transition to Steady State
c5300#
*Jun 14 15:02:51.479: TTY74: DSR came up
*Jun 14 15:02:51.479: tty74: Modem: IDLE->(unknown)
*Jun 14 15:02:51.479: TTY74: EXEC creation
*Jun 14 15:02:51.479: TTY74: set timer type 10, 30 seconds
c5300#
*Jun 14 15:02:52.755: TTY74: Autoselect(2) sample 7E
*Jun 14 15:02:52.755: TTY74: Autoselect(2) sample 7EFF
*Jun 14 15:02:52.755: TTY74: Autoselect(2) sample 7EFF7D
*Jun 14 15:02:52.759: TTY74: Autoselect(2) sample 7EFF7D23
*Jun 14 15:02:52.759: TTY74 Autoselect cmd: ppp negotiate
*Jun 14 15:02:52.759: TTY74: EXEC creation
*Jun 14 15:02:52.759: TTY74: create timer type 1, 600 seconds
*Jun 14 15:02:52.891: TTY74: destroy timer type 1
*Jun 14 15:02:52.891: TTY74: no timer type 0 to destroy
c5300#
4d03h: %LINK-3-UPDOWN: Interface Async74, changed state to up
c5300#
*Jun 14 15:02:55.767: Unthrottle 74
c5300#
4d03h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async74, changed
state to up


Aaron Leonard wrote:

> That's very odd. The router shouldn't care what the
> ANI is.
>
> I'd get:
>
> debug isdn q931
> debug csm modem
> debug modem
>
> conf term
> service timestamp debug date msec
> modem call-record terse
>
> Let's see what a good and a bad call look like. Also
> check "show run", "show ver", "show modem ver".
>
> Cheers,
>
> Aaron
>
> ---
>
>> Cisco 5300
>>
>> 2 ISDN/PRI with ANI. When a call comes in with ANI blocked then
>> connection establishes without problem. If ANI is NOT blocked, the
>> modem will not initiate negotiation. Sometimes the modem will
>> immediately return to onhook state. Other times the modem will stay
>> in call setup for an indefinite period.
>>
>> My thought is that this is related to modemcap but could find no
>> supporting documentation. Does anyone have a suggestion?
>>
>> TIA
>>
>>
>> _______________________________________________
>> cisco-nas mailing list
>> cisco-nas@puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nas
>>
>>
>
Re: modem not negotiating when receive ANI on ISDN/PRI [ In reply to ]
Hi Rodney,

Well, your debugs are bizarre. Here's the crux of the failing call:

> *Jun 14 15:00:00.719: Mica Modem(2/1): Call Setup
> *Jun 14 15:00:00.719: csm_connect_pri_vdev: TS allocated at bp_stream 1,
> bp_Ch 0,vdev_common 0x613A9618
> *Jun 14 15:00:00.723: ISDN Se2:23: TX -> CALL_PROC pd = 8 callref =
> 0x8242
> *Jun 14 15:00:00.723: Channel ID i = 0xA98381
> *Jun 14 15:00:00.723: ISDN Se2:23: TX -> ALERTING pd = 8 callref =
> 0x8242
> *Jun 14 15:00:00.771: Mica Modem(2/1): State Transition to Call Setup
> *Jun 14 15:00:00.771: Mica Modem(2/1): Went offhook
> *Jun 14 15:00:00.771: CSM_PROC_IC2_RING: CSM_EVENT_MODEM_OFFHOOK at slot
> 2, port 1
> **Jun 14 15:00:00.771: CSM_RX_CAS_EVENT_FROM_NEAT:(006A):
> EVENT_CALL_IDLE at slot 2 port 1 cause 201*
> *Jun 14 15:00:00.771: CSM_PROC_IC3_WAIT_FOR_RES_RESP:
> CSM_EVENT_DSX0_DISCONNECTED at slot 2, port 1
> *Jun 14 15:00:00.771: Mica Modem(2/1): Soft Reset
> *Jun 14 15:00:00.775: CSM(2/1): Enter csm_enter_disconnecting_state


The highlighted debug is the problem ... we are in the middle of
setting up a call using ISDN, but suddenly NEAT (which is the
framer code for the CT1) has told CSM (Call Switching Module, the
IOS code responsible for modem call handling) that *CAS* (i.e. RBS)
signaling has told it to hang up the call. If ISDN signaling is
being used on a span, then NEAT should never be looking for
CAS A/B bit signal transitions - something has clearly gone awry.

I do see that you have some spans configured for winkstart CAS
(e&m-fgb) and others for PRI, so perhaps NEAT has gotten confused.

One thought: have you reconfigured one of your T1s without rebooting?
You shouldn't HAVE to reboot after a reconfiguration, but maybe
the NEAT logic wasn't reset after a reconfiguration? (Just a stab
in the dark.)

I was not able to find a known bug matching this syndrome.

I do see that you are running 12.2(2)XA, which is somewhat iffy code.
(It was the first 12.2 code with support for the AS5400 and for
V.92/V.44.) If the reboot idea doesn't help any, I would upgrade
IOS ... I'd probably go to a 12.3 mainline image such as 12.3(5e)
or 12.3(15).

Cheers,

Aaron
Re: modem not negotiating when receive ANI on ISDN/PRI [ In reply to ]
Aaron,

Thanks for you assistance.

I attempted a reboot but something happened to our flash and the
12.2(2)XA image was gone. Because of my flash size limitation I am
unable to upgrade to 12.3 at this time. I did find an image for
12.2(2)XB3 that installed.

At any rate, everything is working as expected now.

Thanks again.

Rod

Aaron Leonard wrote:

> Hi Rodney,
>
> Well, your debugs are bizarre. Here's the crux of the failing call:
>
>> *Jun 14 15:00:00.719: Mica Modem(2/1): Call Setup
>> *Jun 14 15:00:00.719: csm_connect_pri_vdev: TS allocated at bp_stream 1,
>> bp_Ch 0,vdev_common 0x613A9618
>> *Jun 14 15:00:00.723: ISDN Se2:23: TX -> CALL_PROC pd = 8 callref =
>> 0x8242
>> *Jun 14 15:00:00.723: Channel ID i = 0xA98381
>> *Jun 14 15:00:00.723: ISDN Se2:23: TX -> ALERTING pd = 8 callref =
>> 0x8242
>> *Jun 14 15:00:00.771: Mica Modem(2/1): State Transition to Call Setup
>> *Jun 14 15:00:00.771: Mica Modem(2/1): Went offhook
>> *Jun 14 15:00:00.771: CSM_PROC_IC2_RING: CSM_EVENT_MODEM_OFFHOOK at slot
>> 2, port 1
>> **Jun 14 15:00:00.771: CSM_RX_CAS_EVENT_FROM_NEAT:(006A):
>> EVENT_CALL_IDLE at slot 2 port 1 cause 201*
>> *Jun 14 15:00:00.771: CSM_PROC_IC3_WAIT_FOR_RES_RESP:
>> CSM_EVENT_DSX0_DISCONNECTED at slot 2, port 1
>> *Jun 14 15:00:00.771: Mica Modem(2/1): Soft Reset
>> *Jun 14 15:00:00.775: CSM(2/1): Enter csm_enter_disconnecting_state
>
>
>
> The highlighted debug is the problem ... we are in the middle of
> setting up a call using ISDN, but suddenly NEAT (which is the
> framer code for the CT1) has told CSM (Call Switching Module, the
> IOS code responsible for modem call handling) that *CAS* (i.e. RBS)
> signaling has told it to hang up the call. If ISDN signaling is
> being used on a span, then NEAT should never be looking for
> CAS A/B bit signal transitions - something has clearly gone awry.
>
> I do see that you have some spans configured for winkstart CAS
> (e&m-fgb) and others for PRI, so perhaps NEAT has gotten confused.
>
> One thought: have you reconfigured one of your T1s without rebooting?
> You shouldn't HAVE to reboot after a reconfiguration, but maybe
> the NEAT logic wasn't reset after a reconfiguration? (Just a stab
> in the dark.)
>
> I was not able to find a known bug matching this syndrome.
>
> I do see that you are running 12.2(2)XA, which is somewhat iffy code.
> (It was the first 12.2 code with support for the AS5400 and for
> V.92/V.44.) If the reboot idea doesn't help any, I would upgrade
> IOS ... I'd probably go to a 12.3 mainline image such as 12.3(5e)
> or 12.3(15).
>
> Cheers,
>
> Aaron
>
>
Re: modem not negotiating when receive ANI on ISDN/PRI [ In reply to ]
Hi Rod,

Sorry to hear about the difficulty during the upgrade, but I'm
glad to hear that things are working for you right now.

I do have to say that 12.2(2)XB3 wasn't real solid code ... the
12.2XB train didn't really stabilize till around XB6. If you want to
run 12.2XB, I'd recommend that you run more recent XB (the
latest for the 5300 is 12.2(2)XB16) - EXCEPT that we are not
permitted to post 12.2XB code right now due to the
"Cisco IOS Software Center Update"
http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/prod_bulletin0900aecd80281c0e.html
...

Anyhoo ... you DO have quite a simple configuration, so hopefully
12.2XB3 will continue work well for you ...

Cheers,

Aaron

---

>
>
> Thanks for you assistance.
>
> I attempted a reboot but something happened to our flash and the
> 12.2(2)XA image was gone. Because of my flash size limitation I am
> unable to upgrade to 12.3 at this time. I did find an image for
> 12.2(2)XB3 that installed.
>
> At any rate, everything is working as expected now.
>
> Thanks again.
>
> Rod
>
> Aaron Leonard wrote:
>
>> Hi Rodney,
>>
>> Well, your debugs are bizarre. Here's the crux of the failing call:
>>
>>> *Jun 14 15:00:00.719: Mica Modem(2/1): Call Setup
>>> *Jun 14 15:00:00.719: csm_connect_pri_vdev: TS allocated at
>>> bp_stream 1,
>>> bp_Ch 0,vdev_common 0x613A9618
>>> *Jun 14 15:00:00.723: ISDN Se2:23: TX -> CALL_PROC pd = 8 callref
>>> = 0x8242
>>> *Jun 14 15:00:00.723: Channel ID i = 0xA98381
>>> *Jun 14 15:00:00.723: ISDN Se2:23: TX -> ALERTING pd = 8 callref =
>>> 0x8242
>>> *Jun 14 15:00:00.771: Mica Modem(2/1): State Transition to Call Setup
>>> *Jun 14 15:00:00.771: Mica Modem(2/1): Went offhook
>>> *Jun 14 15:00:00.771: CSM_PROC_IC2_RING: CSM_EVENT_MODEM_OFFHOOK at
>>> slot
>>> 2, port 1
>>> **Jun 14 15:00:00.771: CSM_RX_CAS_EVENT_FROM_NEAT:(006A):
>>> EVENT_CALL_IDLE at slot 2 port 1 cause 201*
>>> *Jun 14 15:00:00.771: CSM_PROC_IC3_WAIT_FOR_RES_RESP:
>>> CSM_EVENT_DSX0_DISCONNECTED at slot 2, port 1
>>> *Jun 14 15:00:00.771: Mica Modem(2/1): Soft Reset
>>> *Jun 14 15:00:00.775: CSM(2/1): Enter csm_enter_disconnecting_state
>>
>>
>>
>>
>> The highlighted debug is the problem ... we are in the middle of
>> setting up a call using ISDN, but suddenly NEAT (which is the
>> framer code for the CT1) has told CSM (Call Switching Module, the
>> IOS code responsible for modem call handling) that *CAS* (i.e. RBS)
>> signaling has told it to hang up the call. If ISDN signaling is
>> being used on a span, then NEAT should never be looking for
>> CAS A/B bit signal transitions - something has clearly gone awry.
>>
>> I do see that you have some spans configured for winkstart CAS
>> (e&m-fgb) and others for PRI, so perhaps NEAT has gotten confused.
>>
>> One thought: have you reconfigured one of your T1s without rebooting?
>> You shouldn't HAVE to reboot after a reconfiguration, but maybe
>> the NEAT logic wasn't reset after a reconfiguration? (Just a stab
>> in the dark.)
>>
>> I was not able to find a known bug matching this syndrome.
>>
>> I do see that you are running 12.2(2)XA, which is somewhat iffy code.
>> (It was the first 12.2 code with support for the AS5400 and for
>> V.92/V.44.) If the reboot idea doesn't help any, I would upgrade
>> IOS ... I'd probably go to a 12.3 mainline image such as 12.3(5e)
>> or 12.3(15).
>>
>> Cheers,
>>
>> Aaron
>>
>>
Re: modem not negotiating when receive ANI on ISDN/PRI [ In reply to ]
Aaron,

Funny you should say this now. Things ran fine for about 3 hours. Now
I'm getting "%% Unable to create EXEC - no memory or too many processes"
when trying to log into the console. It's showing a bunch of
"%SYS-2-MALLOCFAIL: Memory allocation of 32768 bytes failed from
0x603AD5AC, pool Processor, alignment 0 -Process= "MM/CSM Event Bkgnd",
ipl= 0, pid= 72 -Traceback= 603B0D88 603B3440 603AD5B4 603ADDC0 6017E01C
603A71E4 603A71D0" type errors as well.

I'm having a tough time finding out what IOS version I should be or am
able to run given this box.

Thanks

Rod

Aaron Leonard wrote:

> Hi Rod,
>
> Sorry to hear about the difficulty during the upgrade, but I'm
> glad to hear that things are working for you right now.
>
> I do have to say that 12.2(2)XB3 wasn't real solid code ... the
> 12.2XB train didn't really stabilize till around XB6. If you want to
> run 12.2XB, I'd recommend that you run more recent XB (the
> latest for the 5300 is 12.2(2)XB16) - EXCEPT that we are not
> permitted to post 12.2XB code right now due to the
> "Cisco IOS Software Center Update"
> http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/prod_bulletin0900aecd80281c0e.html
>
> ...
>
>
Re: modem not negotiating when receive ANI on ISDN/PRI [ In reply to ]
On Wednesday 15 June 2005 19:29, Rodney Kreisler wrote:

> I'm having a tough time finding out what IOS version I
> should be or am able to run given this box.

I've been running 12.3(12a) for nearly 6 months now, with
no problems whatsoever. Modem portware version is
2.9.5.0.

I'd suggest you look at 12.3, and even though you don't
have enough flash, you could boot the IOS off your TFTP
server.

Mark.

>
> Thanks
>
> Rod
>
> Aaron Leonard wrote:
> > Hi Rod,
> >
> > Sorry to hear about the difficulty during the
> > upgrade, but I'm glad to hear that things are
> > working for you right now.
> >
> > I do have to say that 12.2(2)XB3 wasn't real solid
> > code ... the 12.2XB train didn't really stabilize
> > till around XB6. If you want to run 12.2XB, I'd
> > recommend that you run more recent XB (the latest
> > for the 5300 is 12.2(2)XB16) - EXCEPT that we are
> > not permitted to post 12.2XB code right now due to
> > the "Cisco IOS Software Center Update"
> > http://www.cisco.com/en/US/products/sw/iosswrel/ps51
> >87/prod_bulletin0900aecd80281c0e.html
> >
> > ...
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas