Problem Description
An IVR has encountered an issue where in certain Announcement is not being played. The signaling path is from SipServer where the incoming call is receive and communicates to an IVR application for some announcement to be played. The customer has integrated F5 in between SipServer and to the IVR possibly for load balancing. It was expected that once F5 receives the Sip Messages it will just forward it to the destination IP.
It was observe that previous INVITE messages to the IVR for the same call was successful and was only failing for some. We have compared the two example and observe that successful INVTES were not fragmented compared to the failed ones. We conducted packet traces on the SipServer and F5 and confirmed the following:
1. Verified from Sip Server that Invite is sent to the IVR for the announcement however the Sip packet has been fragmented due to custom sip headers required by the IVR application to play the correct announcement audio.
2. Using wireshark/packet trace it was confirmed that F5 device was able to receive the complete fragmented packets however it was not able to forward the Invite request to the IVR.
Issue was identified with the F5 device in regards to processing fragmented sip packets. Configuration changes was made on the F5 device.
This blog will be focus on understanding Session Initiation Protocol mainly based on the integration of different telephony platform such as Asterisk, Cisco Call Manager, Avaya and digital gateways to a Sip Server. This will also include helpful commands in managing the different telephony platform on issue encountered in the deployment and integration.
Tuesday, November 12, 2019
Friday, October 18, 2019
I am Back
After 8 years I have developed again an interest in documenting issues that I am encountering in VOIP and SIP technologies.
The workload that I facing at my current job requires that I document unusual call scenarios related to RFC 3261 for Sip.
This involves working with different PBX/Media gateway platform, such as Avaya, Cisco and Audiocodes.
If you have any questions related to RFC 3261 implementation please let me know.
I will be reviewing my old post and will remove post that I consider incorrect and/or irrelevant. This blog was created to document the challenges I am encountering and be able to ask for help and document how the issue progress.
Subscribe to:
Posts (Atom)
Issue Between Sip Server and F5 in Handling Fragmented Sip Packets
Problem Description An IVR has encountered an issue where in certain Announcement is not being played. The signaling path is from SipServe...
-
Problem Description An IVR has encountered an issue where in certain Announcement is not being played. The signaling path is from SipServe...
-
After 8 years I have developed again an interest in documenting issues that I am encountering in VOIP and SIP technologies. The workload tha...
-
The following are useful commandline for managing opensips and other related applications. python -c "import sys, gnutls; print gnutls...