ISDN PRI dialer connections to AS5300

Swapping out an AS5200 running 11.3 with an AS5300 running 12.3. Copied the same config from the 5200 to the 5300. ISDN Pri calls from remote routers to the 5200 connect and stay connected. Calls from the same router to the 5300 disconnect after 1 sec. Q931 debug shows x8090 disconnect code being sent from the 5300. Suspect AAA auth issue because I don't see any attempts logged in tacacs server (CiscoSecure). When I debug ppp auth the only thing out of the ordinary is a "PPP Authorization Required" message but the AAA author configs are the same on both 5200 and 5300. When I run a debug on tacacs on the 5300 I see "pass" statuses coming back from the server.

Use below commands to troubleshoot.
â¢ debug isdn q931 - To check ISDN connections as outbound calls are initiated.
â¢ debug ppp negotiation - To see if a client is passing PPP negotiation. A high number of concurrent PPP negotiations can overwhelm the router CPU.
â¢ debug ppp authentication - To see if a client is passing authentication. If you are using a version prior to Cisco IOS release 11.2, use the debug ppp chap command instead.
â¢ debug ppp error - To display protocol errors and error statistics associated with PPP connection negotiation and operation.

Similar Messages

ISDN PRI multilink connection to multiply BRI's

Can somebody help me? I need to configure
connection that will be initiated from
Cisco2611 (R1) with 8 BRI's to Cisco3620 (R2) with PRI module. After authenti-
cation R2 performs callback to R1 and brings up up to 8 B-channel according traffic load.
10x
Alex

Traffic should be generated from the originating site.So a trigger should be generated from the BRI site.Refer URL for configuring
BRI http://cisco.com/en/US/tech/tk801/tk379/technologies_configuration_example09186a008010456b.shtml

ISDN PRI redundancy on AS5300

I am having cisco AS5300 router with a ISDN PRI line terminating over it.
I would like to have redundancy for the existing PRI line with another PRI.
Is this possible ? If yes where can I get a sample configurations.

If it's redundancy for the dialin, you have two options:
1) Make all the clients add the secondary number to dial
2) Request a single number for the two ISDN PRI's from your telco (this is without a doubt the easiest).
If it's redundancy for dialout, just add the interface in the same dialer pool as the first one...:
interface Serial0:15
dialer pool-member 1
interface Serial1:15
dialer pool-member 1
Did it help?

Remote dialin access using isdn pri

I configured dialin accesss using isdn pri interface. It works fine just for one user. When another user dials in (using same or different local username/password), the previous one loses the connectivity. Actually the statuses seem fine for the previous user: I can see him under "sh users" as well as host route in routing table. ppp session stays idle. There is no ip connectivity anymore.
aaa authentication ppp default local
isdn switch-type primary-net5
username test1 password 7 03105E18125E
username test2 password 7 06120A32581C
controller E1 1/0
pri-group timeslots 1-31
controller E1 1/1
pri-group timeslots 1-31
interface Serial1/0:15
no ip address
dialer pool-member 1
dialer idle-timeout 7200
isdn switch-type primary-net5
interface Serial1/1:15
no ip address
dialer pool-member 1
dialer idle-timeout 7200
isdn switch-type primary-net5
interface Dialer0
ip unnumbered FastEthernet0/0.1
encapsulation ppp
dialer pool 1
dialer caller "XYZ"
dialer-group 1
peer default ip address pool netm
fair-queue
ppp authentication chap pap
ip local pool netm 10.31.32.65 10.31.32.126

Hi Starman,
configure the following command under dialer inetrafce and check the issue.
int di0
dialer load-threshold 255 either
dialer ilde-timeout 120
if you want another to use the isdn line then create another dialer interface.
clarify me whether the users are accessing the pri from the same location or different locations using different isdn no's.
If users are present in two different locations then best solution is create seperate dialer interface for users.
Thanks,
Satish

No carrier from PVDM2-36DM via ISDN PRI link

