BGP Route flaps, accidental fiber cuts, equipment failure, these are all things that trigger outages and cause traffic to behave erratically and unpredictably. In the moment of crisis, a five minute voice outage feels like an eternity. What many people do not realize is, just when the network begins to “normalize” itself, this will cause [...]
Archive for the ‘Acme Packet’ Category
Acme Packet SBC: SIP Endpoint Registration Behavior During a Network Outage (avoiding SIP overload and registration flooding)
Posted: 21st December 2012 by Mark in Acme Packet, BroadWorks, SBC, SIP0
Acme Packet SBC: Configuring “Selective” Early Media Suppression
Posted: 18th December 2012 by Mark in Acme Packet, BroadWorks, SBC, SIPThe Acme Packet SBC includes support for Early Media Suppression. This allows you to decide what Realms can and cannot support Early Media and in what direction Early Media is allowed. Taking it one step further, the Acme Packet SBC also supports Selective Early Media Suppression. This means that even if a realm is configured [...]
Active Directory based Call Routing on the Acme Packet SBC (Integrating CUCM, Microsoft Lync, and PSTN SIP Trunking)
Posted: 5th October 2012 by Mark in Acme Packet, SBC, SIPMany Enterprises have migrated (or will soon migrate) to SIP Trunking for PSTN access. For an Enterprise with a single IP PBX platform and an SBC on the edge, call routing from the PSTN to the internal network is typically very straight forward because all DID’s point to one IP platform. Example of a simple [...]
Acme Packet SBC: The New “SIP Monitoring and Tracing” Tool for Troubleshooting SIP Calls
Posted: 8th August 2012 by Mark in Acme Packet, SBC, SIPDiagnosing a troubled SIP call has a tendency to be a real pain. Whether it’s running wireshark, tcpdump, or collecting debugs, having to sort through duplicate packets and attempting to merge different pcap files together does not provide a simple way to troubleshoot a single call while looking at both sides of the call in [...]
Acme Packet Linux SBC: Assigning Network Interface Names to Physical Ports (Port Allocation)
Posted: 31st May 2012 by Mark in Acme Packet, SIPThe Acme Packet SBC is now available in a Server Edition that runs on HP DL series servers. The platform is based on the same C-Series code that is used in the 3800 and 4500 appliances and runs on an Acme Packet optimized Linux kernel. There are some configuration elements that vary between the Server [...]
Acme Packet SBC and “trans-expire” Timers (reducing post-dial delay due to Invite timeout)
Posted: 10th April 2012 by Mark in Acme Packet, SBC, SIPBy default when a SIP Invite is sent from a SIP endpoint to the Acme Packet SBC, the default expires timer is used to determine when the Invite will timeout based on no response. Changing this globally may not produce the desired result as this impacts all Invites to all devices across all realms. In [...]
Acme Packet SBC and the “register-grace-timer” sip-config Option
Posted: 24th January 2012 by Mark in Acme Packet, BroadWorks, SBC, SIPThe Acme Packet SBC contains an optional parameter that may be added to the configuration which helps avoid a SIP avalanche from occurring. One instance of a SIP avalanche is when a very large number of SIP endpoints consecutively send SIP registrations to an SBC which then forwards them to a SIP registrar. This can [...]
The Acme Packet 3800 and 4500 series Session Border Controllers come with an NIU (Network Interface Unit) that includes four Gigabit ports. In rare cases one may need to support Media Aggregation where two of the Gigabit interfaces need to be look like they are “bonded” to accommodate a large number of calls (with media [...]
Acme Packet SBC “load-limit” Command Option
Posted: 9th November 2011 by Mark in Acme Packet, SIP, UnixThe Acme Packet SBC has an optional parameter that may be added under sip-config that allows the SBC to gracefully handle traffic in the event the SBC’s main processor reaches a certain threshold. There are several reasons as to why this may occur, but at the most basic level it’s a good idea to draw [...]
In most cases a SIP Redirect Server simply responds to a SIP Invite with a 302 Moved Temp message and provides multiple contacts in the Contact Header. When this occurs, the device receiving the 302 Moved Temp message (such as an Acme Packet SBC) will attempt to contact (ie. send a SIP Invite) the first [...]