Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SIP trunk twinning issue 1

Status
Not open for further replies.

critchey

IS-IT--Management
Nov 17, 2015
1,793
US
I have a customer running R11.0.4.5 with SIP trunks. Everything about the SIP trunks appears to work correctly except the audio issue we are experiencing with twinning on the SIP trunks. In the past, when I encountered this issue, I would turn on keep alives under System>LAN1>VOIP and it would resolve the issue but not in this case. What is odd is whatever value I set for the keep alive timer the SIP trunks while twinning will start to get audio after that timer.

IE keep alive is setup for 5 seconds
You twin a call and get no audio for first 5 seconds and then audio starts after 5 seconds. If I adjust the timer it follows the timing so I know it is that value making a difference. I can set it as low as 2-3 seconds (1 second it seems like the audio cuts off after a bit). It makes it "usable", since you are without audio only for 2-3 seconds, but it is still not right.

Customer is in control of firewall it is a Mikrotik firewall which I am not familiar with at all. Wondering if anyone has had this issue and what they might suggest I ask the firewall guy to try (assuming the issue is in the firewall but Ill gladly make changes in the IPO as well). We actually initially had issues even getting audio with network topology being used in the IPO but that was finally resolved today so I feel like we are close. IT is saying he sees the RTP traffic, it is sent to the IPO but it waits the 2-3 seconds before accepting it. He says SIP_ALG is disabled (seemed like it was enabled till today but network topology works so I tend to believe it is disabled now).



The truth is just an excuse for lack of imagination.
 
So the IT guy contacted Mikrotik support and recieved this response:
"Try to change firewall NAT action=masquarade to action=src-nat with pointing outgoing IP address. Let us know if that somehow changes the behavior of the device."

The IT guy made the change and as of now that has fixed the issue. Figured Id post the resolution in case anyone else encounters the same problem.

The truth is just an excuse for lack of imagination.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top