The network topology is
Modem --> [FXS][cisco 2821][E1] --> ISDN PRI --> [E1][cisco 2811][PVDM2-36DM]
ISDN PRI link is operated correctly, debug isdn q931 shows that connection is established. Info message is
*Jul 23 06:27:45.407: %ISDN-6-CONNECT: Interface Serial1/0:1 is now connected to 555 N/A
Unfortunately, no carrier signal is going from modem to line.
Configuration of Cisco Routers is below.
1st (2821)
==========
controller E1 0/2/0
framing NO-CRC4
pri-group timeslots 1-2,16
interface Serial0/2/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn incoming-voice modem
no cdp enable
dial-peer voice 1 pots
destination-pattern 555
port 0/3/0
voice-port 0/3/0
cptone RU
dial-peer voice 888 pots
destination-pattern .T
port 0/2/0:15
2nd (2811)
==========
controller E1 1/0
framing NO-CRC4
pri-group timeslots 1-2,16
interface Serial1/0:15
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn timer T310 120000
isdn not-end-to-end 64
isdn protocol-emulate network
isdn incoming-voice modem
no cdp enable
line 0/322 0/357
modem InOut

> The PVDM2-DM works only with NM-xT1/E1.
Yes, of course, it is well known fact. We are using NM-1CE1T1-PRI. See "show diag" output below.
Slot 0:
C2811 Motherboard with 2FE and integrated VPN Port adapter, 2 ports
Port adapter is analyzed
Port adapter insertion time unknown
EEPROM contents at hardware discovery:
PCB Serial Number : FOC11070F5L
Hardware Revision : 1.0
Top Assy. Part Number : 800-26920-03
Board Revision : A0
Deviation Number : 0
Fab Version : 03
RMA Test History : 00
RMA Number : 0-0-0-0
RMA History : 00
Processor type : 87
Hardware date code : 20070214
Chassis Serial Number : FHK1109U00A
Chassis MAC Address : 001b.2aa3.c1c8
MAC Address block size : 24
CLEI Code : COM7C00ARA
Product (FRU) Number : CISCO2811
Part Number : 73-10258-04
Version Identifier : V04
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF C1 8B 46 4F 43 31 31 30 37 30 46 35 4C 40
0x10: 03 E7 41 01 00 C0 46 03 20 00 69 28 03 42 41 30
0x20: 88 00 00 00 00 02 03 03 00 81 00 00 00 00 04 00
0x30: 09 87 83 01 32 3F 46 C2 8B 46 48 4B 31 31 30 39
0x40: 55 30 30 41 C3 06 00 1B 2A A3 C1 C8 43 00 18 C6
0x50: 8A 43 4F 4D 37 43 30 30 41 52 41 CB 8F 43 49 53
0x60: 43 4F 32 38 31 31 20 20 20 20 20 20 82 49 28 12
0x70: 04 89 56 30 34 20 D9 02 40 C1 FF FF FF FF FF FF
PVDM Slot 0:
36 port PVDMII digital modem PVDM daughter card
Hardware Revision : 1.0
Part Number : 73-10102-03
Board Revision : C0
Deviation Number : 0
Fab Version : 03
PCB Serial Number : FOC10354YRW
RMA Test History : 00
RMA Number : 0-0-0-0
RMA History : 00
Processor type : 00
Product (FRU) Number : PVDM2-36DM
Version Identifier : V01
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 04 90 41 01 00 82 49 27 76 03 42 43 30
0x10: 88 00 00 00 00 02 03 C1 8B 46 4F 43 31 30 33 35
0x20: 34 59 52 57 03 00 81 00 00 00 00 04 00 09 00 CB
0x30: 8A 50 56 44 4D 32 2D 33 36 44 4D 89 56 30 31 20
0x40: D9 02 40 C1 FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Slot 1:
NM-1CE1T1_PRI Port adapter, 1 port
Port adapter is analyzed
Port adapter insertion time unknown
EEPROM contents at hardware discovery:
Hardware Revision : 1.0
Top Assy. Part Number : 800-21550-02
Board Revision : A0
Deviation Number : 0-0
Fab Version : 03
PCB Serial Number : FOC104753CA
RMA Test History : 00
RMA Number : 0-0-0-0
RMA History : 00
Fab Part Number : 28-5935-03
Manufacturing Test Data : 00 00 00 00 00 00 00 00
Field Diagnostics Data : 00 00 00 00 00 00 00 00
Product (FRU) Number : NM-1CE1T1-PRI
Version Identifier : V01
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 03 9D 41 01 00 C0 46 03 20 00 54 2E 02
0x10: 42 41 30 80 00 00 00 00 02 03 C1 8B 46 4F 43 31
0x20: 30 34 37 35 33 43 41 03 00 81 00 00 00 00 04 00
0x30: 85 1C 17 2F 03 C4 08 00 00 00 00 00 00 00 00 C5
0x40: 08 00 00 00 00 00 00 00 00 CB 8D 4E 4D 2D 31 43
0x50: 45 31 54 31 2D 50 52 49 89 56 30 31 20 FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

