Avaya 8700 to Nortel m1 opt 61C over PRI tie trunks Interop problem

[rheusdens]

I have a scenario where we are intconecting an Opt. 61C rel 25.30 with an avaya s8700 via pri. The 6 PRI's from the CO that were feeding the 61C are being moved over to the avaya and the M1 is being tied to the Avaya over PRI. This will allow the customer to transition over service to the 8700 over a two year period. Avaya has enabled a green feature to allow caller ID to function over the sl1/dms100 protocol since the NI2 capabilities of the 61C are limited and the customer does NOT have Qsig. I need help getting this working from anyone who has perhaps done this in the past. We can get the D channels up no problem but the B channels just go into a lockout state. I do the M1 side but if we can perhaps get screenshots of a D channel on the m1 and the RDB and the Ds1 and route config on the avaya, that would help us out alot. Avaya and Nortel are in no way assisting us with this venture so any ideas would be great. The B channels show idle when we do an sl1 tie and the D channel shows ok, but thye show on teh avaya as far end locked out. Same effect if we goto D100 as the protocol on the m1. I beleive its something on the avaya side but im out of ideas. Thanks

 

[rheusdens]

Forgot to mention this is all so that Caller ID Name and number works over the link both ways. No NDS on the M1 side for ni2 meant we needed to buy the green feature on the avaya to make the systems talk. I had them running fine with CBCT routing on the m1 but now that we are using this sl1 ni1 protocol, nothing works.

 

[phonesrus]

I don't know if this will help, but in the past on G3 v-4 and later when we had PRI connectivity issues to a Nortel we changed the Avaya PRI trunk to a TIE DCS T/G and assigned it a node number, basically treating the Nortel as a node. There is a change in the messaging on the "D" channel, when you do this, that affects the "B" channels.
I don't know if this will work on the 8700's, but it might be worth a try. I have done the same to Cisco Call Manglers.
If you are going to be moving stations over to the Avaya and talking to the Nortel you will also need UDP to define which extensions are where.

 

[rheusdens]

We are not seeing these options in the 8700 is the tie one thing to change, the dcs t/g another?

 

[phonesrus]

display trunk-group 23 Page 1 of 9 SPE B
TRUNK GROUP

Group Number: 23 Group Type: isdn-pri CDR Reports: y
Group Name: FINANCE COR: 63 TN: 1 TAC: 73
Direction: two-way Outgoing Display? n
Dial Access? n Busy Threshold: 99 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 TCM,Lookahead: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: a Overlap Receiving? n

Trunk Hunt: ascend
Connected to Toll? n STT Loss: normal DTT to DCO Loss: normal
Calling Number - Delete: Insert: Numbering Format:
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0



Page 2 of 9 SPE B
TRUNK FEATURES
ACA Assignment? n Measured: none Wideband Support? n
Internal Alert? n Maintenance Tests? y
Data Restriction? n NCA-TSC Signaling Group: 5
Send Name: y Send Calling Number: y
Used for DCS? y PBX ID: 3 Send Connected Number: y
Suppress # Outpulsing? n Numbering Format: public DCS Signaling: d-chan
Service/ Called Called Del Insert Per Call Night
Feature Len Number CPN/BN Serv

display ds1 1d16 Page 1 of 2 SPE B
DS1 CIRCUIT PACK

Location: 01D16 Name: DCS to FINANCE
Bit Rate: 1.544 Line Coding: b8zs
Line Compensation: 1 Framing Mode: esf
Signaling Mode: isdn-pri
Connect: pbx Interface: user
Country Protocol: 1
Protocol Version: b
Interface Companding: mulaw CRC? n
Idle Code: 11111111
DCP/Analog Bearer Capability: 3.1kHz

MAINTENANCE PARAMETERS

Slip Detection? y Near-end CSU Type: integrated




Above is an example of a PRI TIE DCS Trunk Group/DS1 board setup for NI2.