Making Analog Devices Work with OCS – Part 2

Now that we’ve talked through some of the theories involved with analog devices (see part 1 here) let’s roll up our sleeves and configure our environment for Scenario #1.

Our first task is unpacking the Tenor AF gateway from NET.  This small form factor device will allow us to plug in eight analog devices to our OCS environment.

 

Using the supplied console (serial) cable we can log into the device with Putty:

During boot the device prompts us to press “i” to configure a static IP, press “i”

 

Next we put in our IP information:

 

Now we install the Tenor Configuration Manager (unless you happen to know the Tenor CLI-I don’t just yet).  The first time it starts we can either have it search for the device (takes a couple of seconds) or put in the IP of our device.  Now we’re in and ready to start configuring!

We’ll start by configuring SIP Signaling:

 

The important values for our scenario are highlighted above.

Yellow – The “-1” setting for Register Expiry Time tells the gateway not to register.

Pink – This is the IP of our digital gateway.

Red –  We uncheck “Allow Only Proxy Calls” so the calls from our other gateway won’t get rejected.

It’s important to click “Confirm/OK” before moving to the next screen or the TCM (Tenor Configuration Manager) will bark at you.

Now we’ll see the “Asterisk” Icon change to red-this means the gateway has changes ready to be applied.  Press the “Asterisk” to apply the changes:

  

Next we set our codec.  I stuck with G711 for this configuration, but you have a number of choices depending on your needs:

 

And now we configure outgoing routing to use “SIP Only”:

 

The IP side of our gateway is now configured-on to the FXS ports.  Let’s start by setting fax to use T38 and fall back to G711 (this is a common setting in the US):

 

Next we set our CAS Signaling:

 

This setting will allow the FXS port to send an offhook tone to the device if the remote party disconnects before the phone plugged into the port does:

And now we just need to add an entry for the Dialed Number to assign it to a port:

 

Green – This is the port our device will be plugged into.

Red – This is the exact dialed number we want this port to map to – if we want calls to 513-555-1111 to map to this port, we enter it here.  *Hint – If you want multiple numbers to go to the same port, you can do that here as well.

Yellow – As we aren’t registering to the other gateway, we want to leave the User Agent field unspecified.

At this point we need to remember to submit our changes to the Tenor again:

 

Now we just need to update our main T1 gateway with a route to the analog gateway:

For an Audio Codes we go to “Configuration>Routing Tables>Tel to IP Routing” and add an entry like below:

 

Here is the configuration for a NET VX:

 

In the case of a paging system you’re likely to only use an extension, so the DN (Dialed Number) would only be 3, 4 or 5 digits as would the route; but everything else would be the same.

Once the route is in place we can place test calls from the public network to our analog devices and start moving our devices off of the PBX.  One more step in the right direction!

Advertisements

About Kevin Peters

My name is Kevin Peters.
This entry was posted in Uncategorized and tagged , , , , , . Bookmark the permalink.

3 Responses to Making Analog Devices Work with OCS – Part 2

  1. Jonny says:

    Hi Kevin,

    Thanks for detail explanation….

    I am implementing Lync 2010 in my test environment, I have one question regarding Audio Code Media Pack 124. Is it possible to use Media Pack 124 (24 port FXS) with Lync to make analog device to work with Lync? As we have Audio Code MP124 box (24 port FXS port) for analog device & we want to use it. Currently we are using audio code MP124 with asterisk IP PBX & I do nt want to use Asterisk any more. I haven’t find any article related to Audio Code.

    Thanks in advance

    • Kevin Peters says:

      Hello Jonny,

      I am not sure if the 124 Media is directly supported or what firmware version is required, but from their site here: http://www.audiocodes.com/products/microsoft-gateways
      MediaPack Analog Gateways
      AudioCodes MediaPack Media Gateways support different configurations, enabling the connection of the Microsoft Unified Communications solution to different models of PBXs using analog ports in various FXO/FXS configurations.

      I have used mp-114/118 with Lync so I know those work and I would assume the 124’s work as well. I would recommend contacting your Audio Codes vendor for more information.

      Thanks for reading!
      -kp

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s