Posts

Showing posts from August, 2017 Show all
I've had multiple clients approach me with the same scenario in Skype for Business/Lync 2013: <NAME> in <DEPARTMENT> wants to change the caller id for their individual DID or extension to a different number.  For clients that have a Sonus 1k/2k SBC, this is very easy to do. Transformation rules on the Sonus 1k/2k SBC allow for manipulating the 'Calling Party Address/Number' field. The 'Calling Party' is who initiates the call. If we change the calling party from the users number to the number they want, that addresses their issue. First, we create a transformation rule. Below are examples for both an e164 number and an extension: Extenstion Example E164 Example Lastly, we'll also need to include a 'catch all' rule. The 'catch all' rule catches any other number and passes it through without manipulation. Below is an example: Catch All Example After our rules are created, we'll need to make sure they are order...
A customer contacted me with an inbound call issue. Inbound calls were taking at least 30 seconds to connect, and some would not connect at all. While I've experienced call delays before, the root cause was different each time I investigated. Since the issue was happening so frequently, I took a SIP trace from their Audio Codes Gateway. I noticed the following pattern in the SIP trace: INVITE SIP 183 INVITE SIP 183 CANCEL 200 OK If everything was working correctly, *I should* see the SIP 183 answered with a '200 OK' rather than an additional SIP 183. My initial thought was, "Why isn't the carrier answering my 183 message?" I spoke with an engineer from the carrier (AT&T) and he provided logs from his end showing they were, in fact, answering my SIP 183. The customer side, however, was not sending the SIP 200 back to them. What's going on here? The carrier's log proved they weren't causing the problem. The other time I've exper...