Jump to content

Vodia PBX

Administrators
  • Content Count

    9,759
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Vodia PBX

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

192,480 profile views
  1. Are you on version 1.4 of the iOS app? Also are you on a recent version of the PBX (e.g. 65.0.10)? The new version support support a fast app start, which should make sure that only a few messages are exchanged to answer the call.
  2. Vodia PBX

    iOS App crashes

    The app probably has problems getting to the PBX. When you generate the QR-code, you should do from a browser that is coming from a similar location like the phone. In other words, if you use "localhost" the phone might have problems finding the PBX. Ideally, you should use a DNS address for the domain that has a certificate. If you have a certificate, make sure that you are using the https scheme for the URL.
  3. If the app shows the extensions in the domain on the home screen, that means that it can talk to the PBX. If not I would check the certificate (if you are on public IP, using letsencrypt should be easy) and what URL was provisioned into the app (click on the account name to check the settings). If that works, only the firewall could be blocking RTP. I would check first if you can make an outbound call before receiving a call. This also makes sure that the app has the microphone permission which sometimes is invisible if you accept the call from the iOS incoming call dialog.
  4. You can put multiple identities through provisioning only within the same domain (you can still use multiple domains manually through classic SIP registration). For this you need to copy & paste the MAC address from your first account into the other accounts and re-sync the device. The order is kind of random, not sure if it is sorted by MAC or by first addition and there is frankly not much control over it. But in many cases you don't need that. The ACD has a feature for virtual offices, so that the PBX can indicate the called number on the display or even through a small announcement at the beginning of the call. Your setup sounds like it should work. I would double check that the address did not get blacklisted. In the button profile, you can select the "identity" it should use when assigning a button. This should be important for the phone, so that at least one line is available for each registration.
  5. One thing that is (and probably will remain) a problem is if your PBX is in the LAN and the app is not. Then the wakeup from Apple will still work, but the app cannot contact the PBX and then you will have that effect. The solution for this is to make the PBX available from anywhere (AKA public IP), either by putting it into the cloud or programming your firewall to make it look like that.
  6. If there is a "green" icon next to the address and your PBX operates on a "routable" address, it should work with all browsers. Some browsers have special flags that allow exceptions, for example to allow WebRTC on insecure connections like http. After uploading a X.509 certificate, many browsers still keep the old certificate in the cache. In such cases "F5" is often not enough to refresh the cache. If the iOS also rejects the certificate, well then there must be something wrong with the import or the name of the certificate. The internet is full of forum questions around certificates (not only on the Vodia PBX)... The easiest is to use a lets encrypt certificate where this is all done automatically for you.
  7. The PBX just calls the number that was visible. That is okay in most cases. But I agree, we should confirm the number to avoid accidental call backs. The other thing that we are working on is a virtual hold, where the caller gets called back at a time when the caller would be waiting in line.
  8. It is not a simple topic. Generally speaking, "never change a running system". This applies especially for older models where is it sometimes better to leave them running with their version, even if there are know bugs instead of taking the risk of upgrading them with new problems. Apart from that, it makes sense to use the latest official releases. If you feel you need to use a different version, I would try those versions. You can do this specifically for one extension, just change the firmware link in the parameter section for the extension (in the provisioning tab).
  9. This is usually a problem for the ATA—I assume that you are using one? On the PBX, you would have to assign a "dial plan" for the extension where the ATA is registered. Then you should be able to dial out.
  10. The first one (whatever that is). If you put the DID on a ACD, it will try to route it to an agent that is available on the app and if there are several available, it will send it to the one that was in the conversation.
  11. I would make a PCAP trace for the call and see what happens in terms of SIP and RTP. You can open a ticket and attach the PCAP there so that we can take a look in private.
  12. Thanks. We actually fixed a similar problem recently with initial DTMF coming in after a transfer from another system.
  13. You can assign as many DID as you want to an extension. For example, you could assign one just for conferencing purposes. Depending where you are coming from, this "DID" can also contain also alphanumeric characters. So for example, you could use the alias name "conf-5434634564" as DID/alias name for the extension and then call in from a trunk that goes directly to the conference server, so that there are no carriers involved. The PBX will then take care about ringing the user up, including desktop phones, cell phones and apps.
  14. We are not against it at all, actually believe that this is a great step into reducing SPAM and increasing office productivity. There is a nice description on the Bandwidth web page (https://www.bandwidth.com/glossary/stir-shaken/) that explains the call flow. The PBX is either the "calling party" or the "called party", authentication is done through username and password. So the PBX would be the "end user"—even if the PBX is not physically on the end user premises. Do you know any SIP trunk provider that would parse STIR/SHAKEN headers?
×
×
  • Create New...