Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

AT&T T1 Outbound Issues

Status
Not open for further replies.
Jmack23

Jmack23

Programmer
Mar 17, 2017
24
US
Hello,

I am trying to get some help with configuration of a T1 on a IP office 500 V2.

The signaling is ESF, B8ZS, CPE.
Clock Quality is set to Network, CRC Checking enabled.

I have tried Direction Bothway and outgoing.
I have tried Bearer Voice, Data and both.
I have tried E & M - Tie, Ground Start, Loop Start, E & M - Switched 56K.
AT&T told me the line is a Wink start.

When I make an outbound call as this is only for long distance I get a fast busy. The AT&T tech wasn't sure what the issue was. I am hoping some of you might know. I was thinking it was a similar issue to the NI2_CALLED_PARTY_TYPE=UNKNOWN but I am unsure how to specific this for a T1 circuit.

Thanks for any assistance.
 
Sort by date Sort by votes
Under IPO manager I put them in service. Is this what you are referring to?
 
Upvote 0 Downvote
yes, and your positive you have it configured correctly? Also line sub type should be Pri and switch type should be NI2, At lease that is how ours is set up
 
Upvote 0 Downvote
I am not. I only received information on the framing, zero suppression and wink start. The system comes up and goes idle. You can see the configuration information I have and a test call.

 
Upvote 0 Downvote
Here is a trace for just the T1 settings:

UNICODE-UTF8
enu
492663mS T1Line: line: 9.24: State= Idle ep none CanMakeCall: Yes
492665mS T1Line: line: 9.24: State: Idle CMMessage: CMSetup
492666mS T1Line: line: 9.24: State Change Idle -> Initiated
492666mS T1Line: line: 9.24: Sending LL Message Seize
492674mS PRN: rtpRelayFilter ioctl(open) rc: 0 rtpRelayId: 1
492674mS PRN: rtpRelayFilter configure rc: 0 rtpRelayId: 1
492675mS T1Channel: chan: E&M 9.24: Transmit T1EMOffHook
492676mS T1CAS: Channel E&M 9.24: TX: 0000 -> 1111
492676mS T1Channel: chan: E&M 9.24: StateChange Idle->OutgoingHandshake
492676mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), speech path off
492686mS T1Channel: chan: E&M 9.24: StateChange OutgoingHandshake->AwaitWinkStart
492788mS T1CAS: Channel E&M 9.24: RX: 0000 -> 1111
492788mS T1Channel: chan: E&M 9.24: Receive T1EMOffHook
492788mS T1Channel: chan: E&M 9.24: EventRx T1EMOffHook state=AwaitWinkStart
492788mS T1Channel: chan: E&M 9.24: StateChange AwaitWinkStart->WinkGuard
492868mS T1Channel: chan: E&M 9.24: StateChange WinkGuard->WinkConfirm
493018mS T1CAS: Channel E&M 9.24: RX: 1111 -> 0000
493018mS T1Channel: chan: E&M 9.24: Receive T1EMOnHook
493018mS T1Channel: chan: E&M 9.24: EventRx T1EMOnHook state=WinkConfirm
493018mS T1Channel: chan: E&M 9.24: StateChange WinkConfirm->OutgoingActiveDial
493019mS T1Line: line: 9.24: State= Initiated RxMessage: Wink
493608mS T1Channel: chan: E&M 9.24: StateChange OutgoingActiveDial->Talk
493608mS T1Channel: chan: E&M 9.24: Transmit T1EMOffHook
493609mS T1Line: line: 9.24: State= Initiated RxMessage: StartDial
493609mS T1Line: line: 9.24: State Change Initiated -> OverlapSend
493610mS T1Line: line: 9.24: Sending LL Message DialDigits
493612mS T1Dialler: dialler: -265929868.24: Digit Store: 15159874123
493612mS T1Dialler: dialler: -265929868.24: Dial DTMF 1
493612mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), send digit 49 (tone 1)
493752mS T1Dialler: dialler: -265929868.24: Dial DTMF 5
493752mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), send digit 53 (tone 5)
493892mS T1Dialler: dialler: -265929868.24: Dial DTMF 1
493892mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), send digit 49 (tone 1)
494032mS T1Dialler: dialler: -265929868.24: Dial DTMF 5
494032mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), send digit 53 (tone 5)
494172mS T1Dialler: dialler: -265929868.24: Dial DTMF 9
494172mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), send digit 57 (tone 9)
494312mS T1Dialler: dialler: -265929868.24: Dial DTMF 8
494312mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), send digit 56 (tone 8)
494452mS T1Dialler: dialler: -265929868.24: Dial DTMF 7

