01-12-2011 01:57 AM - edited 03-04-2019 11:03 AM
Hi, Now I am tring to setup Cisco 1812j with ISDN Line.
Here is what I connect the device.
(I am in Japan)
ISDN Line (NTT east) >> DSU(NTT east INS Mate V30Slim with S/T port) >> Cisco 1812j(S/T)
On DSU setting I enable DSU and Disable Terminator.
First of I would like to test outbound call.
Here is the config.
interface BRI0
ip address 192.168.92.2 255.255.255.0
encapsulation ppp
dialer map ip 192.168.92.1 name Router1 broadcast 080********(Cell Phone Number)
dialer-group 1
isdn switch-type ntt
isdn point-to-point-setup
ppp authentication chap
ppp chap password 0 CISCO
ip route 10.92.0.128 255.255.255.248 BRI0 192.168.92.1
Then I test by ping with #debug dialer.
#ping 10.92.0.129
And I could not receive a call by my cell phone landline either.
Here is the debug.
*Jan 12 09:47:02.077: BR0 DDR: place call
*Jan 12 09:47:02.077: BR0 DDR: Dialing cause ip (s=192.168.92.2, d=10.92.0.129)
*Jan 12 09:47:02.077: BR0 DDR: Attempting to dial 080********....
*Jan 12 09:47:10.077: BRI0: wait for isdn carrier timeout, call id=0x8012
*Jan 12 09:47:10.077: BR0 DDR: place call
*Jan 12 09:47:10.077: BR0 DDR: Dialing cause ip (s=192.168.92.2, d=10.92.0.129)
*Jan 12 09:47:10.077: BR0 DDR: Attempting to dial 080*********Jan 12 09:47:10.077: BRI0: call delayed. number redialed too soon.
Success rate is 0 percent (0/5)
I can call from analog phone thru DSU.
But somehow I can not call from 1812j.
I am wondering where is the issue.
Thanks
Sean
Solved! Go to Solution.
01-12-2011 11:07 PM
With one router, you can only verify the connection to the isdn network but perhaps this is also what you mean?
To verify the connection, you need to see return traffic from the network.
What I used to do was turning on "debug isdn q931" and toggle the line. (shut-no shut)
Then check the output for two-way communication.
http://www.cisco.com/en/US/tech/tk801/tk379/technologies_tech_note09186a0080093c1a.shtml
regards,
Leo
01-12-2011 03:01 AM
Perhaps you need to add the following:
isdn sending-complete
This should be added under interface configuration.
http://www.cisco.com/en/US/docs/ios/dial/command/reference/dia_i3.html#wp1011412
regards,
Leo
01-12-2011 04:28 AM
Thanks, lgijssel
I tried that however it still same.
By the way,
Currently it does not light on B1 and B2 at front of the device.
Only "Link" is lighting.
Is this normal?
May be when ISDN connect to the other end it will light up?
Thanks
Sean
01-12-2011 04:42 AM
Other information.
#sh isdn status
Global ISDN Switchtype = ntt
ISDN BRI0 interface
dsl 0, interface ISDN Switchtype = ntt
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 67, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 0 CCBs = 0
The Free Channel Mask: 0x80000003
Total Allocated ISDN CCBs = 0
Looks ok?
Sean
01-12-2011 04:46 AM
Currently it does not light on B1 and B2 at front of the device.
Only "Link" is lighting.
Is this normal?
May be when ISDN connect to the other end it will light up?
Probably yes.
Can you post the output for "debug isdn events"
Leo
01-12-2011 04:14 PM
Here is the debug log.
I turn on debug dialer and debug isdn event.
*Jan 13 00:05:55.378: BR0 DDR: place call
*Jan 13 00:05:55.382: BR0 DDR: Dialing cause ip (s=192.168.92.2, d=10.92.0.134)
*Jan 13 00:05:55.382: BR0 DDR: Attempting to dial 080********
*Jan 13 00:05:55.382: ISDN BR0 EVENT: UserIdle: callid 0x8014 received ISDN_CALL (0x0)
*Jan 13 00:05:55.382: ISDN BR0 EVENT: process_bri_call: call id 0x8014, called_number 080********, Guid B9D5BD58800C speed 64, call type DATA, bchan -1 clng_num none
*Jan 13 00:05:55.550: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x8014 calltype 1 HOST_PROCEEDING..
*Jan 13 00:05:59.550: ISDN BR0 **ERROR**: Ux_BadMsg: Invalid Message for call state 3, call id 0x8014, call ref 0xA, event 0x131A
*Jan 13 00:05:59.550: ISDN **ERROR**: Module-l3_sdl_u Function-Ux_BadMsg Error-Source ID = 300 Event = 131A
*Jan 13 00:06:00.038: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x8014 calltype 1 HOST_DISCONNECT
*Jan 13 00:06:00.038: BRI0: wait for isdn carrier timeout, call id=0x8014
*Jan 13 00:06:00.102: ISDN BR0 EVENT: process_rxstate: ces/callid 1/0x8014 calltype 1 HOST_DISCONNECT_ACK.
*Jan 13 00:06:01.378: BR0 DDR: place call
*Jan 13 00:06:01.378: BR0 DDR: Dialing cause ip (s=192.168.92.2, d=10.92.0.134)
*Jan 13 00:06:01.378: BR0 DDR: Attempting to dial 080********
*Jan 13 00:06:01.378: BRI0: call delayed. number redialed too soon..
Success rate is 0 percent (0/5)
Sean
01-12-2011 09:59 PM
I think I may be find the issue.
I was testing the line by calling to my cellphone.
But ISDN does not allow to call as voice as data.
Now I test calling to the other landline number which connect with other ISDN Router,
The debug log is not same as what I call to cell phone as below.
*Jan 13 05:54:28.211: BR0 DDR: place call
*Jan 13 05:54:28.211: BR0 DDR: Dialing cause ip (s=192.168.92.2, d=10.92.0.129)
*Jan 13 05:54:28.211: BR0 DDR: Attempting to dial 03********.
*Jan 13 05:54:30.143: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 03******* N/A.
I am going to setup the other ISDN Router.
Hopefully works.
By the way,
How can I test the line connectivity if I only have one ISDN Router?
May be #show isdn status?
Thanks
Sean
01-12-2011 11:07 PM
With one router, you can only verify the connection to the isdn network but perhaps this is also what you mean?
To verify the connection, you need to see return traffic from the network.
What I used to do was turning on "debug isdn q931" and toggle the line. (shut-no shut)
Then check the output for two-way communication.
http://www.cisco.com/en/US/tech/tk801/tk379/technologies_tech_note09186a0080093c1a.shtml
regards,
Leo
01-13-2011 11:38 PM
Thanks Leo.
It works now.
The problem was CHAP username was wrong.
I just change the username to same name as hostname.
http://www.cisco.com/en/US/tech/tk713/tk507/technologies_tech_note09186a00800b4130.shtml
debug isdn q931
and
debug ppp authentication
debug ppp negociation
Those command helps me.
Thanks
Sean
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