Create a Revolution SIP Registration

1. Go to Configuration > Phone Systems > SIP
2. Select Settings. See Customizing SIP Settings for a detailed description of the fields.

   • STUN Server – The STUN server allows clients to find out their public address, the type of NAT (Network Address Translators) they are behind, and the Internet side port associated by the NAT with a particular local port. This information is used to set up UDP communication between the client (Revolution) and the VoIP provider BroadSoft, etc.) to establish a call.

     The type of firewall you have set up determines whether you need to configure STUN server. Consult with your network administrator.

     Note: Revolution only supports the standard port (3478) for STUN server.

   • Outbound Proxy Servers – Consult your PBX vendor documentation to determine if an Outbound Proxy Server is required in order for Revolution to register with your PBX system. This field allows multiple entries of the form: sip:<FQDN| IP>

   • Inbound Digest Realm, Inbound Username, and Inbound Password – Only alter these fields if you are working with Avaya, Cisco, or Mitel PBX systems.

   • Disable Reinvites – Enable of you are using a cloud PBX or system that does not support reinvites.

Revolution needs to know how to communicate with your PBX system. For some PBX systems, this is done on the PBX side, for others, it's done in Revolution.

Tip: For those who need to configure communication in Revolution, you'll need information from your PBX system to configure settings in Revolution. Ask your network administrator for assistance.

For multi-site organizations SIP Registrations do not get assigned to a site; they're always available to All.

3CX customers If you are not using authentication for your SIP trunk, skip this section. You do not need to add a SIP Registration because your SIP trunk is already pointing to the Revolution server.

1. Go to Configuration > Phone Systems > SIP
2. Select New > New SIP Registration.
3. Enter a descriptive Name that identifies your VoIP PBX system.
4. (Redundancy Only) For Priority Group, select one of your Priority Groups to define how SIP notifications behave in an active/active redundancy environment. Also see Redundancy.

5. For Registrar URI, enter sip: followed by the Registrar URI provided to you by your VoIP PBX vendor. Example: sip:as.iop1.broadworks.net.

   • Using a different port – sip:as.iop1.broadworks.net:5000 where the endpoint uses a SIP port that isn't the default 5060. The port is specified at the end.
   • TCP instead of default UDP is required – sip:as.iop1.broadworks.net;transport=TCP when your environment requires TCP as the transport type instead of the default UDP.

   Note: (You cannot combine setting a different port and transport type – sip:as.iop1.broadworks.net:5000;transport=TCP is not acceptable.)

6. Enter the Address of Record from your VoIP PBX system. Entering an alias is acceptable. Example: 7582@as.iop1.broadworks.net where 7582 is an alias of 2404987582.
7. Set the Registrar Interval according to the guidelines defined in your VoIP PBX system documentation. Example: BroadWorks requires using 1200 seconds or higher as the interval.
8. Enter the Username and Password from your VoIP PBX. Entering an alias is acceptable. Example: 7582 is an alias for my BroadWorks UI username.
9. Enter the Realm from your VoIP PBX. This is often the same as the Registrar URI without 'sip:' added. Example: as.iop1.broadworks.net.
10. Click Save.

VoIP PBX Examples:

• Broadworks:  (select to expand)
  
• CallSprout: (select to expand)
• 3CX:  (select to expand)

Enter the PBX extension numbers you defined for use as SIP lines in Revolution. See Creating a New SIP Line