Site to Site Extension Dialing Between SIP PBX and PRI PBX

Is it possible to set up site to site extension dialing between a SIP capable PBX and a PRI PBX?  At Site A we have  a Netvanta 7100 PBX which supports SIP.  At Site B we have a Toshiba CIX670 phone system that is setup with PRI.  Furthermore, Site A uses 4 digit extensions while Site B uses 3 digit extensions.

Yes, it is possible to have site to site extension dialing between a SIP capable PBX and PRI PBX.

First, there must be connectivity between both Site A and Site B; Site A should be able to ping devices on Site B and vice versa.  On a  private MPLS network this should not be a problem.

Second, there must be a SIP capable device at Site B that will process SIP calls to and from Site A on behalf of the Toshiba CIX670.  In this scenario, there is a Netvanta 908e Total Access router acting as SIP gateway that then delivers PRI to the Toshiba.

A SIP Trunk Account needs to be created on the Netvanta 7100 at Site A that points to the IP configured on the 908e at Site B.  A SIP Trunk Account needs to be created on the 908e TA that points to the IP address configured on the 7100 at Site A.  The port used is 5060.

A SIP Trunk Group needs to be created at Site A that includes the new SIP Trunk Account and that permits the digits you plan to use for dialing extensions at Site B. Since Site A is using 4 digit extensions, the permit template could look like 1XXX assuming 1XXX is not being used anywhere else on the system or by any other site that may be part of the VoIP network.

At Site B, a SIP Trunk Group that includes the new SIP Trunk Account needs to be created on the 908e that accepts calls to/from extensions at Site A.  For example, if Site A is using 7XXX extensions, then the SIP Trunk Group on the 908e at Site B needs to permit 7XXX.

At this point, dialing Ext. 1XXX  from Site A should be reaching the 908e on site B.  The next step is to route those calls to the PRI Trunk between the 908e and the Toshiba.  To do so, modify the PRI Trunk Group to permit 1XXX.  Doing this will route 1XXX calls coming in on the newly created SIP Trunk over to the PRI.  You can verify that calls are making it to the PRI by doing a VOICE> SUMMARY debug on the 908e.  While Debug is on, dial a 1XXX extension.  The Debug output should show dialed number 1XXX going from the new SIP Trunk over to the PRI Trunk.  If the Toshiba has not been configured to accept those calls, the call will fail with Unallocated Number message.

On the the Toshiba system, creating a DID table entry that routes incoming digits 1XXX to each of the 3 digit stations is the final step in allowing Site A to dial Site B extensions.

Allowing Site B to dial Site A extensions will require additional setup; hopefully a part II for this post will follow soon.

#adtran-netvanta, #netvanta-7100, #pri, #sip, #sip-to-pri, #site-to-site-dialing, #site-to-site-extensions, #voip

Windows 10 Symantec Endpoint Protection (SEP) Client 12.1.6 Compatibility

Windows 10 has been out for some time now.  Upon first being released, Symantec Endpoint Protection clients that were on Version 12.1.5 or older were no longer compatible if upgrading to Windows 10.

Symantec released SEP Version 12.1.6 for Windows 10 users.  Fast forward to today and Microsoft has released a Feature Update to Windows 10, version 1607.  In order to install the update, users running SEP 12.1.6 are prompted to uninstall SEP because it is no longer compatible with the newer version of Windows 10.

There is however a new version of SEP client 12.1.6 that is compatible with Windows 10.  Symantec Endpoint Protection 12.1.6 (12.1RU6 MP6) build 7061 (12.1.7061.6600) for enterprise users can be downloaded here by entering your serial number and downloading the file named Symantec_Endpoint_Protection_12.1.6_MP6_All_Clients_EN.zip.

#sep-12-1-5, #sep-12-1-5-to-12-1-6, #sep-windows-10-compatability, #symantec-endpoint-protection, #symantec-endpoint-protection-windows-10-compatability