Dorigo Posted March 3 Report Share Posted March 3 Hi there, just reaching out to see if there are any settings in an Azure VM that causes our system to have no audio or dial out, firewall ? We are in a trial period and testing, Azure is a total failure. However, using another VM (not azure) with the same sip trunks and settings is working perfect. We just disabled trunks between each during testing or just had one on each enabled, and have separate Yealink T54W phones provisioned, located at the same office. The phones provision ok, but the Azure setup as mentioned no sound on either side when calling in, unable to dial out. Both systems Deb 12, both latest Vodia version, standard default ports in usage. Have changed port rules in Azure without any success so far, destination IP or any. Located in AU, Azure VM also in AU. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 4 Report Share Posted March 4 Did you try setting the "IP routing list" (in /reg_sipsettings.htm) to "public"? Quote Link to comment Share on other sites More sharing options...
Dorigo Posted March 4 Author Report Share Posted March 4 Is that a setting in the web management GUI or do I need to ssh and manually change settings? I've changed to preset light gray default from "private public" to just public ? Do we need to add url's as well ? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 5 Report Share Posted March 5 The screenshot shows the right location. If you don't put the polling address there, it will use the address that it learns when it checks the license server which includes the IP address from where the request was coming from. So if the IP address does not change, you should be good. If the calls connect properly thats a sign that the signaling works. You can take a look at the SIP call messages and the SDP attachments. if they contain the public IP address, the PBX is doing it right and then the question is if the ports are properly exposed. You can try turning on PCAP for an extension and e.g. call the mailbox with *97 and then check the RTP in the PCAP. Quote Link to comment Share on other sites More sharing options...
Dorigo Posted March 5 Author Report Share Posted March 5 (edited) Hi I have a pcap capture, but not sure what I should be looking for? The settings between a known good VM and Azure appear identical, using the same trunks, but the AzureVM fails to dial out, "not found" error. Both systems using mostly all default settings, no changes to ports etc. Assuming a missed setting that I've not seen in the documentations - Azure specific? Edited March 6 by Vodia PBX Removed PCAP for privacy reasons Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted March 6 Report Share Posted March 6 Well the PCAP show that the number that you have dialed does not exist (removed the PCAP to hide the domain name and IP addresses)... This is not related to port forwarding. You might have to set up a SIP trunk and dial plan to get that working. As for the media connectivity, just dial *97 to see if you can hear the mailbox announcements. Quote Link to comment Share on other sites More sharing options...
Dorigo Posted March 6 Author Report Share Posted March 6 Thanks, for the assistance. I believe we are back on track, outgoing calls appear resolved. PBX functional, trial done, new licences arranged. Greg Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.