Jump to content
Vodia PBX forum

All Activity

This stream auto-updates     

  1. Last week
  2. The click2dial app for Open Xchange App Suite and Vodia is ready to use for MacOS - on all browsers!! Get it here https://software.muristan.org/OXcallingVodia/OXcallingVodia.zip Unzip the file and put the application in your application folder. Then open a web browser and insert: callto:set https://yourpbxaddress extensiondomain yournumber yourpassword When your browser asks if use OXcallingVodia click yes. Then click on a phone numer in Open Xchange App Suite. The link callto:+49123456789 will be handled by the app and passed to Vodia PBX. Have fun!
  3. Hi, Community I am sharing two links that may be useful for anyone that love and use the Cisco 3PPC series phone. Have a great and awesome weekend! Video on how to provision a Cisco 3PPC with VodiaPBX https://www.youtube.com/watch?v=LmMyALrh7VA Vodia documentation on Cisco 3PPC https://doc.vodia.com/cisco_3pcc_provisioning
  4. Hi, Community I am sharing two links that may be useful for anyone that love and use the Cisco 3PPC series phone. Have a great and awesome weekend! Video on how to provision a Cisco 3PPC with VodiaPBX https://www.youtube.com/watch?v=LmMyALrh7VA Vodia documentation on Cisco 3PPC https://doc.vodia.com/cisco_3pcc_provisioning
  5. Many Thanks! That would be very friendly and a help creating the WebExtension. Can you see my email address? Here is a quick and dirty Click2Dial solution for MacOS. But it works! 1. Create this shell script - insert your extension and passwort: #!/bin/sh L1=${#1} L2=$((L1-6)) PHONENUMBER=${1:7:L2} URL="https://pbx.domain.de:10443/remote_call.htm?user=09%40localhost&dest=$PHONENUMBER&auth=09%40localhost%3Asecret&connect=true" open $URL 2. Download the app Platypus and create the app OXcallingVodia.app selecting the above shell script. Store the app in application directory inside your home directory. 3. Download the app LinCastor and registrate the app OXcallingVodia.app with the default protocoll callto With more time you can edit Info.plist etc ... or write a webExtension
  6. Well we have a Chrome extension - no idea how much different that is from Firefox. We could share the code with you if you want to take a look.
  7. Open Xchange is a very common groupware that we use successfully in our facilities. The phone numbers of the contacts are displayed as clickable uri: callto:0815 It would be fantastic to have this Uri in the following format to make calls over a Vodia PBX: https://pbx:443/remote_call.htm?user=09%40localhost&dest=0815&auth=09%40localhost% 3Asecret&connect=true Unfortunately, it looks like this URI can not be changed in App Suite. So it needs a Firefox WebExtension. Is that already there? Otherwise, this could be developed with little effort. I would participate in the development costs if the code were released as open source.
  8. Hi, As of now, manual configuration is the only way to go as we don't provision it yet.
  9. Ah I see you added this as a feature ok thanks will test
  10. Hi Guys, I'm using Vodia 62.0. Is there a way I can provision Mitel 5360 phone. I know I can manually configure but I want auto provisioning. Please advise. Thank You
  11. Hi, We already have a button called as "record" on Snom phone ( worked on the model 725) which works too on this version http://portal.vodia.com/downloads/pbx/version-62.1.xml
  12. I'm trying to implement a live ACD web UI, and I ran into an issue. The program is on asp.net core 2. I'm using the documentations found here, https://doc.vodia.com/third_party https://doc.vodia.com/websocket According to the documentations above, I must first obtain the session ID and then open up a websocket connection. I try to obtain a session ID using information from third party documentation, but always receive a response 'false'. How can I debug this, or what could be wrong? A portion of my code, var url = string.Format("http://ipaddress/rest/system/session"); var encoded_url = HttpUtility.UrlEncode(url); var uri = new Uri(url); var base64_hash = Convert.ToBase64String(Encoding.ASCII.GetBytes(string.Format("{0}:{1}", "user", "password"))); var client = new RestClient(uri); var host_address = "myhost"; var response = ""; HttpWebRequest request = (HttpWebRequest)WebRequest.Create(uri); request.Method = "post"; request.Host = host_address; request.Accept = "*/*"; request.ContentType = "application/json"; request.Headers.Add("Authorization", string.Format("Basic {0}", base64_hash)); request.Headers.Add("DNT", "1"); request.Headers.Add("Origin", string.Format("http://{0}", host_address)); using (var streamWriter = new StreamWriter(request.GetRequestStream())) { string json = "{\"name\":\"3rd\"," + "\"username\":\"user\"," + "\"domain\":\"domain\"}"; streamWriter.Write(json); streamWriter.Flush(); streamWriter.Close(); } using (HttpWebResponse resp = request.GetResponse() as HttpWebResponse) { var reader = new StreamReader(resp.GetResponseStream(), Encoding.UTF8); response = reader.ReadToEnd(); } So the idea is, I obtain the session ID on the backend and insert it into a cookie, and then fire up websocket connection via javascript to receive ACD updates. I can fetch other information like wallboard, domain users etc, so it doesn't look like a rights issue for my user.
  13. is there any update on implementing this feature? I have noticed that in the last update that the system no longer works with http://wiki.snom.com/Settings/fkey/starcode when the key is pressed I am seeing the below in logs. [4] 20190416114440: Dial number *94 from user 681 and dial plan Redacted [5] 20190416114440: *94 does not match any star code It does seem to work using http://wiki.snom.com/Settings/fkey/dtmf but this has the undesired effect of sending the DTMF tones when the button is pressed. I can provide full logs if required but this definitely worked in version 60.0 and possibly 61.0
  14. This will affect the ringing patterns for alot of our clients too. If the logic of this has changed, can we have another setting that functions as this one did previously please? Eg. Ring all extensions defined in this field simultaneously after (x) seconds.
  15. Thnx a lot! I got it work. Because I did first installation with Vodia 57 or so there was no trunk wizard in the past to chose Easybell. I removed the trunk and created the new one using the wizard. But I had to add hpai: {from} in the text mode because this parameter was not set. Now it's working
  16. Earlier
  17. When you set up the trunk, did you use the easybell drop down? That should contain all the headers the right way. The important part is this: hf: <sip:{trunk-account}@sip.easybell.de> hpai: {from} hru: {request-uri} ht: <{request-uri}> hpr: {if clip true}id{fi clip true}
  18. Easybell anwer: Wir haben Ihre Störungsmeldung geprüft. Die Ursache ist eine fehlerhafte Konfiguration Ihrer Telefonanlage. Die UPN (User Provided Number / gewünschte CLIP Rufnummer) wird derzeit im From-User Part des SIP-Invites übermittelt. In diesem Feld muss jedoch die NPN (Network Provided Number / Stammrufnummer) übermittelt werden, damit der Anruf richtig geroutet werden kann. Ihre Telefonanlage kann die gewünschte UPN in einem der folgenden vier Felder hinterlegen: - P-Asserted-Identity - P-Preferred-Identity - From-Display - Remote Party ID ***** I configured Vodia dom_trunk_edit.htm to use P-Asserted-Identity for CLIP number. Why is it not used??
  19. Hi, Looks like Maybe they changed some policy that we don't yet follow or something. We will still have to look into it.
  20. Here the complete configuration: #Trunk 2 aadr: analog: false ani_emergency: ani_regular: bcp: behind_nat: false cid_update: cobusy: 500 Line Unavailable code: codec_lock: true codecs: 18 9 0 8 codest: dial_extension: !49631343178([0-9]+)$!\1!u!00 dialplan: 1 dir: dis: false domain: 1 dtmf: false dtmf_mode: earlymedia: true expires: 3600 failover: never fraction: 128 from_source: pai from_user: glob: global: true hcv: hd: {rfc} hf: {from} hpai: {trunk} hppi: hpr: {if clip true}id{fi clip true} hrpi: hru: {request-uri} ht: {to} icid: ignore_18x_sdp: false interoffice: false minimum: 10 minor: 300 s name: Easybell outbound_proxy: sip:sip.easybell.de pcap: false prack: true prefix: 49631343178 redirect: false reg_account: 0049631343178 reg_display: Easybell reg_keep: reg_registrar: sip.easybell.de reg_user: 0049631343178 remote_party: 4963193183 request_timeout: require: rfcrtp: false ring180: false rtcpxr: false rtp_begin: 20000 rtp_end: 50000 send_email: sip_port: 5061 status: 200 OK tel: false trusted: true type: register use_epid: false use_history: false use_uuid: false user_defined_hdr: uuid: urn:uuid:c57c369e-3024-4a15-b3d1-c3703568d0a8 wrtc_dest_name: wrtc_dest_number:
  21. I have an Easybell-Trunk and Vodia Version: 62.0.3 To display the ANI ef the extensions I selected in the Easybell Trunk-configuration P-Asserted-Identity. In Vodia dom_ext.htm I gave a special ANI to the extension starting with 49631 (Coutry prefix and local prefix) In dom_trunk_edit.htm I selected: CLIP Standard/Anzeige von Nummern: P-Asserted-Identity but it doesn't work. I changed most other parameters without success. Any idea? Thanks Andreas
  22. Hello, Was there any update on this?
  23. I understand what you are saying, but what I am saying is this has changed in operation from previous versions. Which is effecting how my customer agent groups are working. Can you confirm if it's changed ? like i said previously all additional agents would ring when this stage was hit and thats the function I need back.
  24. We would love to remove that feature, but we tried a year ago and there were still people using it. We even tried to hide the field which resulted in another uproar... Taking things away that are used for years is not making friends! Anyway for new installations I would not recommend to use it any more.
  25. Well, is there a difference on that we should have for IOP (which is Rasperian) and a Raspberry Pi 3 Model B+? Originally we did not really change the SSH files, just patch them - however the problem was obviously that the OS upgrade wiped out SSH and now we had to write the complete file to get this working. Maybe we have to do this depending on the SSH version? IMHO it is a big deal, because IOP users should have shell access when they enable it from the GUI. Actually the script even restarts sshd, so it would not even require a reboot.
  26. The "additional agents" are just put on the list as if they had logged in. The typical case is to include additional resources, e.g. managers or sales personell when agents are not picking up calls. The algorithm to choose the next agent is then done as if they had logged in. Ehen using the "longest idle first" that would usually be a manager, so it might make more sense to choose the random logic. It does not really help to get the waiting lines shorter. Maybe we should have another setting that says if there are more than so-and-so many callers waiting include the following agents.
  1. Load more activity
  • Create New...