![]() I had a conf call with one of their senior developers today to discuss the issue and see if a patch can be put into a firmware update. Meraki support have confirmed that all their products do not support SIP. This issue is related to outbound external calls only, sorry for not clarifying earlier. The initial outbound call rings the number being called, but upon answering, there is no audio or only one-way - Calls between sites over the VPN work perfectly. We're therefore sending our SIP provider an internal .x address which they will never be able to connect to, and this is why outbound one-way voice or no voice at all is being experienced. This is exactly what's happening to our outbound SIP packets on both Lync & Avaya, the Meraki firewall isn't replacing the internal IP address in the SDP/RTP packet with the NAT public IP. ![]() You hit the nail on the head when you said "Then your PBX might need some SBC or similar configuration to present SIP headers correctly with your public IP". No port forwarding as its not required with a full 1:1 NAT. Inbound (external) and internal calls to other offices (over the VPN) work - We have a 1:1 NAT configured for each of the Avaya/Lync servers in each office on individual IP addresses. We experience one-way audio or no audio at all on outbound external calls only. Separate trunks are connected to each Avaya/Lync server locally in each respective country that our offices are present. SIP Trunks from a company called Pure-IP. Old Cisco 800/1900's in other offices that aren't experiencing the problem, but those Cisco's have SIP ALG capability. Meraki MX80's in the offices experiencing the audio issue. Here's the setup.Īvaya IP Office PBX (v8 & v9), Lync 2013 Enterprise Server (part of a 9 server farm) in each of those offices. ![]() Sorry for not providing the full info, thought i'd put the feelers out first. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |