Jump to content

Leaderboard

The search index is currently processing. Leaderboard results may not be complete.

Popular Content

Showing content with the highest reputation since 05/25/2021 in Posts

  1. Is there any ETA when v5 will be available for general public?
    3 points
  2. you can enable double record route in kamailio, so kamailio will put both public and private ips, but actual communication will be on private ips between freeswitch and kamailio,
    1 point
  3. I may have overlooked this, but is there a way to modify the config of a yealink phone through advance provisioner? Example: I have several phones that I need to kill DND for. If I can get into them, I can dump the config, add the line needed, and upload back to the phone, but is there a way to do this using advanced provisioner for phones that are on a VLAN that I cannot access remotely? Thanks for any input
    1 point
  4. Provided you have the ability to serve web pages over the Internet, you can create an XML file to support the functions you want to change and serve it on your web server. The option to retrieve the file is in Advanced Provisioner under Settings | Custom Config File URL. Please consider to never store credentials or personal information in that file.
    1 point
  5. I can also confirm this, in Amazon EC2. But I only needed to change the Kamailio config. Correction; I also needed to add external/public ip to FreeSWITCH server at ext-rtp-ip, otherwise the sound didn't work. Br Tomas
    1 point
  6. How do I set multiple phones to a single voicemail box? I want multiple phones to be able to access our single “support” voicemail. Can my same phone have more than 1 mailbox? YES! Here’s how: Open your Provisioner App. (This is slated for access in SmartPBX shortly) Select the Devices tab Select the device you want to update. Go to the Combo Keys tab From the dropdown for Type, select BLF In the Value field, enter *98[voice Mailbox number] as its value. There should be no spaces. Label
    1 point
  7. Can confirm, applied these settings to a sandbox deployment without a bindable external IP and everything worked perfect.
    1 point
  8. You might find this link helpful. Although it's for AWS, the same config (at least mostly) would apply to Azure. https://github.com/OpenTelecom/kazoo-install-guide
    1 point
  9. The below works in AWS. I haven't worked much with Azure's networking environment, but I can't imagine (well, I can, it's Microsoft) that the DNAT / SNAT workings are too different. Assign PUB IP to instance/interface, then just change the below configs in Kamailio and Freeswitch. If you're using an all-in-one, then you'll just need one PUB. I've got a clustered setup going with my Kama and FS instances separate. On Freeswitch - Remember FS trunks directly out of the cluster. It does not route out back through Kamailio. nano /etc/kazoo/freeswitch/sip_profiles/sipinterface_1.x
    1 point
×
×
  • Create New...