Changing The MTU On An AudioCodes E-SBC Device

I recently had a requirement to change the MTU on an AudioCodes E-SBC to match that of an upstream routing device. The MTU change cannot be made via the GUI and must be performed via the CLI, if you don’t have access to supporting documentation this can be quite difficult to locate.

1. Using Putty or a similar application connect to your device using Telnet as the connectivity method.

2. When prompted for authentication enter the devices user name and password.

3. Once authenticated type the word “enable” and when prompted enter the enable password, if you do not know this or it doesn’t match the password you utilised to initially authenticate, try the devices default password.

4. Once in enable mode enter the following commands, each on a new line, in order to change the MTU. Note the MTU listed is an example and should be adjusted to match that of the upstream routing equipment. The listed interface in this example is the one that is connected to the routing device, to identify what interface name you need to use run “show running-config” and review the output until you see the interface name that matches the assigned IP address to the WAN interface for example.

configure data
interface gigabitethernet 0/0
mtu 1400

That’s it all done, don’t forget to burn the change to flash once complete.

AudioCodes E-SBC – Removing ;ext= From An INVITE Header

Recently I was performing an integration between Microsoft Lync Server 2013 and an Alcatel OmniPCX phone system at a customer site. The existing PBX already had an element of VoIP via a separate platform called OpenTouch which allowed users to have multiple devices associated with a single extension. For an unknown reason when calling OpenTouch users via Lync Server 2013, which caused the call to be sent to an AudioCodes Virtual E-SBC and then onto the Alcatel PBX via a direct SIP trunk, the users handset would not ring. After working with the customers Alcatel vendor, it transpired the OpenTouch platform did not like INVITE’s that were sent with a from destination of +441234567890;ext=7890 for example, and the ;ext= element was causing the issue. In order to remove this aspect from an INVITE the ;ext= element needed to be stripped from the INVITE header using a Message Manipulation on the AudioCodes E-SBC, as with Sonus devices a regular expression is required in order to remove any parts of an INVITE we do not need. On an AudioCodes devices running version 6.8 of the firmware, the following was performed.

1. When logged into the device and expand VoIP -> SIP Definitions -> Msg Policy & Manipulations and then select Message Manipulations.

2. In the Message Manipulations table, click add and provide an Index number, such as 1 if this is your first manipulation and then proceed to configure the manipulation as per the provided screenshot below.

Message Manipulation 1024x96 AudioCodes E SBC   Removing ;ext= From An INVITE Header

3. To understand how Message Manipulation works, in the condition section this where we look for specific information within the INVITE. In this case we are using a regular expression to place each part of the INVITE header into a variable. For example the (.*) part of the condition places the value into variable $1, this would be the +441234567890 part of the number only, the next part of the regular expression (;ext=) would be placed in variable $2 which would only be the (;ext=) part of the header and so on and so forth. By placing each part of the header into variable we can then control the manipulation by specifying an Action Value, this Action Value constructs the header using only specific parts that we wish to use. For example, to gain a result that removes the ;ext= element, we would use $1 (+441234567890) and then $4 (@) and then $5 ( to construct a header that displays

4. Once this is complete, expand VoIP -> VoIP Network -> IP Group and then edit the IP Group you wish to apply the message manipulation to. When the properties of the manipulation opens, enter the Manipulation Set ID that you entered in step 2 into either the inbound or outbound manipulation set ID dialog boxes depending on the direction in which you need to apply the manipulation, as illustrated below.

SBC Manipulation Set AudioCodes E SBC   Removing ;ext= From An INVITE Header

That’s it, when performing a debug trace on the gateway you should now see the ;ext= element has now been removed from the INVITE header.

AudioCodes Mediant 1000 MSBG – Audio Quality Issue

So it’s been a long time since I last posted an article on the site, Microsoft Lync Server 2010 has been keeping me busy to say the least. During a recent deployment I experienced an issue with audio quality for both inbound and outbound calls when utilising an AudioCodes Mediant 1000 MSBG gateway running firmware version 6.2. The best way I can describe the problem was that when the call was answered it sounded like the person on the other end was stood next to a jet engine, there was a lost of noise and loss on the connection. When running  a syslog on the mediant, in debug level five, and reproducing the issue I could see the following events:

SRTP Error – failed decrypting RTCP packet: authentication failure (2) [Code:3700e] [CID:30]
SRTP Error – failed decrypting RTCP packet: wrong SSRC (11)
SRTP_PCK_DROP_AUTH:1  [Code:5004] [CID:30]
ErrMgs=9 Invalid RTP version (= 0)

When initially looking at these errors I was thinking either a coders or certificate issue could be causing the problem. This was actually incorrect, after some investigation it turned out that my TDM Bus Settings were not configured with the correct LAW attributes. To resolve the issue I performed the following:

1. Log in to the AudioCodes Mediant 1000 MSBG device.

2. On the left hand side of the screen select the “Full” radio button.

3. Ensure you have select the configuration tab and expand the “VoIP” container.

4. Expand the “TDM” container and then select “TDM Bus Settings”.

5. In the TDM Bus Settings page, if you are located in Europe set the “PCM LAW Select” value to “ALaw”. If you are based in the United States this should be set to “ULaw”.

6. Set the TDM Bus Clock Source value to “Network” and click submit in the bottom right hand corner of the screen.

7. At the top of the screen click the “Burn” button to save the configuration to flash and then reset the gateway.

That’s it, your poor quality audio issue should now be resolved.