none
Implementing AudioCodes Mediant 1000 - What should I know?

    Question

  • I will be moving our small pilot Enterprise Voice deployment with 5 users, direct SIP to IP-PBX and no media bypass over to MS supported Mediant 1000 in the next couple of weeks.  Once that's done we'll transition more and more users over.

    How is the AudioCodes as far as ease of configuration and setup?  I'll be happy to accept any tips or helpful bits of information when it comes to working with this media gateway.

    I understand that I can remove my trunk translation rules in Lync and have the Mediant normalize E.164 for the IP-PBX, is this correct?  What is best practice?

     

    Thanks!

    Friday, July 15, 2011 9:45 PM

Answers

  • Unfortunately, there is no “quick and dirty” way to configure a gateway. My observations are that US gateway manufacturers are shutting themselves in the foot packing the devices with tons of unnecessary features when comes to “Lync Certified Gateway”, perhaps in driven by “Who has bigger” competition. This ultimately makes the configuration (almost) impossible task for an average person but, on other side, provides job security for the System Integrator Partners. Ferrari's gateway has 3 configuration menus but... this is another story.

    Now that I am done with the “fun” section, here it goes:

    There is no one single (Audiocodes) guide that describes step-by-step Mediant <-> Lync integration. Apparently AC folks learned how to write manuals from Microsoft in their early days, when everything was written as one MSFT talks to another. Microsoft evolved since…

    From your post is not clear if your Mediant is SBC as well (very different configuration steps.) If you decide to take the challenge and try to configure it , I will be happy to assist you. Just let me know.

     

    Drago


    http://www.lynclog.com
    Saturday, July 16, 2011 2:53 PM
  •  

    Echo everything Drago said, if you're not used to gateways/voice it will take some time to get your head around.

    In addition there are some nice video's here (with aweful computerised speech, but never mind that)

    http://www.audiocodes.com/web-based-technical-training

    Yes you can manipulate numbers on the Gateway if that's how you want to handle it.

    For media bypass you'll need TLS, which makes it slightly harder to troubleshoot (since you can't use wireshark to see what's going on). As a beginner I'd set it up as a TCP gateway first, then switch to TLS, that way any security/certificate issues won't throw you at the start.

    hope that helps, good luck

    Tom


    If a post is helpful, please take a second to hit the green arrow on the left, or mark as answer, thanks
    Tom Arbuthnot, Consultant Modality Systems
    Blog: Lync'd Up Blog Subscribe: RSS
    Twitter @tomarbuthnot
    Saturday, July 16, 2011 5:20 PM
  • Hello,

    AudioCodes MSBG CPU actually base on two CPU’s and two IP-Addresses.

    You probably change only one of them.

    The default IP-Address of the GW, that relevant to you is 192.168.0.2, try open browser to it (HTTP://192.168.0.2), make sure that your Workstation/Laptop IP-Address is in the same network (e.g., 192.168.0.100 and Subnet Mask 255.255.255.0)!

     

    Maybe you restored only the first IP-Address (192.168.0.1) and the second it’s still the IP-Address that you assigned before. In this case, you need to change the Workstation/Laptop IP-Address to the same network and subnet mask of the assigned IP-Address and browse to it.

     

     

    You can find more information about AudioCodes GW in the following links:

    http://www.audiocodes.com/microsoft

     

    http://www.audiocodes.com/msbg

    And more:

     

    http://www.audiocodes.com

     

    In case that you need more advance technical support:

    support@audiocodes.com

                   

    Ofer Aharonov

    AudioCodes Interoperability Engineer

     

    Tuesday, July 19, 2011 8:33 AM

All replies

  • Unfortunately, there is no “quick and dirty” way to configure a gateway. My observations are that US gateway manufacturers are shutting themselves in the foot packing the devices with tons of unnecessary features when comes to “Lync Certified Gateway”, perhaps in driven by “Who has bigger” competition. This ultimately makes the configuration (almost) impossible task for an average person but, on other side, provides job security for the System Integrator Partners. Ferrari's gateway has 3 configuration menus but... this is another story.

    Now that I am done with the “fun” section, here it goes:

    There is no one single (Audiocodes) guide that describes step-by-step Mediant <-> Lync integration. Apparently AC folks learned how to write manuals from Microsoft in their early days, when everything was written as one MSFT talks to another. Microsoft evolved since…

    From your post is not clear if your Mediant is SBC as well (very different configuration steps.) If you decide to take the challenge and try to configure it , I will be happy to assist you. Just let me know.

     

    Drago


    http://www.lynclog.com
    Saturday, July 16, 2011 2:53 PM
  •  

    Echo everything Drago said, if you're not used to gateways/voice it will take some time to get your head around.

    In addition there are some nice video's here (with aweful computerised speech, but never mind that)

    http://www.audiocodes.com/web-based-technical-training

    Yes you can manipulate numbers on the Gateway if that's how you want to handle it.

    For media bypass you'll need TLS, which makes it slightly harder to troubleshoot (since you can't use wireshark to see what's going on). As a beginner I'd set it up as a TCP gateway first, then switch to TLS, that way any security/certificate issues won't throw you at the start.

    hope that helps, good luck

    Tom


    If a post is helpful, please take a second to hit the green arrow on the left, or mark as answer, thanks
    Tom Arbuthnot, Consultant Modality Systems
    Blog: Lync'd Up Blog Subscribe: RSS
    Twitter @tomarbuthnot
    Saturday, July 16, 2011 5:20 PM
  • Thank you both.  I'll start reading now.  

    It is just a gateway, not an SBC.  Tom, I've used media bypass with TCP and it worked fine (using set-csmediaconfiguration to not requite encryption), however I do plan on using TLS with this gateway.

    Monday, July 18, 2011 4:34 PM
  •  

    From your post is not clear if your Mediant is SBC as well (very different configuration steps.) If you decide to take the challenge and try to configure it , I will be happy to assist you. Just let me know.

     

    I received the gateway today.  It is a Mediant 1000B.  It appears it is an MSBG (from the short amount of time I was in the GUI).  Which to my knowledge is a gateway and SBC combined?  Please correct me if I'm wrong. 

    Anyway, I'm having a hell of a time just configuring an IP address on the management interface.  I could access the web based GUI at one point using the default IP.  So I configured a new IP address but I think I forgot to set the VLAN correctly, because I could not access the gateway with the new IP.  

    So then I did a factory reset using the terminal and rebooted.  I see it gets the default 192.168.x.x address again and I can ping it, but when i try to access the web GUI it redirects me to the first address I tried to set it to, which obviously doesn't work.  I looked everywhere in the CLI for another reset option or why it would be redirecting.

    Tuesday, July 19, 2011 2:30 AM
  • Hello,

    AudioCodes MSBG CPU actually base on two CPU’s and two IP-Addresses.

    You probably change only one of them.

    The default IP-Address of the GW, that relevant to you is 192.168.0.2, try open browser to it (HTTP://192.168.0.2), make sure that your Workstation/Laptop IP-Address is in the same network (e.g., 192.168.0.100 and Subnet Mask 255.255.255.0)!

     

    Maybe you restored only the first IP-Address (192.168.0.1) and the second it’s still the IP-Address that you assigned before. In this case, you need to change the Workstation/Laptop IP-Address to the same network and subnet mask of the assigned IP-Address and browse to it.

     

     

    You can find more information about AudioCodes GW in the following links:

    http://www.audiocodes.com/microsoft

     

    http://www.audiocodes.com/msbg

    And more:

     

    http://www.audiocodes.com

     

    In case that you need more advance technical support:

    support@audiocodes.com

                   

    Ofer Aharonov

    AudioCodes Interoperability Engineer

     

    Tuesday, July 19, 2011 8:33 AM
  • The LAN IP address by default is set to VLAN 1 but also strips the VLAN tag i.e. even if it says VLAN 1, you can plug it to any VLAN and still be able to access it.

    Follow Ofer’s advice to connect to the device. If you still cannot connect, login to AC site with your account (if you don’t have an account, ask your reseller to create one), navigate to http://www.audiocodes.com/downloads , select the model – Product family – CPE & Access Gateways, Product group –Analog Media Gateways, Product Mediant 1000, Version – 6.2 General Availability) and download SIP M1K and M600 Utility&Ini files Ver 6.2.zip. In folder Utilities you will find file ACSyslog120.exe – you will need it since Mediant 1000 does not have Logging pave on the GUI.

    Download BootP_2_3_0_17.zip as well. This utility can set the gateway with IP address of your choice upon boot. Refer to the product manual “LTRT-83308 Mediant 600 and Mediant 1000 SIP User's Manual v6.2” how to use it.

     

    Drago


    http://www.lynclog.com
    Tuesday, July 19, 2011 11:27 AM
  • I gained access to the web management again.  It was a misconfigured switch the mediant was plugged into.  Turns out the nearest (managed) switch to the mediant in the server room was not set up like all of the others.

    I'll will get that user account and start reading up.

    Drago, can you outline what exactly is different with configuring the MSBG as opposed to the standard M1K gateway?  I only plan on using the gateway features of this MSBG for now.

     

    Tuesday, July 19, 2011 4:28 PM
  • So far configuration seems to be going OK.  But I do have an issue, I think.

    I've configured the IP address of our DNS server in the GUI but I noticed that when I view the 'Call Routing Status' that my mediation server (configured as a proxy) is in a FAIL state.  So I used the Diagnostics Ping test in the GUI to ping my mediation server by name and IP, but both of them fail.  Even pinging the Mediant's default gateway fails.  I figured maybe that utility is broken so I connected to an SSH session on the Mediant and tried pinging, still nothing works.  Yet I am perfectly able to ping the Mediant from any workstation/server and obviously I'm able to connect to the web interface.

    Unfortunately i'm waiting on the T1's to be configured on our PBX so I can't move forward with the gateway configuration.  So this is where i stand.  Do I have any reason to be worried here?


    Wednesday, July 20, 2011 11:53 PM
  • 1. Actually, there difference between MSBG and MSBG-SBC. I thing MSBG incorporates Router/Firewall capabilities (look my first reply - this is what I meant)

    2. When comes to ping, pretty much depends if you configured the WAN interface. Do not mess with it. Act as it is not there at all. Rather try to telnet and see if the connection can be established. Let me know.

    3 Diagnostic ping test is misleading term. It uses the WAN interface to send the ping, but by default the WAN interface is firewalled. Audiocodes makes a good Gateways and I don't understand why taking on Cisco... Just do what you do best (hint hint)

     

    Drago


    http://www.lynclog.com
    Thursday, July 21, 2011 12:04 AM
  • 2. I've pretty much been acting as if it isn't there.  As I have no use for router/firewall capabilities on my internal LAN.

    3. This would explain why the ping tests fail.  If there is no way to test from the LAN interface I'll just have to wait until I can go further with my deployment before I can verify.

     

    Thanks

    Thursday, July 21, 2011 12:27 AM
  • Take your configuration strategy one step at the time. Configure M1K as SIP over TCP gateway. Accept the default ports (and configure the ports accordingly on M1K as well.) Install Wireshark on Lync server, filter trafic between the server and Gateway and observe the signaling (you must configure Wireshark to parse SIP traffic on the appropriate port). The joyful moment is when you see OPTIONS request from Lync and 200 OK from the gateway. Then you can breathe again.

    Once done with the network configuration/connectivity check, you will have three more steps - configuration of sip routing, manipulation tables and finaly, when calls are flowing in and out, transitioning from TCP to TLS.

    Dont forget to backup your .INI file on every successful step (name the file descriptively i.e. WorkingOptions.INI, WorkingOutboundCalls.INI and so on.) I have my WorkingWithAllFeatures.INI config file in a bank safe (smile)

     

    Drago


    http://www.lynclog.com
    Thursday, July 21, 2011 1:09 AM
  • Drago,

    This thread's a bit aged, but have a question regarding the AudioCodes. According to AudioCodes manual for the Mediants, there's a limit to how many IP-to-IP routes you can define (120). We're planning for our Enterprise Voice and other phone systems, with numbers that are not necessarily in nicely blocked chunks; we may need way more routes defined than the 120 route limit described in the documentation. Is this a hard-coded limit?

    I've tried calling AudioCodes support line, but all I got was "Let's sign you up for a support agreement."  


    me

    Friday, August 17, 2012 8:02 PM
  • I do not know the answer, but my guess would be - yes.

    Drago


    http://www.lynclog.com

    Monday, August 20, 2012 12:29 PM
  •  I have an Audio Codes Mediant 1000B between a Lync 2010 server and an Avaya PBX connected to the PSTN.  I am having issues with outbound users sending DTMF tones.  They are failing.  Has anyone had this problem and how was it fixed?
    Wednesday, September 26, 2012 8:45 PM
  • I'm working with a new Mediant 1000 and am having a hard time getting my head around the concept of the VoIP vs VLAN IPs.

    Why do I need a VLAN IP address for this device?  Shouldn't the WAN and internal "voice" interface suffice?

    Similarly,  is there a good (introductory) AudioCodes document I should read in order to understand the difference between the BOARD and DATA INI files, and how they relate to the System, VoIP, and Data sections of the configuration UI?


    Wednesday, October 10, 2012 1:51 PM