********** SysMonitor v10.1.0.1.0 build 3 [connected to 10.5.8.6 (Avaya_Sukup_Exp (Server Edition(E)))] **********
494452mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), send digit 55 (tone 7)
494490mS PRN: Monitor Status S-Edition Expansion (V2) 10.1.0.1.0 build 3
494490mS PRN: LAW=U PRI=2, BRI=0, ALOG=4, VCOMP=74, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=9 VMAIL=1(VER=3 TYP=2) 1-X=0 CALLS=1(TOT=5)
494592mS T1Dialler: dialler: -265929868.24: Dial DTMF 4
494592mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), send digit 52 (tone 4)
494732mS T1Dialler: dialler: -265929868.24: Dial DTMF 1
494732mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), send digit 49 (tone 1)
494872mS T1Dialler: dialler: -265929868.24: Dial DTMF 2
494872mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), send digit 50 (tone 2)
495012mS T1Dialler: dialler: -265929868.24: Dial DTMF 3
495012mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), send digit 51 (tone 3)
495152mS T1DSP: PRIU DSP 3: channel 24 (timeslot 48), speech path on
495152mS T1Line: line: 9.24: State= OverlapSend RxMessage: DigitsDone
495153mS T1Line: line: 9.24: State Change OverlapSend -> Active

********** Warning: Logging to Screen Stopped **********
 
Upvote 0 Downvote
On the channels tab make sure they are put in service
 
Upvote 0 Downvote
Harkening back to Merlin Legend days and T1 services, it would normally be
Clock > Network
Line Sub Type > T1
Framing > ESF
Zero Suppression > B8ZS
Line Signalling > CPE
Direction > Bothway
Bearer > Any
Type > E & M - Tie
Incoming Trunk Type > Wink-Start
Outgoing Trunk Type > Wink-Start
 
Upvote 0 Downvote
Are you sure they are programmed as a real T1 versus a PRI? I haven't had ATT deliver a true T1 for years. It is always a PRI, NI2. Try changing to that versus T1.
 
Upvote 0 Downvote
Do you have access to System Status? Does the T1 show it comes into service or does the trunk stay out of service?
 
Upvote 0 Downvote
It shows idle in system status. I can see the call on channel 24 when trying to dial out.
 
Upvote 0 Downvote
Are you sending the main number out via ARS? Maybe ATT doesn't like what they are seeing.
 
Upvote 0 Downvote
I am, should I try to just dial with a line id?
 
Upvote 0 Downvote
Is the main number associated with this LD T1 or with their other PRI/etc? It could be that if you are sending the main number and it isn't associated with ATT's LD T1 it is rejecting it.
 
Upvote 0 Downvote
Your ticket from ATT didn't post properly. Have they said what they are seeing on their end? Do they see the call attempt? If so, they should be able to see why they are rejecting it.
 
Upvote 0 Downvote
I am waiting to hear more from them as I sent them information on the configuration but I don't expect a speedy response.
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

D
  • Question
IP DECT R4 Issues
Replies
0
Views
165
DeathfromAvaya
D
RedTech443
  • Locked
  • Question
Outbound SIP calling adding a "L"
Replies
3
Views
568
derfloh
derfloh
4thright
  • Locked
  • Question
IP Office 500 v2 - T1 Trunking
Replies
14
Views
1K
derfloh
derfloh
smartedge1
  • Locked
  • Question
PRI OUTBOUND ISSUE ON EXPANSION SERVER
Replies
4
Views
594
smartedge1
smartedge1
chadphoneguy
  • Locked
  • Question
Avaya IP Office VM to email issues
Replies
4
Views
823
eaglepromopro
eaglepromopro

Part and Inventory Search

Sponsor

Back
Top