Posted in AudioCodes, ShoreTel, Skype for Business

AudioCodes SBC Configuration

Diagram

sip-trunk-ippbx-3

Scenario

Configuration entities configured with the name “LAN” are used for interfacing with the LAN (e.g., IP PBX) and those configured with the name “WAN” are used for the interfacing with the WAN (e.g., SIP Trunk). IP addresses used above are only set as examples.

Device/Software

  • AudioCodes Mediant Software
  • Firmware Version: 7.00A.049.003

Step 1 – Assign Ethernet Ports to Ethernet Groups 

mediant-sw-ports

 LAN: Ethernet Group 1 with ports GE_1
 WAN: Ethernet Group 2 with ports GE_2

Configuration tab > VoIP menu > Network > Ethernet Groups Table

mediant-sw-ethernet-group

Step 2 – Assign VLAN IDs to Ethernet Groups

 LAN: VLAN ID 1 assigned to Ethernet Group 1
 WAN: VLAN ID 2 assigned to Ethernet Group 2

Configuration tab > VoIP menu > Network > Ethernet Device Table

mediant-sw-vlan

Step 3: Add Logical IP Network Interfaces for LAN and WAN

 LAN: IP address 172.16.0.234
 WAN: IP address 212.199.200.100

 VLAN 1 (Ethernet Group 1) is assigned to the LAN interface
 VLAN 2 (Ethernet Group 2) is assigned to the WAN interface

Configuration tab > VoIP menu > Network > IP Interfaces Table

mediant-sw-logical-ip

Step 4: Add Media Realms for LAN and WAN

Configuration tab > VoIP menu > VoIP Network > Media Realm Table

Media Realm for LAN Interface

mediant-sw-realm-lan

Media Realm for WAN Interface

mediant-sw-realm-wan

Step 5: Add SIP Interfaces for LAN and WAN

Configuration tab > VoIP menu > VoIP Network > SIP Interface Table

SIP Interface for LAN

mediant-sw-sip-int-lan

SIP Interface for WAN

mediant-sw-sip-int-wan

Step 6: Add Proxy Sets for IP PBX and SIP Trunk

The Proxy Set defines the actual address of SIP server entities in your network. Therefore, you need to add a Proxy Set for the following entities:
 LAN: IP PBX with address 172.16.0.231
 WAN: SIP Trunk with address 212.199.200.10

Configuration tab > VoIP menu > VoIP Network > Proxy Sets Table

Proxy Set for IP PBX (e.g. Skype for Business)

mediant-sw-proxy-lan

Select the table row of the Proxy Set that you added, and then click the Proxy Address Table link located below the table

mediant-sw-proxy-ip

Proxy Set for ITSP (e.g. Telstra)

mediant-sw-proxy-wan

Select the table row of the Proxy Set that you added, and then click the Proxy Address Table link located below the table.

mediant-sw-proxy-ip-wan

Step 7: Add IP Groups for IP PBX and SIP Trunk

The IP Group represents the SIP entity. In the example, you need to add an IP Group for the following entities:
 WAN SIP Trunk (server-type IP Group)
 LAN IP PBX (server-type IP Group)

Configuration tab > VoIP menu > VoIP Network > IP Group Table

IP Group for LAN IP PBX

mediant-sw-lan-ip-group

IP Group for WAN SIP Trunk

mediant-sw-wan-ip-group

Step 8: Add IP-to-IP Call Routing Rules

For call routing between the SIP entities, you need to add IP-to-IP routing rules for the following call directions:
 Calls from the WAN SIP Trunk to the LAN IP PBX.
 Calls from the LAN IP PBX to the WAN SIP Trunk.

Configuration tab > VoIP menu > SBC > Routing SBC > IP-to-IP Routing Table

Call Routing Rule from WAN SIP Trunk to LAN IP PBX

mediant-sw-wan-to-lan

Call Routing Rule from LAN IP PBX to WAN SIP Trunk

mediant-lan-to-wan

It will look like this

mediant-sw-ip-to-ip

Note: A destination SIP Interface is not specified for the routing rules. The ‘Destination SIP Interface’ parameter is applicable only if the ‘Destination Type’ parameter is configured to any value other than IP Group.

Step 9: Add IP-to-IP Manipulations

Essentially, manipulation will depend on your scenario and requirements. Like for example, if your IP-PBX is a Skype for Business you need to configure your incoming destination number to be in E.164 format like +65912345678. On the other hand, the destination number for outgoing calls must strip + sign or + and country code. And usually add 00 for international calls.

I will discuss more of this on another blog so just tune in.

Hope it’ll help you to initially setup your AudioCodes Mediant SW SBC!!

Thanks!

Advertisements
Posted in AudioCodes, ShoreTel

Incoming call disconnects after 32 seconds!!!

Scenario:

  • Inbound: Optus -> SBC -> ShoreTel
  • Incoming call from Optus to Shoretel drops after 32 seconds

Diagram:

  • Optus -> SBC -> ShoreTel

32-seconds-hangup

As you can see on the SIP ladder diagram above, there’s unusual multiple 200 OK response from ShoreTel.

Solution: Unfortunately, the solution wasn’t shared by ShoreTel engineers, however the fixed was done on their end. So the next time you see above trace within SBC, immediately asks assistance from ShoreTel engineer to address the issue on their end.

Cheers!

Posted in AudioCodes, ShoreTel

488 Not Acceptable Here

Happy New Year!

After spending a vacation for Christmas, I had my first AudioCodes virtual SBC implementation for this year and the error above took me a while to resolve. A while means few hours, thank God not days 🙂

So here’s the scenario.

ShoreTel -> SBC -> Optus

Essentially, the error above only happens to few outbound numbers. Almost all other numbers are working fine. Diagram below shows where the 488 Not Acceptable Here error comes from.

488-not-acceptable-here

Based on the error, when Optus is sending a valid 180 Ringing to SBC, for some reason the SBC automatically sending “488 Not Acceptable Here” error to ShoreTel thus call is not able to connect successfully.

Solution: On the SBC’s IP Profile for ShoreTel leg, you have to disable “Early Media”. Search for parameter IpProfile_EnableEarlyMedia.

Note: When EarlyMedia is enabled, the device sends a SIP 18x response with SDP, allowing the media stream to be established before the call is answered. However, on above case the SBC doesn’t have Media channels and DSP resources on Feature Key license that’s why it can’t construct the SIP 18x response with SDP. So the only option is to disable it.

Thanks!