NEC: SIP Trunking Configuration Guide V.1

Size: px

Start display at page:

Download "NEC: SIP Trunking Configuration Guide V.1"

Logan Lyons
5 years ago
Views:

1 NEC: SIP Trunking Configuration Guide V.1 FOR MORE INFO VISIT: CALL US US intermedia.net

2 2 NEC: SIP Trunking Configuration Guide V.1 TABLE OF CONTENTS Introduction... 3 Sphericall Setup and Limitations as Tested... 3 Coded Re-Invite Limitation... 3 SIP End Devices... 3 Faxing... 3 Software Level... 3 Prerequisite for Configuring NEC Univerge Sphericall System with Intermedia SIP Trunks... 4 Intermedia Configuration Information... 4 Firewall/Router Setup NAT and SIP Port Forwarding... 5 Support... 6 PBX Configuration and Setup... 6 SIP Trunk CREATION... 6 Configure Service Provider:... 6 Configure the SIP Creditial... 7 Codec Configuration... 8 Configuring 911 calls:... 8

3 3 NEC: SIP Trunking Configuration Guide V.1 INTRODUCTION These Notes describe the procedures for configuring Session Initiation Protocol (SIP) Trunking between service provider Intermedia and a NEC 3C Sphericall System. The Intermedia SIP Trunking service referenced within these Notes is designed for business customers. The service enables local and long distance PSTN calling via standards-based SIP trunks directly as an alternative to legacy analog or digital trunks, without the need for additional TDM enterprise gateways and the associated maintenance costs. SPHERICALL SETUP AND LIMITATIONS AS TESTED Coded Re-Invite Limitation The current NEC 3C Sphericall firmware release doesn t support re-invite, preventing mid call codec change. This means that calls to and from to applications that support re-invite have a potential to fail. This is generally not the case with the OFF NET PSTN call but can be problematic with ON NET calls (i.e. calls that stay on the Intermedia network) to Intermedia s IVR or other endpoints. Re-invite failure will cause call failure or one-way audio. SIP End Devices NEC 3C Sphericall setup supports two types of SIP phones: NEC SIP phone Polycom SIP Phones Both types of SIP phones should be configured with: G729 primary G711 Secondary RFC 2833 DTMF G729 annexb disabled (no silence packets) Faxing NEC 3C Sphericall supports an external SIP ATA for the fax line. This ATA should be configured with only G711. The PBX should be configured with G729 primary and G711 secondary. Software Level NEC 3C Sphericalll firmware version: User-Agent: Sphericalll/8.0.1 Build/120

4 4 NEC: SIP Trunking Configuration Guide V.1 PREREQUISITE FOR CONFIGURING NEC 3C SPHERICALL SYSTEM WITH INTERMEDIA SIP TRUNKS Intermedia Configuration Information You should have the configuration information from Intermedia before you start the install. This information will provide settings for the SIP connection(s). To set up your SIP trunking account, contact Intermedia at: Once your account is set up they will provide you with the following service information: Table 1: Intermedia Account Information Option (NEC) Option (Intermedia) Description Outbound Proxy SBC IP Address (ex ) The Outbound Proxy is the SIP registration domain for your Intermedia SIP trunks. When your SIP trunks initially register they use this domain. Service Provider Domain Auth Username SBC DNS Name (ex. usbc.accessline.com) SIP Trunk ID (ex. dgw ) The domain for your Intermedia SIP trunks. When your SIP trunks initially register they use this domain. This is the username that Intermedia uses to authenticate your registration. Auth Password Trunk Number(s) Password (ex. Akkbid24) New number (ex ) The Auth Password is the password required with your Auth Username. These are the telephone numbers that users will dial to reach you over your Intermedia SIP trunks. The information you will receive from Intermedia will be sent via and composed of the following information. Your order will be different from this information:

