With the drive of unified communications to cloud based connectivity, a Session Border Controller (SBC) can play an important part in supporting a migration from premise equipment. Some gateway manufactures provide a convenient Graphical User Interface (GUI), others still focus on leveraging a command line interface (CLI). This overview will step through the generation and signing of the certificates that would be used for Tranport Layer Security (TLS) for both signaling and media within a Cisco Unified Border Element (CUBE).
With some recent troubleshooting, there was a need to capture packets off a Cisco ISR. Walking through the steps is small effort, however there are some some notes that can aid with the configuration.
For those of you who open their Cisco CUBE to 0.0.0.0 0.0.0.0 or issue the no ip address trusted list command, hopefully this may change your mind.
Working with voip.ms for the first time was pretty straightforward. I liked the $.99/mo DID with a pay per minute session that allowed simultaneous connections across my lab SIP trunk. After adding some funds, it appeared that their wiki page’s configuration was not working properly. I imagine it would be a common problem, so below is the debug message that took me down the path for a successful 200 OK SIP connection as well as the correct sip-ua configuration.