ISDN PRI & BRI configration

Hi,
I have 2800 series route at central location with PRI line and remote location with BRI line and DLINK router. i have 10 remote site.
Now i want to connect my multiple remote site through BRI to my PRI at central location
can you guide me with the configration at the central location PRI part
I am in INDIA
Bhargav

in india we have E1 as a PRI follow the procedure.
Configuring Channelized E1 ISDN PRI
To configure ISDN PRI on a channelized E1 controller, use the following commands beginning in global configuration mode:
Command Purpose
Step 1
isdn switch-type switch-type
Selects a service provider switch type that accommodates PRI. (Refer to Table 17 for a list of supported switch type keywords.)
Step 2
controller e1 slot/port
or
controller e1 number
Defines the controller location in the Cisco 7200 or Cisco 7500 series router by slot and port number.
Defines the controller location in the Cisco 4000 series or the Cisco AS5200 universal access server by unit number.1
Step 3
framing crc4
Defines the framing characteristics as cyclic redundancy check 4 (CRC4).
Step 4
linecode hdb3
Defines the line code as high-density bipolar 3 (HDB3).
Step 5
pri-group [timeslots range]
Configures ISDN PRI.
.1 Controller numbers range 0 through 2 on the Cisco 4000 series and 1 to 2 on the Cisco AS5200 access server.
If you do not specify the time slots, the specified controller is configured for 30 B channels and 1 D channel. The B channel numbers range 1 to 31; channel 16 is the D channel for E1. Corresponding serial interfaces numbers range 0 to 30. In commands, the D channel is interface serial controller-number:15. For example, interface serial 0:15.
Table 17lists the keywords for the supported service provider switch types to be used in Step 1 above.
Dlink you have to configure simple dial-up connectivity with PRI.
Thanks,
Dharmesh Purohit

Why do we need to assign ip for the D channel ISDN-PRI

Why do we need to assign ip address to the D channel (signaling ) when we configure ISDN-PRI in the example below :
http://www.cisco.com/univercd/cc/td/doc/product/access/ap/ap_ts3/ap_ts3sw/apswisd.htm
<quote>
Step 1:Specify the D channel of the first Primary Rate Interface (PRI):
AS01(config)# interface Serial 0:23
AS01(config-if)#
Step 2: Assign an IP address and subnet mask to the interface:
AS01(config-if)# ip address 172.16.254.253
</quote>
Regards

You can assing one there, and / or on dialer interfaces. It depends on what you are doing.
These will be the address used by PPP when it runs on the B-channels.

Ask module E1 ISDN PRI (for data modem)

Hello,
my topology like this :
in the headoffice, I Have cisco 2911 (no pvdm card) and ISDN PRI from telco,
in the branch, i use modem Atrie 288LCD for dial .
what is the modules should i buy for cisco 2911 in the headoffice ..?
Thanks

http://www.cisco.com/en/US/prod/collateral/modules/ps2641/product_data_sheet0900aecd8050918e.html

How to configure isdn pri on gigabit interface on AS 5850 router

hello All,
i currently have a project at hand which is a voip project using sip protocol. my client wants to send voip traffic to my router using STM interface with SIP protocol. But the challenge is how do i convert the sip protocol to ISDN PRI on another STM gigabit interface before sending it to my PSTN switch for onward termination to the customer. currently i use serial interface to communicate with my PSTN using E1 for other existing clients in other to terminate calls to customers. please see sample configuration below:
interface Serial10/1:15
no ip address
encapsulation hdlc
no snmp trap link-status
trunk-group JKN
isdn switch-type primary-net5
isdn incoming-voice modem 64
isdn map address .* plan unknown type unknown
isdn send-alerting
no cdp enable
thank you.
Adekunle