5 5 NEC: SIP Trunking Configuration Guide V.1 SIP Trunk ID: dgw Password: Akkbid24 SBC DNS Name: usbc.accessline.com SBC IP Address: SBC Port: 5060 Call processing has been setup to allow up to X simultaneous calls. The following new numbers and routing have been provisioned in our systems to route via the SIP trunks to the PBX. Please ensure they are programmed in the customer's phone equipment to route appropriately and advise the customer of these new numbers: The following 911 callback number has been configured in our network as the default for this location: Make sure it routes appropriately at the customer's site. FIREWALL/ROUTER SETUP SIP-based VOIP enabled PBX or SIP phones connected to Intermedia s Service via our SIP trunking service MUST be installed in a secure trusted zone behind a Firewall and not exposed to the public internet. This means the PBX or SIP phones should never be put into a router's DMZ (allows untrusted access). The firewall must block all inbound internet (untrusted) traffic to the PBX or SIP phones. The firewall can be configured to allow inbound traffic from trusted devices from remote (satellite) locations. You do not have to block outbound traffic from your private network to the internet, but Network- Address-Translation, or NAT must be enabled. NAT allows the Intermedia Service to send calls to the PBX or SIP Phones. If the firewall has multiple NAT settings, you must select the NAT setting that Address Restricted and not Endpoint Independent. If you do want to limit outbound internet traffic on the firewall, then you need to open SIP related ports on the firewall to allow Intermedia s Service to function properly. Protocol Port(s) UDP 6060 TCP 6061 UDP NAT and SIP In the router to which the NEC 3C Sphericall is connected, enable NAT and disable all special SIP management features (such as SIP ALG). 3.2 Port Forwarding Forward UDP ports 6060 and 1024 through 1215 to the DSX system s IP address.

6 NEC: SIP Trunking Configuration Guide V.1 SUPPORT For technical support on the NEC 3C Sphericall products described in these Application Notes visit http://www.necam.com/support/.

6 6 NEC: SIP Trunking Configuration Guide V.1 SUPPORT For technical support on the NEC 3C Sphericall products described in these Application Notes visit PBX CONFIGURATION AND SETUP SIP Trunk CREATION: Create a new SoftTrunk under Trunks tab Configure Service Provider: When the Configure Service Provider window pops up, fills in the following information: Service Provider Domain is the SBC DNS Name provided by Intermedia Outbound Proxy is the SBC IP Address provided by Intermedia Port should be configured for 6060 Primary MGC is the name of your 3C Primary Server Secondary MGC is the name of your 3C Secondary Server Contact Domain is the domain name of your Data Service Provider

to Hub property, and fill in the information provided by Intermedia:

7 7 NEC: SIP Trunking Configuration Guide V.1 Configure the SIP Creditial Once the trunk successfully created, go to Hub property, and fill in the information provided by Intermedia: Account is the SIP Trunk ID provided by Intermedia Password is the Password provided by Intermedia

8 8 NEC: SIP Trunking Configuration Guide V.1 Codec Configuration For CODEC configuration, go to System Property in the Main Window, and go to MediaStreams tab to configure the following: G729 primary G711 Secondary RFC 2833 DTMF G729 annexb disabled (no silence packets)

9 9 NEC: SIP Trunking Configuration Guide V.1 Configuring 911 calls: Intermedia provides a 911 Call Back Number, which has been configured in our systems with the street address used for Emergency responders to identify the location where the PBX is physically located. All calls to 911 must have the main 911 Call Back Number provisioned; if not the Intermedia system will default to the Emergency 911 Call Back number. Emergency call back from the 911 operator will be made to the Emergency Call Back number provided by Intermedia. The PBX must be configured to route this number to all phones, to the receptionist or a hunt group to make sure a call back from 911 can be received.

Syntellect IVR SIP Trunking Configuration Guide Using AccessLine SIP Trunking

And Syntellect IVR SIP Trunking Configuration Guide Using AccessLine SIP Trunking Interfacing AccessLine SIP Registrar and Syntellect SCP v8 IVR Platform By Jeff Thorness Introduction These Notes describe