Follow

Avaya IP Office Manager 7.0+ IP Auth Method

This guide will assist you in setting up SIPTRUNK as a SIP trunk provider on Avaya IP Office Manager version 7. This particular configuration was done on an Avaya IP Office 500v2 with a VCM 32 card. This Avaya System was configured via open internet and was not behind any firewall. The following configuration represents a minimal configuration to provide inbound and outbound calling with a single DID and channel at SIPTRUNK. It includes utilization of multiple gateways for failover capabilities as a best practice.

 

IMPORTANT: Refer to Interconnecting with SIPTRUNK for the full list of gateways along with whitelisting recommendations. 

 

1. Log in and load your configuration in Avaya IP Office Manager.

 

2. Go to "System" and then select your IP Office System. 

 

3. Select the "LAN 1" tab.

 

4. Select the "VoIP" tab and ensure that "SIP Trunks Enable" is checked.

 

 

5. Select the "Network Topology" tab and fill in the settings to match your topology.

 

NOTE: This device was not behind NAT, but you may use the SIPTRUNK STUN server (stun.siptrunk.com) if necessary. The "Binding Refresh Time" is a setting that controls the frequency of SIP options messages. We chose 60 seconds as it provided a good result in testing.

 

STUN-server-siptrunk-IP-address-edit.png

 

6. Go to "Lines" and then right-click and select "New" > "SIP Line". 

 

7. Under "ITSP Domain Name", input the external IP address you will use for the Avaya system. All other settings can be left as default or adjusted as necessary.

 

8. Under the "Transport" tab, input the IP address for gw1.siptrunk.com (63.247.69.226) in the "ITSP Proxy Address" field.

 

9. Ensure that you have input valid DNS settings, network configuration information, and that "Calls Route via Registrar" is checked.

 

 

10. Select the "SIP URI" tab and add an entry. The applicable settings from below are the "Incoming" and "Outgoing" groups. These need to match the line number that you just created. All other settings were left at the default.

 

 

11. Select the "VoIP" tab, and then click "Advanced". 

 

12. Ensure that only G.711 U-LAW and G.729 are selected.

 

13. Check the box for "Re-invite Supported" and ensure that RFC 2833 is selected for DTMF mode.

 

 

14. Create a second "SIP Line" and duplicate all settings except for "ITSP Proxy Address" under the "Transport" tab. This is for gw2.siptrunk.com (205.251.137.154) and will provide redundancy for inbound and outbound calling when configuration is complete.

 

15. Repeat these steps for the third and fourth "SIP Line" and duplicate all settings except for "ITSP Proxy Address" under the "Transport" tab. Add gw4.siptrunk.com (104.219.162.45) and gw5.siptrunk.com (104.219.163.120).

 

 

16. Navigate to the "User" tree and select "No User". 

 

17. Select the "Source Numbers" tab and add "SIP_OPTIONS_PERIOD=1" as an entry. This is an additional time-based control on the frequency of SIP Options messages.

 

 

18. Select the User who will be dialing and receiving calls on the SIP Line and go to the "SIP" tab. Enter the DID that will be transmitted as their caller ID under "SIP Name" and "Contact."

 

NOTE: SIPTRUNK requires 11 digits in the To header for outbound calls. If your requirement is to only dial 10 digits within the United States, create the ARS rule that follows:

  • Code: XXXXXXXXXXN
  • Telephone Number: 1N
  • Feature: Matching
  • Line Group ID: Matching

 

NOTE: Refer to these articles on Setting Up Caller ID and Setting Up Outbound Calling for more information on configuring each with SIPTRUNK.

 

 

19. Navigate to the "Short Codes" tree and create a new short code. This code will be used to direct calls to the SIP Line we created.

 

20. Ensure that your "Telephone Number" field follows the N@"gw1.siptrunk.com" format where N=Any Number, or you may specify a specifically dialed number if you wish. 

 

21. We chose to use an ARS entry in the "Line Group" field which will be discussed in upcoming steps as it allows us to provide fail-over capabilities in case gw1.siptrunk.com is unavailable. You could simply skip the ARS steps and use the Line Group you previously created.

 

 

22. Navigate to the "Incoming Route" tree and create a new route.

 

23. Under the "Standard" tab, ensure that the "Line Group" matches what you created previously and that you list the DID that will be delivered with a "+" symbol in front. 

 

 

24. Under the "Destinations" tab, ensure that you have set an appropriate destination for your inbound route to deliver the call to.

 

 

THE FOLLOWING STEPS ARE OPTIONAL BUT RECOMMENDED

 

25. Navigate to the "ARS" tree and create a new entry.

 

26. Give the route a distinctive name and mark it as "In-Service". Add a code for calls to be routed through. The code pictured below transmits any number dialed through the Line Group that was previously created.

 

27. Note that the out of service route is directed to a second ARS group that was created using the same process outlined here, except it uses the secondary Line Group previously created. The second ARS group is also used as a lower priority "Alternate" route in this ARS group routing.

 

 

28. Log in to your SIPTRUNK portal and select "Modify Trunk" on the trunk you will be connecting to from your Avaya unit.

 

29. Set the trunk to "IP Authentication" and input the address and port you will be using to connect to SIP.US with from your Avaya unit. 

 

NOTE: Refer to this article for more information on How to Set Up IP Authentication in the SIPTRUNK portal. 

 

30. Save the Avaya configuration and load it into the system.

 

31. Once the system reboots, you should be able to make and receive calls through SIPTRUNK.

 

If you experience problems after following this guide, please refer to our Troubleshooting Guides. If you are still unable to resolve the issue, please open a ticket to contact the Support team at support@siptrunk.com

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk