ingate siparator documentation - ic 4 0 su3...our test example focused on udp, as demonstrated...

of 13

Contents 1. General Information ............................................................................................................................. 2

1. Ingate Siparator................................................................................................................................. 2

2. Warnings ........................................................................................................................................... 2

3. Vendor Contact ................................................................................................................................. 2

4. Version Verified................................................................................................................................. 2

5. Pre-Install .......................................................................................................................................... 2

6. Install ................................................................................................................................................. 3

7. Required Post Installation Steps ....................................................................................................... 3

2. Configuration Guide .............................................................................................................................. 3

1. Configure Networks and Computers In Siparator ............................................................................. 3

2. Dial Plan ............................................................................................................................................ 3

3. Line Configuration ............................................................................................................................. 4

1. Line Menu ..................................................................................................................................... 5

2. Identity (Out) Menu ...................................................................................................................... 6

3. Audio Menu .................................................................................................................................. 7

4. Transport Menu ............................................................................................................................ 8

5. Session Menu ................................................................................................................................ 9

6. Authentication Menu .................................................................................................................. 10

7. Proxy Menu ................................................................................................................................. 11

8. Access Menu ............................................................................................................................... 11

9. Region Menu ............................................................................................................................... 12

4. SIP Proxy Support ............................................................................................................................ 13

5. Fax Considerations .......................................................................................................................... 13

6. E911 Support ................................................................................................................................... 13

of 13

1. General Information

1. Ingate Siparator

2. Warnings

Check the SIP Carrier Matrix of the Interactive Intelligence Testlab website for certification

status and supported features.

http://testlab.inin.com

This validation test was performed with Siparator running in an Internal/LAN mode.

Siparator has been successfully run with other CIC systems in DMZ mode, DMZ/LAN mode,

and Standalone mode. This specific validation test only applies to Siparator running in an

Internal/LAN mode.

This validation test was performed with Siparator running as an SBC, and NOT in Back-to-

Back-User-Agent mode (B2BUA was not enabled). This test was performed with Siparator as

a forwarding agent only, and authentication was not enabled. Other customers have run

Siparator in a B2BUA mode while working with CIC. This validation test only applies to

Siparator running in a forwarding, un-authenticated, non-user-registered mode.

This validation test was performed with Siparator running as an SBC, and not as a Far End

NAT Traversal device. Other customers have run Siparator as a Far End NAT Traversal with

fully managed IP phones. This validation test only applies to Siparator running in a

forwarding, un-authenticated, non-user-registered mode.

3. Vendor Contact

http://www.ingate.com

4. Version Verified

Interaction Center 4.0 SU3

Required Engineering Specials (ES):

None installed

Ingate Siparator Version 5.0.2

5. Pre-Install

Ingate will provide a licensing file that will be usable for the environment. In order to

maintain DSCP tagging on Ingate traffic, the QoS license must be purchased from Ingate. In

of 13

order to utilize the basic SIP Dial Plan of Ingate, at least one SIP Trunk license must be

purchased from Ingate.

6. Install

A SIP Line must be created. See Line Configuration for more information.

The Dial plan in Ingate must be configured properly. See Dial Plan for more information.

7. Required Post Installation Steps

<…………………………….>

2. Configuration Guide

1. Configure Networks and Computers In Siparator

Go to “Network” -> “Networks and Computers”. Create an object for “WAN” and for “LAN”

as below. Please note your LAN configuration should reflect your internal network

environment:

2. Dial Plan

Ingate supports a robust dial plan. Go to “SIP Traffic” -> “Dial Plan”.

A sample configuration is here. Specify a simple “From Header” match that says “Any”

traffic.

of 13

Next, specify a Matching Request URI. In this case, we have specified a rule that matches

any traffic to the Siparator Private Interface (192.168.0.206, in this example):

Next, specify a “Forward To” target. Please note that the IP Address, Port, and Protocol

should reflect your carrier’s settings.

Finally, create the dial plan object that causes calls to forward to the carrier from the CIC

server. PLEASE OBSERVE the best practice of “rejecting” any traffic not specifically accepted

by Siparator. This is an important security precaution.

PLEASE NOTE: you will also need to configure Inbound call routing rules using the Matching

Request URI, the Forward To, and the Dial Plan. This configuration is required, and is not

demonstrated in the configuration above.

3. Line Configuration

The line page has a vast majority of the configuration options required for SIP Carrier setup.

This is the section that configures the connection to the carrier’s servers, any authentication

or registration information, and basic configuration needs.

Any reference to a menu, while talking about the line configuration, will refer to the options

on the left side of the line configuration page, and tabs will refer to the standard tab

interface across the top of the line configuration page.

of 13

1. Line Menu

• Active

The active box should be checked. This activates the line. If this box is not

checked, the line will not be available for any function. This can also be affected

by right clicking on the line in Interaction Administrator, dropping to the Set

Active menu option, and selecting Yes.

• Domain Name

This box should contain the FQDN of the Customer Domain as provided by your

carrier. In this case, as calls were simply forwarded directly, the domain name

was not important

• Enable T.38 Faxing (or Disable, if not supported by your carrier)

Siparator can pass through T.38 to the carrier. Please check to determine the

proper setting here.

• Remainder of Line Menu Options

These have no major direct impact on the SIP carrier configuration, and should

be addressed according to business needs.

of 13

2. Identity (Out) Menu

• Calling Address

Clicking the “…” button next to the Line Value 1 brings up the Configure Line

Value dialog.

• Address

Enter the Main DID to be used as the default User Portion on outgoing calls.

Ingate will pass through whatever is provided, and so please check with your

carrier regarding what is supported or not.

• Remainder of Identity (Out) Menu Options

These have no major direct impact on the SIP Carrier configuration and should

be addressed according to business needs.

of 13

3. Audio Menu

• Audio Path

The choice between Dynamic or Always-In is, for the most part, the choice of the

client with respect to the business being done on the server. In many cases, with

the use of Siparator, the decision of audio path will happen entirely on the private

network (be transparent to the carrier). However, there are several important

caveats.

o Dynamic audio for SIP carriers can sometimes exhibit less delay as

compared to Always-In audio. Much will depend upon your placement of

Siparator in relation to the carrier, and the location of your media servers

relative to Siparator.

o With Dynamic audio, audio will be brought into the Media Server when a

call is Recorded, Conferenced, Placed on Hold, or is navigating the IVR.

• DTMF Type

Siparator supports both In-Band and Out-of-Band (RFC2833) DTMF Types. Please

check with your carrier regarding which setting is correct here.

• Remainder of Audio Menu Options

These have no major direct impact on the SIP Carrier configuration and should be

addressed according to business needs.

of 13

4. Transport Menu

• Transport Protocol

Siparator supports UDP, TCP, and TLS. It is also possible for Siparator to support one

protocol on the LAN (TCP, for example) and a different protocol for the carrier (UDP,

perhaps). Even transcryption (doing TLS internal and UDP or TCP to the carrier—or

vice versa) is supported. Though the use of TLS in general (and transcryption in

particular) can reduce the available capacity on a Siparator unit. Siparator 21 units

can support all 50 sessions encrypted (no loss of capacity). Other Siparator models

(51, 55, 61, etc…) will see capacities reduced by 50% (i.e., a Siparator 51, which can

support 150 sessions without TLS, will only support 75 sessions with TLS). The

setting here should reflect your configuration on Siparator.

Our test example focused on UDP, as demonstrated above.

• Receive Port

This option should be set to match your configuration on Siparator. By default

Siparator only listens on port 5060 (for TCP or UDP) and 5061 (TLS).

Our test example focused on port 5060.

• Remainder of Transport Menu Options



of 13

5. Session Menu

• Media Timing

This should be set to Normal in most cases. Siparator was validated to support the

carrier and the CIC system sending media whenever is appropriate (Early or

Delayed), so in the end Siparator should reflect the carrier setting.

• Terminate Analysis on Connect

If Call Analysis is not desired (i.e., Dialer is not in play, and a call analysis function is

not desired for Call Forwarding, Speed Dials, or other features), then this is a setting

that can be enabled. Otherwise, it should be disabled. This setting is less about the

carrier’s desired setting, and more about the customer’s intended use of CIC.

• Remainder of Session Menu Options



of 13

6. Authentication Menu

In our validation cases, we did not use SIP Authenticaiton. Siparator does support

SIP Auth. Siparator can validate SIP directly using its own authentication database.

It can also pass authentication seamlessly through to the far end provider (allowing

CIC to authenticate to the carrier THROUGH Siparator, without Siparator itself doing

the authentication).

Siparator also supports registration to the carrier—it can “register” on behalf of CIC

to the carrier. In this case, often times the B2BUA (Back to Back User Agent) feature

is enabled.

Dialplan behavior in Siparator decides the appropriate approach. “Forwarding” the

traffic follows whatever rule is set on the Forward target (Send to IP, send to

registered user via B2BUA, etc…). Auth implies that Siparator will request the traffic

authenticate first to Siparator before sending on.

Our test case used only “forward” rules.

of 13

7. Proxy Menu

• Prioritized list of Proxy Addresses

When talking to Siparator, the Local or “LAN” IP address of the Siparator should

reside here.

• Remainder of Proxy Menu Options

These have no major direct impact on the SIP Carrier configuration, and should be


8. Access Menu

of 13

• All computers will be

This should be set to Denied Access to not only limit the remote end-points that

this line will accept calls from, but also so that other lines that use the same

Protocol/Port (eg UDP/5060) can be created.

• Exceptions

In this case, the only IP address that should be registered as an exception to the

“deny access” rule is the private or “LAN” IP address of the Siparator unit.

•

9. Region Menu

• Location

This should be set according to business needs, however should take care to assure

the assigned Location supports the proper codecs. Siparator will pass through any

RTP traffic of any kind. That will include G.722, Video, and virtually any traffic

signaled via SIP but encoded via RTP. HOWEVER, bear in mind that CIC itself

currently only supports G.711 and G.729AB.

Our test case validated only G.711.

of 13

4. SIP Proxy Support

This particular test case did not validate SIP Proxy support. However, other customers have

established connectivity through Siparator to a SIP Proxy for purposes of handling codecs

not supported by CIC. Examples would be G.722, Video, etc…

5. Fax Considerations

We did verify that T.38 faxing was successfully transmitted through a Siparator unit.

6. E911 Support

Siparator will pass through any remote phone number transmitted to it via CIC. That was a

case thoroughly validated by this interoperability test. Siparator can also overwrite these

numbers if needed—though in practice it is better to allow CIC to control ANI, and to keep

Siparator sending to the carrier whatever CIC sends it—and vice versa.

ingate siparator documentation - ic 4 0 su3...our test example focused on udp, as demonstrated...

Documents