Jump to content

Vodia PBX

Administrators
  • Posts

    11,035
  • Joined

  • Last visited

2 Followers

Profile Information

  • Gender
    Male

Recent Profile Visitors

195,095 profile views

Vodia PBX's Achievements

Grand Master

Grand Master (14/14)

  • Conversation Starter Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Posting Machine Rare

Recent Badges

0

Reputation

  1. Well the question was 15 years ago LOL. The PBX has the "virtual private assistant" for that the recognizes the caller-ID with the cell phone number of an extension, which is convenient and reasonable safe, especially when e.g. STIR/SHAKEN is at play to make sure that the caller-ID is not spoofed.
  2. That one probably is really because of the time zone. We'll fix that in the next build. As for the popup, we'll probably have to use it ourselves and see what is happening...
  3. We have moved the push server back to the old servers for now — the problem is that we need the new push servers for the new Android app which is also supposed to work with 68. We are checking if we need to enable more ciphers on the new push server.
  4. Are you still getting the emergency call notification?! IMHO this should have been resolved in the Windows app and also with the 69.2.3 build.
  5. Vodia PBX

    69.2.1

    We'll have a 69.2.3 soon, we'll include the MacOS this time...
  6. There is a setting "Follow RTP" (in reg_rtpsettings.htm) for that. I guess this one is turned on? Then the PBX should follow the RTP. You should see a message like "Tuning to new SSRC from xxx" (log level 5, media). The message "Source address for sip:xxxxx has changed from tls:192.168.x.y:39992 to tls:80.226.x.x:43321" is not related to RTP, this is about the registration, it is actually pretty useless if you have mobile device that change the IP address all the time.
  7. There is actually a new Vodia Android app in the process of getting released, we'll find out how to get it.
  8. Oh maybe this is because you are using the 8 prefix for the mailbox? Does the pattern !E!30! work? It should not be !E!830!. If you want to use the timeout, it should be !T!30!.
  9. Well you could probably also use an auto attendant for that. Anyhow if you use an IVR node, the cryptical DTMF list can have a T entry (for timeout), like !T!815! and the duration for the timeout is in the "Timeout (secs)" setting. The E entry is used for end-of-audio. Also, make sure that you use a single space as separator for the cryptical list.
  10. There are release notes for Version 68. As for the beta, we don't publish release notes.
  11. 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.
  12. In such cases it makes sense to turn PCAP on and take a look at the packets. Even they are not really from the network interface they give you an impression what the PBX feels about RTP and where its coming from.
  13. Sounds like something simple... Maybe can you include a screenshot of where you set it?
  14. If you want your users to login, you should make sure that the PBX can present a valid certificate for the domain. More and more browsers will make life hard entering passwords and sending them in clear text to a server does not even have a valid certificate.
×
×
  • Create New...