Jump to content

Dorigo

Members
  • Posts

    4
  • Joined

  • Last visited

Dorigo's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. Thanks, for the assistance. I believe we are back on track, outgoing calls appear resolved. PBX functional, trial done, new licences arranged. Greg
  2. 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?
  3. 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 ?
  4. 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.
×
×
  • Create New...