Jump to content
Vodia PBX forum

All Activity

This stream auto-updates     

  1. Past hour
  2. Well I think it makes sense to take a look at the SIP packets, maybe there is something weird going on there...
  3. It does not depend on the OS, it depends on the license. You can also use it on Raspberry Pi or Vodia IO if you like. Just get a hosted Demo key to try it out.
  4. Yeah, I had that page in the old version, but in the last version I installed, not. Maybe it's like you say, it's visible only on "cloud" version. So, if I install the linux debian (raspberry) version on some ip public linux server, is that still disabled? Or the only way to have that option is to have the Vodia Hosted version?
  5. You should see that - however this is available only for the hosted editions (on CPE is makes only limited sense):
  6. Hello, according to this doc https://doc.vodia.com/pnp_snom I should find the SNOM Redirection Server setting on Admin->Phone->Setting but I dont' see any parameter like that (I've the last version 63.0.1 Vodia mini PBX Debian (RPI3+)). Where I'm doing wrong?
  7. Today
  8. Initiate call back after hangup is "No" for the called extension in the tests and the calls are not made from a cellphone or POTS-phone, but from a registered extension.
  9. We also have a third party login option: https://doc.vodia.com/third_party
  10. WebSocket will not work for my case, I cannot work with it due to cross-origin protection.
  11. Are you looking for this? https://doc.vodia.com/websocket Hope this helps.
  12. Hello, I know since v61 there was added an API to retrieve an active list of domain calls, is there something for the versions below? The api I'm referring to is described in this topic, https://portal.vodia.com/pbxapi/calls_api The release note https://doc.vodia.com/releasenotes610 section API. Thanks in advance!
  13. Yesterday
  14. That puts the First + Last. Isn't there a way to separate them?
  15. We suppose what we have currently is "{display-name}". Does that help?
  16. When using paramenters to provission, there seems to be {account}: The account name of the current user. But what if you just want the first name or last name? Are there any parameters for those?
  17. Well there is a feature for calling back users in dom_ext2.htm - maybe this one is "Yes"? This one is supposed to be used for private cell phone users that don't want to pay for company calls from their cell phones...
  18. Last week
  19. I assume it's the mailbox, since there is no agent group configured, but mailbox doesn't explicitly offer callback as an option, and "offer camp on" is disabled. The sequence of events from the point of view of the caller seems to be like this: 1) caller places a call to the extension 2) Ring tones are generated . 3) "Something" (probably voicemail) at the PBX picks up and it immediately (before even playing a greeting) for unknown reasons adds the caller to the callback list. 4) The caller hangs up. From the callee's point of view, the phone rings, but when picking up, it's the PBX offering various options. Not sure what it is. (See the file rec_115_13.wav in the attached ZIP. I'm also attaching PCAP files captured on the PBX.) When this happens there is always two calls registered in the log, starting at the same time. A big question is if the callback list option can somehow be triggered before the mailbox has kicked in . It almost appears to be the case, because the mailbox really shouldn't have come into play here. (The callee account had a live registration generated by Counterpath, and the callee picked up well before the call should have landed in voicemail.) weird call with stretto.zip
  20. Hi, Community if you happend to miss the Zoiper Webinar you can find it here, also visit us at https://blog.vodia.com/zoiper_qr_code to learn more about QR code provisioning.
  21. Whow interesting. The ACD callback list? Or the mailbox (you can call back if someone leaves a VM)?
  22. Looks like I'm closer to pinning down what's going on... Seems like my test call generator, somehow, sometimes, manages to make some noise that is misinterpreted as the starcode that gets the call added to the callback list. I wonder, what are the conditions for this feature to be activated by a caller? Can it, for example, happen only when the caller reaches the mailbox, or is there some other situation when it can happen, such as when ringtones are being generated before the callee or voice mail has picked up? Can the feature be turned off?
  23. The phones also have their settings - e.g. you will have to re-provision Poly.com phones if you change that setting. You will see if you look at the SIP traces; the phone might send a 408 timeout or something like that. If you change the setting like this through the web interface (not sure if this still works in 63) you don't need to restart the service.
  24. I did this. http://pbxip/reg_status.htm?save=save&max_ring_duration=3600 , double checked that the pbx.xml got updated. Then restarted the service. But it still does not go past 120 seconds. Ringing a hunt group. First stage is an extension with 120 seconds, but it disconnects before going to the second stage. If I put 60 seconds per stage. It goes to both stages then disconnects.
  25. Can the ring time be increased past the maximum? The option is currently set to 180 seconds. This is the highest number. Can I somehow increase it to 3600? This is an older version 52 I was thinking to modify it directly in pbx.xml
  26. The setup is now the standard one where the client and the registration server alternate registrations, but potentially with some brief overlaps (option 0 below). Not sure this is what is causing problems since Vodia supports multiple registrations for the same account, and since most of the time, the handover appears to work fine. In any case, seems like you are suggesting that 2 would be more stable? /CW 0: Standard: Your VoIP service provider supports multiple registrations. In this mode, there may be short overlaps of registration where both the Push server and the Bria client are registered to the SIP server. 1: Single Device Emulation: Your VoIP service provider does not support multiple registrations. Bria and the Bria Push server must unregister before the other one can register. 2: Continuous: Your VoIP service provider support multiple registrations. The Bria Push server is always connected to the SIP server. Bria is only connected to the SIP server when Bria is in the foreground. When Bria is in the foreground, Bria ignores push notifications so you do not receive duplicates. 3: Single Device Takeover: Your VoIP service provider does not support multiple registrations. Bria and the Bria Push server take over registrations from each other without unregistering first.
  27. Hmmm good thinking. I'll have to read a bit more on lsof and linux internals. Will let you know
  28. Yea, looking at the registration history in the extension tab it would be expected that there is just one, stable registration with the push server. I wonder if that can be set up somehow.
  1. Load more activity
×
×
  • Create New...