ScopTEL TM IP PBX Software. PSTN Interfaces and Gateways

Similar documents
ScopTEL TM IP PBX Software. Basic Installation Hierarchy for Telephony Server

Basic Installation Hierarchy for Telephony Server

WAN. System Networking Lab Table 1

Avaya PBX SIP TRUNKING Setup & User Guide

RP-FSO522 2-Line FXO, 2-Line FXS SIP IP Gateway. Feature

TT11 VoIP Router 1FXS/1FXO TA User Guide

Application Notes for Configuring Cablevision Optimum Voice SIP Trunking with Avaya IP Office - Issue 1.1

ScopTEL TM IP PBX Software. Managing Incoming Lines

Application Notes for Configuring SIP Trunking between CenturyLink SIP Trunk (Legacy Qwest) Service and Avaya IP Office R8.0 (16) Issue 1.

Application Notes for Configuring Windstream SIP Trunking with Avaya IP Office - Issue 1.0

EarthLink Business SIP Trunking. Allworx 6x IP PBX SIP Proxy Customer Configuration Guide

Abstract. Avaya Solution & Interoperability Test Lab

ANSEL FXS / 1 PSTN. VoIP Telephone Adaptor. User Manual V1.10

Configure Gateways. Gateway Overview. Gateway Overview, page 1 Gateway Setup Prerequisites, page 3 Gateway Configuration Task Flow, page 4

Overview of the Session Initiation Protocol

ISDN Troubleshooting. All Mediatrix Units with ISDN cards. v

EarthLink Business SIP Trunking. Toshiba IPEdge 1.6 Customer Configuration Guide

Application Notes for Configuring CenturyLink SIP Trunking with Avaya IP Office Issue 1.0

Configuration Guide IP-to-IP Application

Setting up Alcatel 4400 Digital PIMG Integration

EarthLink Business SIP Trunking. ShoreTel 14.2 IP PBX Customer Configuration Guide

Application Notes for TelStrat Engage Record Version 3.3 with Avaya Business Communication Manger Release 6.0 VoIP Recording Issue 1.

Application Notes for Configuring Tidal Communications tnet Business VoIP with Avaya IP Office using SIP Registration - Issue 1.0

Setting Up a Mitel SX-2000 Digital PIMG Integration with Cisco Unity Connection

Setting Up an Alcatel 4400 Digital PIMG Integration with Cisco Unity Connection

TELECOMMUNICATION SYSTEMS

Application Notes for Configuring SIP Trunking between the Skype SIP Service and an Avaya IP Office Telephony Solution Issue 1.0

UCM6102/6104/6108/6116 Configuration

Public Switched TelephoneNetwork (PSTN) By Iqtidar Ali

Spectrum Enterprise SIP Trunking Service Vertical TM Wave IP500TM / Wave IP2500 TM Release 4.0, 4.5 IP PBX Configuration Guide

Application Notes for Configuring EarthLink SIP Trunk Service with Avaya IP Office using UDP/RTP - Issue 1.0

Application Notes for OneAccess-Telstra Business SIP with Avaya IP Office Release 11 SIP Trunking - Issue 1.0

ISDN Troubleshooting. All Mediatrix Units with ISDN cards

ISDN Troubleshooting. All Mediatrix Units with ISDN cards. v

EarthLink Business SIP Trunking. Asterisk 1.8 IP PBX Customer Configuration Guide

Application Notes for Configuring SIP Trunking between McLeodUSA SIP Trunking Solution and an Avaya IP Office Telephony Solution Issue 1.

EP502/EP504 IP PBX 1.1 Overview


VoIP Basics. 2005, NETSETRA Corporation Ltd. All rights reserved.

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Avaya IP Office Release 8.0 with AT&T Business in a Box (BIB) over IP Flexible Reach Service Issue 1.0

Application Notes for Configuring the ADTRAN NetVanta UC Server with Avaya IP Office 6.1 Issue 1.0

