I have an Avaya PBX here, and I am attempting to connect an Adtran 924E thru a PRI connection. I have a SIP circuit coming into the Adtran on NET1, and I am trying to use NET4 to connect the PBX. Our phone system version is not updated enough to do SIP trunking, which is why I am trying to use a PRI.
I have tried going thru https://supportforums.adtran.com/docs/DOC-2254, but I was unsuccessful. If anyone has a config they could post for example, that would be great!
Thanks David! It was the switch type on the PBX...I have to make some quick changes to test calls, but I have 23 B-channels in service right now. Thanks again!
Here you go:
interface t1 0/4
tdm-group 1 timeslots 1-24 speed 64
no shutdown
interface pri 1
description pri 1
connect t1 0/4 tdm-group 1
role network b-channel-restarts disable
no shutdown
isdn-group 1
connect pri 1
ip sip
ip sip udp 5060
voice feature-mode network
voice forward-mode network
voice trunk T01 type sip
description "SIP Trunk"
sip-server primary X.X.X.X (IP Address of ITSP)
voice trunk T02 type isdn
description "PBX"
resource-selection circular ascending
connect isdn-group 1
rtp delay-mode adaptive
voice grouped-trunk VOIP
trunk T01
accept $ cost 0
voice grouped-trunk PRI
trunk T02
accept $ cost 0
Let me know if you have any questions.
I had most of that in the config...my problem is the connection between the PBX and the Adtran...
On the PBX, I have a signaling group showing "in-service", but all the ports in the trunk group show "out-of-service-FE"
Just for clarity, I have to use a T1-cross cable to connect the 2, correct? Maybe I have something set incorrectly on the PBX side...
I really appreciate the help!
Is the Adtran showing that the PRI is up?
Are there any errors?
The interface shows UP in the Adtran, although I am seeing CSS errors on T1 0/4...I'm not sure what that means.
1970.01.01 03:02:24 T1.t1 0/4 CSS 15 min threshold exceeded
1970.01.01 03:18:03 T1.t1 0/4 CSS 15 min threshold exceeded
1970.01.01 03:32:09 T1.t1 0/4 CSS 15 min threshold exceeded
1970.01.01 03:47:48 T1.t1 0/4 CSS 15 min threshold exceeded
1970.01.01 04:01:53 T1.t1 0/4 CSS 15 min threshold exceeded
1970.01.01 04:17:32 T1.t1 0/4 CSS 15 min threshold exceeded
1970.01.01 04:31:37 T1.t1 0/4 CSS 15 min threshold exceeded
1970.01.01 04:47:14 T1.t1 0/4 CSS 15 min threshold exceeded
TA924e#sho int pri 1
pri 1 is UP
Description: PRI to PBX
Switch protocol: National ISDN 2
Signaling role: network (NT) b-channel-restarts disabled
Ringing signal: provide inband ringing signal to calling TE
Calling-party override: disabled
Calling-party presentation: allowed
Calling-party number: (no number configured)
digits transferred all
ISDN name-delivery: via Setup msg / Facility IE
progress indicator #8 in alerting message: enabled
progress indicator #2 in connect message: disabled
progress indicator #1 in setup message: disabled
progress indicator #3 in setup message: disabled
progress indicator location: public
resource-selection: circular descending
TBCT: disabled
Connected interface: t1 0/4 tdm-group 1
Channel status 123456789012345678901234
.......................D
Legend: - = Unallocated . = Inactive
A = Active B channel B = Backup D channel
D = Active D channel M = Maintenance
R = Restart
2853 packets input, 24755 bytes, 0 no buffer
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame
0 abort, 0 discards, 0 overruns
2886 packets output, 13945 bytes, 0 underruns
TA924e#
The presence of CSS errors indicates that there is either two timing sources on the T1 interfaces or no clock at all.
You can issue the command "show system" to see the timing source configuration and active timing source on the unit.
You can change the timing source by the command "timing-source <internal | t1 0/X>.
I am using the provider's T1 as the timing source...
"timing-source t1 0/1"
Here is my config in detail:
interface t1 0/1
tdm-group 1 timeslots 1-24 speed 64
no shutdown
!
interface t1 0/2
shutdown
!
interface t1 0/3
shutdown
!
interface t1 0/4
description PRI to PBX
tdm-group 1 timeslots 1-24 speed 64
no shutdown
!
!
interface pri 1
description PRI to PBX
isdn name-delivery setup
connect t1 0/4 tdm-group 1
role network b-channel-restarts disable
no shutdown
interface ppp 1
ip address xxx.xxx.xxx.xxx 255.255.255.252
media-gateway ip primary
qos-policy out PIP_ADVANTAGE
max-reserved-bandwidth 90
no lldp send-and-receive
no shutdown
cross-connect 1 t1 0/1 1 ppp 1
!
!
isdn-group 1
connect pri 1
!
!
!
!
timing-source t1 0/1
!
!
router bgp xxxxx
no auto-summary
no synchronization
network 0.0.0.0 mask 0.0.0.0
network xxx.xxx.xxx.0 mask 255.255.255.252
redistribute static
redistribute connected
neighbor xxx.xxx.xxx.xxx
no default-originate
soft-reconfiguration inbound
remote-as xx
!
Based upon the errors the timing on 0/1 is good the problem is on 0/4.
Try the following:
timing-source t1 0/1
timing-source internal secondary
I have done so...still getting CSS errors. Also, still no B-channels.
What's the phone system's settings for the PRI?
DS1 page...
display ds1 8b09 Page 1 of 2
DS1 CIRCUIT PACK
Location: 08B09 Name: Adtran924
Bit Rate: 1.544 Line Coding: b8zs
Line Compensation: 1 Framing Mode: esf
Signaling Mode: isdn-pri
Connect: network
TN-C7 Long Timers? n Country Protocol: 1
Interworking Message: PROGress Protocol Version: a
Interface Companding: mulaw CRC? n
Idle Code: 11111111
DCP/Analog Bearer Capability: 3.1kHz
T303 Timer(sec): 4
Slip Detection? n Near-end CSU Type: integrated
Echo Cancellation? y
EC Direction: inward
EC Configuration: 4
Signaling Group page...
display signaling-group 6 Page 1 of 5
SIGNALING GROUP
Group Number: 6 Group Type: isdn-pri
Associated Signaling? y Max number of NCA TSC: 0
Primary D-Channel: 08B0924 Max number of CA TSC: 0
Trunk Group for NCA TSC:
Trunk Group for Channel Selection: 6
Supplementary Service Protocol: a
Trunk group page...
display trunk-group 6 Page 1 of 23
TRUNK GROUP
Group Number: 6 Group Type: isdn CDR Reports: y
Group Name: Adtran 924 COR: 66 TN: 1 TAC: 806
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? n Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: tie Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4
TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc
Trunk Hunt: ascend QSIG Value-Added? n
Digital Loss Group: 13
Incoming Calling Number - Delete: Insert: Format:
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0
display trunk-group 6 Page 2 of 23
TRUNK FEATURES
ACA Assignment? n Measured: none Wideband Support? n
Internal Alert? n Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member:
Send Name: y Send Calling Number: y
Used for DCS? n
Suppress # Outpulsing? n Format: public
Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider
Replace Restricted Numbers? n
Replace Unavailable Numbers? n
Send Connected Number: y
Hold/Unhold Notifications? n
Send UUI IE? y Modify Tandem Calling Number? n
Send UCID? n
Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? y
US NI Delayed Calling Name Update? n
Network (Japan) Needs Connect Before Disconnect? n
Signaling group status...
status signaling-group 6
STATUS SIGNALING GROUP
Group ID: 6 Active NCA-TSC Count: 0
Group Type: isdn-pri Active CA-TSC Count: 0
Signaling Type: facility associated signaling
Group State: in-service
Primary D-Channel
Port: 08B0924 Level 3 State: in-service
Secondary D-Channel
Port: Level 3 State: no-link
Trunk Group status...
status trunk 6 Page 1
TRUNK GROUP STATUS
Member Port Service State Mtce Connected Ports
Busy
0006/001 08B0901 OOS/FE-PINS no
0006/002 08B0902 OOS/FE-PINS no
0006/003 08B0903 OOS/FE-PINS no
0006/004 08B0904 OOS/FE-PINS no
0006/005 08B0905 OOS/FE-PINS no
0006/006 08B0906 OOS/FE-PINS no
0006/007 08B0907 OOS/FE-PINS no
0006/008 08B0908 OOS/FE-PINS no
0006/009 08B0909 OOS/FE-PINS no
0006/010 08B0910 OOS/FE-PINS no
0006/011 08B0911 OOS/FE-PINS no
0006/012 08B0912 OOS/FE-PINS no
0006/013 08B0913 OOS/FE-PINS no
0006/014 08B0914 OOS/FE-PINS no
0006/015 08B0915 OOS/FE-PINS no
0006/016 08B0916 OOS/FE-PINS no
0006/017 08B0917 OOS/FE-PINS no
0006/018 08B0918 OOS/FE-PINS no
0006/019 08B0919 OOS/FE-PINS no
0006/020 08B0920 OOS/FE-PINS no
0006/021 08B0921 OOS/FE-PINS no
0006/022 08B0922 OOS/FE-PINS no
0006/023 08B0923 OOS/FE-PINS no
It looks like you have both the Adtran and PBX set to "network".
Try setting the PBX to "user".
Changed DS1 to "Connect:pbx / Interface:user"
Same result. No B-channels.
Pull out the PRI in 0/4 and plug it back in.
Did the errors clear?
I really appreciate you taking the time to help me out. Unfortunately, no change yet.
As far as the config goes it looks OK.
If you are still having timing issues I am not sure what else to try. (Maybe reboot everything?)
Perhaps someone from Adtran can suggest something.
Mike,
Try setting your timing source to the PRI interface instead of the data interface, I usualy set it that way because my data connection is on eth 0/1 instead of T1, but I am wondering if there is a timing mismatch because the data and voice configuration run at differently.
timing-source t1 0/4
!
timing-source internal secondary
!
Also not sure if the PBX requires it but you should also added the following to you pri interface:
interface pri 1
digits-transferred 7 (insert what your PBX expects)
A couple of times I have had to add the following to the isdn-group to get some PBXs to connect properly:
isdn-group 1
min-channels 1
And finally I did not see your Voice configs in your example config so be sure you have the following added:
voice trunk T01 type isdn
description "PRI"
resource-selection circular descending
connect isdn-group 1
rtp delay-mode adaptive
!
voice grouped-trunk PRI
no description
trunk T04
accept $ cost 0
!
And finaly you will need to ensure your SIP trunks are configured properly
Hope it helps
John Wable
Also here is another post that maybe similar to your issue:
I appreciate the help. Still unsuccessful. Can you confirm I should be using a T1-cross cable? I can't even get a D-channel with a straight cable. I have even contacted Adtran support, and have been told the config looks good. Frustrating.
I guess it doesn't hurt to try.