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!

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

AVAYA IP OFFICE INTERCONNECT TO NEC SL2100 using SIP

Status
Not open for further replies.

rexytek

Technical User
May 28, 2023
5
0
0
PH
Hi,

I am a new to interconnecting Avaya and NEC pabx.

Do you have any guides on how to interconnect AVAYA IP Office to an NEC PABX vice versa using SIP Trunk?

Thank you in advance.
 
Have you searched this forum as there are threads about other models which may help.
 
The programming is basically the same as the SV8100/SV9100 systems - so do some searching as it's probably been covered in previous threads.

It's really easy to do if you're familiar with both systems. Setup the trunks with IP authentication and use F-Routes (NEC side) and shortcodes (IP Office side) to enable direct extension calling between the systems.

I have SIP trunks between my IP Office and NEC SV9100 systems and it works just fine.
 
Hi, Shaun E

I have already programmed for the AVAYA (IP Office side), calls are going through already. However, calls from NEC to IP Office does not go through. I only get a busy tone from NEC side. I have programmed already SIP on the NEC Side.

Here is the list of programming for the SIP on NEC based on this link



10-12-09 Set the IP Address for your IPLA/B (System IP)

84-26 Set the IP Address for your DSP Resources

10-68-01 Enable IP Trunk Availability (Set to SIP)

10-68-02 Enter the number of IP Trunks (Set to First available Trunk #)

10-68-03 Enter the number of IP Trunks (Set for Available Licenses)

10-23-01 Enable System Interconnect

10-23-02 Assign the IP address of the Remote System

10-23-04 Dial Number (Enter the leading digit of extension numbers on remote site)

10-36 SIP Trunk Registration -Set a User ID (Can be anything, won't work without)

11-01 Define the F/Routes (Extension Numbers of the Remote Site)

14-05 Place IP Trunks into own Trunk Group.

15-07 Assign CAP Keys to all Extensions

22-02 Set all IP Trunks to "TIE LINES"

44-02-01 Assign Dialed Digits (F/Routes)

44-02-02 Set Service Type to F/Route

44-02-03 Additional Data (Reference a F/Route table from 44-05)

44-05 Assign Trunk Group and MAX digits

14-01-24 Caller ID Pass Through for SIP Trunks (Make sure it is checked per SIP Trunk)
 
Have you got an incoming route on the IP Office side?

Does the trunk show as connected in system status?

APSS/ACIS/ACSS-SME
not arrogant, just succinct.
 
Hi TomMills,

We have set an incoming route on the IP Office side.

However, it does not show any connection in the system status when I try to call from NEC to IP Office.

Thank you.
 
Do you have a NEC SIP trunk license?
 
Hi jsaad,

Yes we have NEC SIP trunk license

Thank you.
 
You need to run system monitor to see what is coming into the IP Office on the SIP trunk. That may show why the IP Office isn't accepting and routing the calls.

Stuck in a never ending cycle of file copying.
 
nec ntac has a guide how to interconnect sl1100 to another pbx.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top