Application Notes for Phonect SIP Trunk Service and Avaya IP Office 7.0 Issue 1.0

NEC: SIP Trunking Configuration Guide V.1

SPA400 Internet Telephony Gateway with 4 FXO Ports

Setting Up a Serial (SMDI, MCI, or MD-110) PIMG Integration with Cisco Unity Connection

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring Windstream using Genband G9 SIP Trunking with Avaya IP Office Issue 1.0

Innovation Networking App Note

Spectrum Enterprise SIP Trunking Service NEC Univerge SV8100 IP PBX Configuration Guide

Application Notes for Configuring SIP Trunking between TelePacific SmartVoice SIP Connect and an Avaya IP Office Telephony Solution 1.

Abstract. Avaya Solution & Interoperability Test Lab

Chapter TIMG BOILERPLATE

SIP TRUNKING CARRIER CERTIFICATION OXE-SIP configuration

Ingate Firewall & SIParator Product Training. SIP Trunking Focused

FTA-102L. Free Roaming Gateway. User Manual

Application Notes for Packet One SIP Trunk System Version 3.1 Interoperability with Avaya Software Communication System Release Issue 1.

Introduction. H.323 Basics CHAPTER

Application Notes for Configuring SIP Trunking between Global Crossing SIP Trunking Service and an Avaya IP Office Telephony Solution Issue 1.

MITEL SIP CoE Technical. Configuration Note. Configure Mitel MiVoice Office 6.1 SP1 PR2 for use with IntelePeer SIP Trunking. SIP CoE XXX

EarthLink Business SIP Trunking. Cisco CME IP PBX Customer Configuration Guide

4 Port IP-PBX + SIP Gateway System

Abstract. Avaya Solution & Interoperability Test Lab

8-Port SIP VoIP Gateway (8 FXS)

Application Notes for Configuring SIP Trunking between the Comdasys Mobile Convergence Solution and an Avaya IP Office Telephony Solution Issue 1.

Application Notes for Configuring SIP Trunking between Bandwidth.com SIP Trunking Solution and an Avaya IP Office Telephony Solution Issue 1.

Abstract. Avaya Solution & Interoperability Test Lab

SV9100 SIP Trunking Service Configuration Guide for Cable ONE Business

PANASONIC. Optimum Business Trunking and the Panasonic KX-NCP500 IP PBX V Configuration Guide

ShoreTel & Windstream for SIP Trunking (Native)

Application Notes for Configuring Fonolo In-Call Rescue with Avaya IP Office Server Edition using SIP Trunks Issue 1.0

Switchvox/Digium Hardware Interface Lab

White Paper. SIP Trunking: Deployment Considerations at the Network Edge

Application Note Configuration Guide for ShoreTel and Ingate

Configuration Guide For Use with AT&T s IP Flexible Reach Service. Version 1/Issue 7. July 30, 2008

OneXS will provide users with a reference server (IP, FQDN, or other means to connect to the service). This must be obtained before setup can begin.

SIP Trunking using Optimum Business SIP Trunk Adaptor and the Nortel BCM50 IP-PBX (Release 5.0)- V

Spectrum Enterprise SIP Trunking Service NEC Univerge SV9100 IP PBX Configuration Guide

XO SIP Service Customer Configuration Guide for Avaya IP Office Version 6.0 with XO SIP

Application Note 3Com VCX Connect with SIP Trunking - Configuration Guide

Application Notes for Configuring Computer Instruments e-ivr, as a SIP endpoint, with Avaya IP Office 500 V2 Issue 1.0

Overview of SIP. Information About SIP. SIP Capabilities. This chapter provides an overview of the Session Initiation Protocol (SIP).

Application Notes for Presence OpenGate with Avaya IP Office 9.0 Issue 1.0

Application Note Asterisk BE with SIP Trunking - Configuration Guide

FRAFOS ABC-SBC Generic SIP Trunk Integration Guide for ShoreTel 14.2

Release Note for N412

Abstract. Avaya Solution & Interoperability Test Lab

Application Notes for Configuring SIP Trunking Using Verizon Business IP Contact Center VoIP Inbound and Avaya IP Office Release 6.1 Issue 1.

Yeastar TA Series Analog VoIP Gateways

1 SIP Carriers. 1.1 LightBound Warnings Vendor Contact Vendor Web Site:

Patton Electronics Co Rickenbacker Drive, Gaithersburg, MD 20879, USA tel: fax:

Microsoft Skype for Business. Installation Guide for Patton SmartNode esbc & VoIP Gateway

SAPEX. The All in One Embedded IP PBX Server

Application Notes for Configuring SIP Trunking Using Verizon Business IP Contact Center VoIP Inbound and Avaya IP Office Release 8.1 Issue 1.

Interworking Signaling Enhancements for H.323 and SIP VoIP

Avaya Solution & Interoperability Test Lab. Abstract

Implementation and Planning Guide

Setting Up an Avaya Definity ProLogix Digital PIMG Integration with Cisco Unity Connection

Grandstream Networks, Inc. UCM6xxx SIP Trunks Guide

SIP Trunking using Optimum Business SIP Trunk Adaptor and the Cisco Call Manager Express Version 8.5

Transcription:

ScopTEL TM IP PBX Software PSTN Interfaces and Gateways

Gateways A VoIP gateway is as a bridge between: Interfaces: (T1/E1, FXO, FXS) Protocols: SIP, Cisco SCCP/Skinny, MGCP (legacy protocol), and H.323 (legacy protocol) CODECS (media): GSM (13 Kbps), ilbc (15 Kbps), G.711 (64 Kbps), G.722 (48/56/64 Kbps), G726 (16/24/32/40 Kbps), G.728 (16 Kbps) and G.729 (8 Kbps)

What are FXS and FXO? FXS (Foreign Exchange Station) FXS is an interface which drives a telephone. FXS interfaces get phones plugged into them, deliver battery, and provide ringing. The FXS interface initiates and sends a ringing voltage to the FXO interface. FXO (Foreign Exchange Office) FXO is an interface that connect to a phone line. They supply your PBX with access to the public telephone network. FXS interfaces are what allow you to hook telephones to your PBX, and FXO interfaces allow you to connect your PBX to real analog phone lines. FXO interfaces receives the ringing voltage from the FXS interface. The phone receiving the call is the last FXO device in the chain, and when it receives voltage from an FXS device, the phone will ring. Setup To receive voltage from outside lines, connect the outside line to an FXO port on your server or gateway. Then connect the phones to FXS ports on your server or gateway. When the FXO port receives the voltage, it will then generate voltage using the FXS port and send it to your analog phone.

FXO interfaces Also known as POTS line (Plain Old Telephone Service) Also known as 1fl (1 family line) Each FXO line can support one conversation between two parties (Tx and Rx Transmit and Receive) Most business use equivalent lines placed into an equivalent group ordered from the phone company AKA Telco. Sometimes these equivalent groups are referred to as: Rotary group Hunt group The first line or pilot in the equivalent group is usually referred to as the BTN (Billing Telephone Number) Usually an inbound Caller ID service is ordered separately for each 1fl at an additional cost If additional lines are added to the pilot in a group then they are programmed by the Telco in a forward on busy configuration. Example: 555-1234 (BTN) forward busy to 555-2234 forward busy to 555-3234 forward busy to 555-4234 Busy (since this is the last number in this 4 FXO equivalency group) Usually an inbound Caller ID service is ordered separately for each 1fl at an additional cost Variants of FXO interfaces include: Loop Start (ScopTEL) Kewl Start (ScopTEL s preferred FXO interface when using DAHDI hardware) Ground Start (Legacy PBX s)

FXO interfaces Disconnect Supervision Disconnect supervision is a term in telephony describing signaling between the telephone exchange and a connected party used to indicate that the connected call is being disconnected. Without this Telco option FXO ports can get hung indefinitely on the PBX. It only applies to Loop Start and Kewl Start circuits (not Ground Start). CPC (Calling Party Control) Is a signal sent from most modern electronic COs to indicate that the "Calling Party" has hung up. North American Central Office Switches use the OSI (Open Switch Interval) to signal the PBX s FXO port that the Calling Party has hung up. The OSI is a break in loop voltage (0VDC), typically for 800ms. If the PBX s FXO port can support the Open Switch Interval it will free up the FXO port. Supervisory Disconnect Tone Some Telco s send a Supervisory Disconnect Tone when the Calling Party hangs up. If the PBX s FXO port can support the Supervisory Disconnect Tone it will free up the FXO port. Battery Reversal Instead of an open loop for 800ms, the DC talk battery gets reversed for 500ms. Battery Reversal is still used in some countries however no FCC registered telephone equipment would recognize a battery reversal, since the FCC requires that telephones operate correctly on either polarity. Therefore Battery Reversal would simply be ignored. Basic Test If you have a Butt-set with a polarity light that's on all of the time while you're talking or you can hold the polarity test button while listening, you can watch the polarity LED. Make a call to your cell phone, hang-up the cell phone, and watch the polarity LED on your Butt-set. When there's an open loop, there's no voltage, and there's no electricity to light the LED. You can also listen for the Supervisory Disconnect Tone on your Butt-set when the Calling Party hangs up.

ISDN Interfaces ISDN interfaces are digital TDM (Time Division Multiplexing) trunks that support multiple voice channels (also known as Bearer channels) over a single circuit. There are two common types of ISDN interfaces; BRI and PRI. Bearer Channel (Media) The bearer capability for BRI and PRI is voice/speech at 3.1 khz audio voice channel of 8 bits sampled at 8 khz with G.711 encoding, and data at unrestricted 64 kbps, restricted 64 kbps, 56 kbps. Each one of these channels is known as a DS0 Data Channel (Signaling) The signaling channel (D) uses Q.931 for signaling with the other side of the link. Q.931 Q.931 is used to transmit and receive call signaling messages according to the H.225 protocol for digital telephone services. The messages in Q.931 include setup (a signal indicating the establishment of a connection), call-proceeding (a signal indicating that the call is being processed by the destination terminal), ring-alert (a signal that tells the calling party that the destination set is ringing), connect (a signal sent back to the source indicating that the intended destination phone set has received the call), and release/complete (a signal sent by either the source or the destination indicating that the call is to be terminated).

Basic Rate Interface The entry level interface to ISDN is the Basic(s) Rate Interface (BRI), a 128 kbps service delivered over a pair of standard telephone copper wires. The 144 kbps payload rate is broken down into two 64 kbps Bearer channels ('B' channels) and one 16 kbps signaling channel ('D' channel or delta channel). This is sometimes referred to as 2B+D. The interface specifies the following network interfaces: The U interface is a two-wire interface between the exchange and a network terminating unit, which is usually the demarcation point in non-north American networks. The T interface is a serial interface between a computing device and a terminal adapter, which is the digital equivalent of a modem. The S interface is a four-wire bus that ISDN consumer devices plug into; the S & T reference points are commonly implemented as a single interface labeled 'S/T' on an Network termination 1 (NT1). The R interface defines the point between a non-isdn device and a terminal adapter (TA) which provides translation to and from such a device. BRI-ISDN is very popular in Europe but is much less common in North America. It is also common in Japan - where it is known as INS64. ScopTEL supports many SIP to BRI gateways (Mediatrix, Patton, Audiocodes, Quintum, Vegastream) ScopTEL only supports Woomera and Wanpipe (Sangoma ) BRI PSTN interfaces (using the Card Detection Wizard).

Primary Rate Interface The other ISDN access available is the Primary Rate Interface (PRI), which is carried over an E1 (2048 kbps) in most parts of the world. An E1 is 30 'B' channels of 64 kbps, one 'D' channel of 64 kbps and a timing and alarm channel of 64 kbps. In North America PRI service is delivered on one or more T1 carriers (often referred to as 23B+D) of 1544 kbps (24 channels). A PRI has 23 'B' channels and 1 'D' channel for signaling (Japan uses a circuit called a J1, which is similar to a T1). Inter-changeably but incorrectly, a PRI is referred to as T1 because it uses the T1 carrier format. A true T1 (commonly called "Analog T1" to avoid confusion) uses 24 channels of 64 kbps of in-band signaling. Each channel reserves 56 kb for data or voice and 8 kbps for signaling and messaging. Analog T1 circuits do not support CLID. PRI uses out of band signaling which provides the 23 B channels with clear 64 kb for voice and data and one 64 kb 'D' channel for signaling and messaging. PRI Circuits supply CLID before the user s phone starts ringing. In North America, NFAS (Non-Facility Associated Signaling) allows two or more PRIs to be controlled by a single D channel, and is sometimes called "23B+D + n*24b". D-channel backup allows for a second D channel in case the primary fails. On a single span Channel 24 is normally reserved for the D Channel on North American T1 PRI circuits. On a single span Channel 16 is normally reserved for the D Channel on E1 PRI Circuits. PRI Circuits use DNIS to route calls to the CPE (Customer Provided Equipment) and most PRI circuits have many DNIS numbers associated with the circuit number (usually sold in blocks of 10 or 30).

DNIS (Dialed Number Information Service) DNIS is the routing number the PRI CPE (Customer Provided Equipment) circuit receives from the carrier (also known as Received Digits) The received digits length (also known as Digits to Out Pulse by some Telco s) can vary in length typically from 3 to 10 digits in length. DNIS digits, as received from the carrier, are used to route calls via Incoming Lines objects in the ScopTEL IP PBX Example 1 The customer s BTN is 555-555-1234 The Received Digit length set by the Telco is 4 The resulting DNIS or received digits is equal to 1234 Toll Free Services The customer has a published toll free number 1-800-555-2234 Toll free numbers must be associated with a local phone number which is referred to as the conversion number The conversion number can be any DNIS number associated with the PRI circuit In this example the conversion number for 1-800-555-2234 is the BTN number 555-555-1234 Therefore the DNIS number for 1-800-555-2234 is 1234

ISDN Interfaces - Clocking Systems with digital interfaces need to synchronize to the network in order to function. Synchronization is performed in a hierarchical way, where each device/switch obtains the network clock from the device/or switch above it in the synchronization hierarchy and passes the network clock to the device/switch below it in the synchronization hierarchy. The synchronization levels are referred to as strata. Sangoma and Digium ISDN interfaces both include an internal CSU/DSU. Clock Mode (Wanpipe) Master Clock: The interface does not obtain timing from the network, but transmits the systems timing to equipment connected to it. Always use this mode when setting the interface to PRI (Network side) signaling. Primary reference: The interface obtains the timing reference from the network, to which the system synchronizes (usually the Telco). Secondary reference (Secondary): The interface acts as a standby reference. If there are excessive errors on the primary reference T1 link, or the interface designated as primary reference fails, this interface will obtain the timing reference from the network, which the system synchronizes to. Thirdary: The interface acts as a standby reference. If there are excessive errors on the secondary reference T1 link, or the interface designated as secondary reference fails, this interface will obtain the timing reference from the network, which the system synchronizes to. Quaternary: The interface acts as a standby reference. If there are excessive errors on the thirdary reference T1 link, or the interface designated as thirdary reference fails, this interface will obtain the timing reference from the network, which the system synchronizes to.

SIP Overview SIP (Session Initiation Protocol) is a light weight ASCII protocol which is well suited for voice (VoIP), video (H.264 CODEC), presence (XMPP), and text chat services. It borrows from other technologies like email and DNS For example an email address looks like mailto:user@domain.com A SIP URI looks like sip:user@domain.com. The default SIP UDP/TCP signalling port is 5060 in format it looks like sip:user@domain.com:5060. The default SIP TCP-TLS signalling port is 5061 in format it looks like sip:user@domain.com:5061. The ScopTEL default RTP port range for SIP is 10000-20000. ScopTEL integrates a SIP UA, UAS, B2BUA, Registrar, and SBC. SIP user agent (UA): is a logical network end-point used to create or receive SIP messages and thereby manage a SIP session. A SIP UA can perform the role of a UAC (User Agent Client ), which sends SIP requests to the UAS (User Agent Server). Registrar: A server that authenticates REGISTER requests and places the information it receives in those requests into the location service for the domain it handles.

SIP Overview continued B2BUA: In the originating call leg the B2BUA acts as a user agent server (UAS) and processes the request as a user agent client (UAC) to the destination end, handling the signaling between end points back-to-back. A B2BUA maintains complete state for the calls it handles. Session Border Controller: is a device regularly deployed in Voice over Internet Protocol (VoIP) networks to exert control over the signalling and usually also the media streams involved in setting up, conducting, and tearing down telephone calls or other interactive media communications. It can control multiple elements including: NAT Traversal SIP normalization via SIP message and header manipulation Malicious attacks such as a DoS (Denial-of-Service attack) or distributed DoS Topology hiding Encryption of signaling (via TLS ) and media (SRTP). ScopTel supports SIP end points (phones) and trunks without the need for optional licenses. SIP is native to ScopTEL.

T.38 Fax (UDPTL) Passthrough Due to packet loss, latency, echo cancellation, compressed CODECS, and jitter buffers faxing is not reliable over IP networks. For example a fax is not supported over IP using any compressed CODEC such as G.729. Faxes are not supported if echo cancellation is used. Therefore some drivers or gateways will disable echo cancellation during fax negotiation. UDPTL (T.38) refers to an Internet Facsimile Protocol used for carrying fax data over IP networks. T.38 must be supported endpoint to endpoint. The UDPTL (T.38) tab allows you to specify various parameters, which are as follows: Start Port: Allows you to specify the starting port of the UDPTL (T.38) channel. By default, its value is 4000. End Port: Allows you to specify an appropriate end port of the UDPTL (T.38) channel. By default, its value is 4999. Enable UDP checksums on UDPTL traffic: Allows you to enable UDP checksums on UDPTL traffic for any error

T.38 Fax (UDPTL) Passthrough (continued) Error Correction Type: Allows you to specify the error correction scheme to be used. You can select an appropriate scheme to use, from the two available schemes. By default, its value is t38 UDP FEC. Maximum packet length: Allows you to specify the maximum packet length in the UDPTL (T.38) channel. By default, its value is 400. Number of Error Correction Entries per packet: Allows you to specify the number of error correction entries per packet. By default, its value is 3. Error Correction Span: Allows you to specify an appropriate error correction span. The span over which parity is calculated for FEC in a UDPTL packet.

If any analog FXO/FXS or T1/E1 or BRI cards are installed then you must do a Card Detect to recognize and configure that hardware before the drivers and configurations can be properly loaded. Configuration > Telephony > Interfaces > Detect Cards Follow the pop-up windows to complete the card detection procedure and be certain to read and follow any instructions that will appear in those pop-up windows. After your PSTN hardware is detected and the required services are running it will be necessary to configure regional properties and gain settings for each of your PSTN cards and ports. If a change is made to any settings on the Interfaces tabs it is a good practice to Commit those changes and then restart the following services in the correct order. First navigate to the General tab The correct order to reset services is: - Stop the Telephony Server - Restart the Analog/Digital Modules (Zaptel/Wanpipe) Service - Start the Telephony Server

A typical VoIP Interface would normally use the industry standard SIP technology. Therefore this example will cover the creation of a CPE side (Customer Provided Equipment) SIP account. SIP trunks normally require a SIP Registrar for client authentication and a SIP Proxy to handle signaling and media. It is common for the SIP Registrar and SIP Proxy to be the same server but the SIP Registrar and SIP Proxy can reside on different servers. To create a new SIP Interface navigate to Configuration > Telephony > Configuration > Interfaces > VoIP Accounts and Click Add a New VoIP Account and choose SIP from the drop down list.

The name field is mandatory and it is typical for the name of the SIP trunk to equal the SIP username provided by the SIP ITSP (Internet Telephony Service Provider). A SIP Friend allows both Incoming and Outgoing Calls and is most typical. In this example the name of our SIP trunk is 5555551212. When the General properties are entered click on the Server tab next to add the authentication properties and the address of the SIP Registrar and Proxy.

Authentication Mode is normally Plaintext but the username and password are sent over the Internet using MD5 encryption. Authentication Mode = MD5 requires the MD5 hash entered into the text box and is not normally used. Enter the Username and Password into the corresponding fields in the GUI. Host Mode Specific is chosen when the server is authenticating to a SIP service provider. This is the option chosen to authenticate to an ITSP. This option requires that the ITSP s hostname or IP address is entered in the text field. Host Mode Dynamic is chosen when another SIP user agent is registering inbound to the server. Therefore the hostname and IP address can be left blank. In this example we are authenticating outbound therefore we must choose Host Mode specific. If Registration must be forced then check the box for Register as User Agent. When finished here click on the Network tab.

If the server is situated behind a third party NAT Router/Firewall then check off the box for Trunk Behind NAT. If the server is situated behind a third party NAT Router/Firewall then the third party Firewall rules must port forward the following rules to the LAN IP address of the ScopTEL server. 5060/udp 10000-20000/udp. Also a static public IP address and/or FQDN (Fully Qualified Domain Name) is recommended for the ScopTEL server to help negotiate Firewall related RTP issues. This IP address or FQDN is entered into the text field located at Configuration > Telephony > General > External IP or Hostname and the Server behind NAT?[ ] option be checked [x]. It is common for most SIP ITSP s to require the Insecure options Port, Invite to be checked.the SIP Qualify Time is defined in seconds (default 300 seconds). The server will send a SIP qualify message to the ITSP every 300 seconds. This allows the ITSP to monitor the status of the SIP registration and latency. When finished here click on the Options tab.

The correct DTMF mode must be selected to match with the requirements of the ITSP. Typically Automatic RFC-2833/inband is selected. However most ITSP s support RFC-2833 because it is more reliable. The CODEC selection must match the requirements of the ITSP and any supported CODEC s not checked off will never be negotiated with the ITSP because they have not been allowed. The global Channel options defined in Configuration > Telephony > Configuration > Channels > Codecs will choose the first supported CODEC in the preferred order. No other options are required at this time so it is OK to click on the Add button.

Interoperable Products Polycom wired and wireless SIP phones are certified by ScopServ http://www.polycom.com Grandstream FXO/FXS gateways are certified by ScopServ http://www.grandstream.com Counterpath Softphones are certified by ScopServ http://www.counterpath.com Sangoma/Vegastream PSTN hardware is certified by ScopServ http://www.sangoma.com Quintum PSTN gateways are certified by ScopServ http://www.quintum.com Algo SIP paging peripherals are certified by ScopServ http://www.algosolutions.com Audiocodes Gateways and SIP Phones are certified by ScopServ http://www.audiocodes.com Phybridge CAT3 to Ethernet bridges and adaptors are certified by ScopServ http://www.phybridge.com