hello n-kirillov,
Yes i mean STM as Synchronous Transport Module for Optical Network. currently, the medium of transport for communication between my router and the PSTN switch is the serial interface whose configuration i have shown above. also currently E1 pri cables are connected to this serial interface and E1s are provision for this serial interfaces directly from the switch for communication with the PSTN switch.
the question now is that my switching team now wants be to communicate with their switch using fibre from STM interface on my router without using PRI cables. is this achievable? if yes what is the configuration like?

ISDN PRI to BRI converter

Hi,
We have ISDN PRI connected to a Cisco 2851 router and using it for voice. Is it possible to take few BRI connections using some kind of converter (module) installed on the router??
I heard some vendor like Nortel have this kind of converter...
Can someone give your input...
Regards
Vijay

Yes, the router can do that. See:
http://www.cisco.com/en/US/tech/tk652/tk653/technologies_tech_note09186a00804794c6.shtml
Hope this helps, please rate post if it does!

Reserving Timeslots on a ISDN PRI

Hi,
Can it be configured on the ISDN PRI link of the Central Location Data Center, reserving 10 Timeslots for taking the calls from one particular Branch Location and another 10 from another individual branch and remaining 10 from left over Branch Sites.
Can we use the channel-group command for this type of the configuration.
Can the 15th timeslot (for e.g., Serial 2/0:15) used when reserving the timeslots under the channel-group command.
Request anyone help me finding a solution.
Regards,
Keshava Raju
[email protected]

You cannot partition the PRI and if you want to limit calls, it's particularly complicated because what you want to do, is to not answer or reject calls when the group a branch pertains to, is full.
In my knowledge, this is not possible. You can hack something with radius to do that authentication is denied when group is full, but this is not the same as not taking the calls.
Hope this helps, please rate post if it does!

ISDN PRI Configuration errors

Dears,
I trying to configure a ISDN PRI on a 1751-V router and the following error occur:
CISCO_BARR(config-controller)#pri-group time 1-6
%Controller tdm clock does not have data capability
%Insufficient HDLC resource for pri-group - it has been removed
How do I to configure ISDN PRI in that router ?
More information:
Cisco 1751-V
Router Version: c1700-ipvoice-mz.123-9d.bin

Hi,
Please make sure that you putting the T1/E1 card in the WVIC and not VIC slot as PRI can do
voice but it is still considedred as data, so if you try to confiugre this in a slot that
is VIC (instead of VWIC) only then it will not work for you. Furthermore, you needed to
have the tdm clock command set to both and not just voice, as you are creating a PRI,
which, again, is Data, but can do voice too.
here is the example of command :--
tdm clock T1 2/0 both export line
hth
CJ

Measure telephone traffic on an ISDN PRI

Has anyone developed an EEM Scrip to measure telephone traffic on an ISDN PRI interface on a voice gateway? Preferably the traffic measurements would be in Hundred Call Seconds (CCS) or Erlangs. It would appear that the “show isdn service” command could be used to determine the state of the individual “B” channels on the PRI.

If the "show isdn service" command gives you what you want, then you could build a policy using the timer event detector (watchdog timer) to run the command periodically and produce the desired reports. I don't know of anyone that has already done this, though.

Key interceptor for dialer/connect key (green) and disconnect key (red)

Hi,
Can someone tell me, how can i capture green key (dialer/connect) and red key (disconnect). In the emulator, i am able to capture all the keys as mentioned in the samples/examples. But in windows mobile (imate), it is not capturing these keys.
I want to know how i can capture these system keys in MIDP 2.0.
Thanks, and regards.

are you able to display key codes in your app (like 1 for key one, etc...)?

SRST, ISDN PRI

Customer reports that when the WAN link fails calls to PSTN get dropped because ISDN PRI drops and reassoicates with SRST.
Souldn't there be a seemless failover to SRST for calls incomming/outgoing to PSTN

I'm assuming your gateway is using MGCP. If so, this is expected behavior. During normal operation, an MGCP PRI backhauls the D channel to Callmanager. When the WAN goes down, so does the D channel. When the D channel drops, so do your calls. It then has to reestablish the D channel with the local gateway. Take a look at the following link.
http://supportwiki.cisco.com/ViewWiki/index.php/Calls_drop_when_switching_from_MGCP_to_SRST_mode_or_rehoming_from_SRST_to_MGCP
Hope this helps.
Brandon

ISDN PRI dialer connections to AS5300

Similar Messages

Maybe you are looking for