Jump to content

OND

Members
  • Posts

    71
  • Joined

  • Last visited

Everything posted by OND

  1. I just updated the app and it's good to go now. Thank you everybody!
  2. Forgot to mention the Vodia Windows app is version 6.0.2.0. Thanks again!
  3. Hello all. I've run into an issue that when customers install the Vodia app for Windows on their PCs, if the app Notifications are turned on, calls to the extension got to VM after 2 rings. If we turn Notifications off, the calls follow the usual no answer timer for VM which is 20 seconds on our system. I've tested this on serveral PCs, Windows 10 and Windows 11, and it does the same thing either way. For now, the customer has turned notifications off, but they need to make sure they are listening for the audible ringing from the app because they don't receive the pop-up. This is an issue for them because they use USB headsets, and they don't always have their headsets on, so they end up missing calls, but the 2 rings is not enough time for them to answer calls when the Notifications are turned on. Has anyone else run into this issue? We are running Vodia Multi-Tenant 68.0.32, hosted on Google. Thanks everybody!
  4. Looks like it was an issue on QuestBlue's end. We're good to go now
  5. Hello. Thank you for your response! I tried going Vodia app to Vodia app and the emojis still don't come through. The thumbs up emoji comes through as "í½±". But going out from the Vodia app to a regular cell phone (iPhone or Android), the emojis go through fine. They just can't come into the Vodia app (smart phone app or softphone). We are using QuestBlue as our carrier. Any suggestions?
  6. Hello. Yes, all persmissions are on, but still no notifications of incoming SMS messages
  7. I have noticed outbound emojis seem to work. It's inbound emojis that come through as a bunch of random letters, numbers and other characters. Thanks again!
  8. Hello all! A customer pointed out to me that the Vodia PBX doesn't seem to support emojis coming in through SMS on any of the apps. For example, if you try sending a thumbs-up emoji, it comes through as: í½±. Are there any plans to support emojis? Apparently this customer has several patients who text her with emojis. Vodia PBX Multi-Tenant hosted on Google Cloud, version 68.0.26
  9. OK, yes I see that after updating to the new version of the app. It seems to be behaving properly after the update. Hopefully this resolves the issues. I will report back here if it does not. Thank you!
  10. So this appears to be an app issue. The customer said that when their call center agents login to the queue through a web browser like Chrome, it works fine. But when they login through the Vodia PC app, calls only ring twice to an agent and then are sent back into the queue. Not sure why this would be
  11. Hello. I have a customer who is telling me that their call queue is ringing to few times and they are not having the opportunity to answer the call. They said it only rings twice and puts the call back into the queue. Which setting adjusts this? I tried setting adjusting the "Ring stage duration (secs)" setting under "Agent selection", but it didn't seem to make a difference. The call center agents are using the Vodia PC app which they donwloaded from the Microsoft store. Any help would be greatly appreciated. Thank you! Vodia Multi-Tenant Version 68.0.26 Hosted on Google
  12. Hello. I have a customer who does not get any kind of notification that he had recovered an incoming SMS message. If he goes into the app, he can see there are new messages, but he has no idea he has new messages without checking. Is there any way to fix this? He has Vodia version 5.0.4 on a Pixel 6 Pro running the latest firmware. Vodia PBX is hosted multi-tenant version 68.0.26 hosted on Google. Thank you!
  13. Hello. Ever since upgrading to version 68, my customer is no longer able to listen to calls through the web app. There used to be a little square in the top right corner of the "Call In Domain" window on the app that allowed us to expand that window and click on the "Listen" button to listen to calls, but that square is no longer there. Is there a different procedure for listening to calls through the web app now? Any help would be greatly appreciated. Thank you! PBX Version: Multi-Tenant, 68.0.16 Hosted on Google Cloud
  14. That was it. I was using the MAC address for authentication, but using the SIP password. I swapped out the SIP password for the MAC password on the VoIP phones page and it came right up. Thank you for your help!
  15. I've tried to copy the identity settings from a working D735 to the C520 as close as I can, but I still haven't been able to get it to register. Here are the settings from the working D735: Identity active: *on off Displayname: West Conference Room Account: 1110 Password: •••••••• Registrar: office-by-airport Outbound Proxy: sip:34.94.107.13:5060;transport=udp Failover Identity: None Hidden Identity: on *off Authentication Username: 000413BC4D6D Mailbox: *97 Mailbox Dial-in (if different from Mailbox): Conference Server: Display Text for Idle Screen: 1110: West Conference Room Display Number for Idle Screen: Display Text for Call Forwarding Target: Here are the settings from the C520: Enable Account: yes Account Label: 1110 Display Name: West Conference Room User Identifer: 1110 Authentication Name: 000413A02A75 Authentication Password: •••••••••••••• Dial Plan: x+P Inter-Digit Timeout (secs): 3 Maximum Number of Calls: 6 Page Auto Answer: Manual Feature Synchronization: Disable Line Type: Private DTMF Method: Auto Unregister After Reboot: Disable SIP Server Server Address: 34.94.107.13 Port: 5060 Registration Server Address: office-by-airport Port: 5060 Expiration (secs): 3600 Registration Freq (secs): 10 Outbound Proxy Server Address: 34.94.107.13 Port: 5060 Backup Outbound Proxy Server Address: Port: 5060 Audio Ringer Tone: 1 Codec Priority 1: G.711u Codec Priority 2: G.711a Codec Priority 3: G.729a/b Codec Priority 4: G.726 Codec Priority 5: G.722 Enable Voice Encryption (SRTP) Enable G.729 Annex B Preferred Packetization Time (ms): 20 Quality of Service DSCP (voice): 46 DSCP (signaling): 26 Signaling Settings Local SIP Port: 5060 Transport: UDP Feature Access Codes Paging: Call Park: Parked Call Retrieval: Voicemail: *97 DND ON: *78 DND OFF: *79 Call Forward All ON: Call Forward All OFF: Call Forward No Answer ON: Call Forward No Answer OFF: Call Forward Busy ON: Call Forward Busy OFF: Anonymous Call Reject ON: Anonymous Call Reject OFF: Anonymous Call ON: Anonymous Call OFF: Call Waiting ON: Call Waiting OFF: Group Call Pickup: Direct Call Pick Up: Voicemail Settings Enable MWI Subscription Mailbox ID: Expiration (secs): 3600 *Ignore Unsolicited MWI *Enable Stutter Dial Tone NAT Traversal Enable STUN Server Address: Port: 3478 *Enable UDP Keep-Alive Keep-Alive Interval (secs): 30 Music On Hold *Enable Local MoH Network Conference Enable Network Conference Conference URI: Session Timer Enable Session Timer Minimum Value (secs): 90 Maximum Value (secs): 1800 Is there anything that stands out as the reason why it may not be registering? Thanks again!
  16. Hello everyone. I was just wondering if anyone has ever setup a Snom C520 conference phone on the Vodia PBX. The GUI is totally different than other Snom phones and I haven't been able to get it going yet. Any help would be greatly appreciated. Thank you! I'm running Vodia Multi-Tenant PBX version 67.0.4 hosted on Google
  17. Also, I am using QuestBlue for my SIP trunks. I found a previous topic where the user switched the "Source for caller-ID information" to "From", but mine was already set that way. Thanks again!
  18. Hello all! For some reason on only one of the domains on my multi-tenant PBX, the customer is not getting Caller ID information on about 60% of their calls. I went down the General Domain settings and they match the other domains I have, and all the others are receiving DIC with no issues. Any ideas? Any help would be greatly appreciated! I'm running Vodia Multi-Tenant PBX version 67.0.4 hosted on Google
  19. Hello everyone. For some reason, when agents in one of my domains call out, the person they are calling is seeing the extension name instead of the company name in their caller ID. Obviously the customer doesn't want "John Doe" showing when they call out, they'd rather have "XYZ Company" show. The funny this is that it only seems to be doing this one one of the domains on my hosted multi-tenant PBX. Where is this setting? I am running Vodia hosted multi-tenant version 67.0.4 on Google Thank you!
  20. I was just able to check on this and yes, I have set the regular ANI rule field on the outgoing trunk to "from:orig-ani", and in the custom headers set "from" to "based on incoming call". I've been able to get this working on an IoP before, but never on my hosted PBX for some reason. Is there anything else you can suggest?
  21. Hello all. I have a customer who forwards all calls using the *80 feature code. When the calls ring on the phone they forward to, they see the CID of their office, but they would rather see the CID of the person who originally called in. Is there a way to set this up? I searched around on the forum and tried adjusting the SIP trunk settings going by a couple different topics I found, but I couldn't get it to work. I also tried having them use the Vodia app instead of forwarding the calls, but they kept saying it worked inconsistently, had audio issues, and that it didn't work when they were using a Bluetooth headset. Any help would be greatly appreciated. Thank you! I am running the Vodia Multi-Tenant PBX version 67.0.4 hosted on Google, and our provider is QuestBlue
  22. Ok, thank you. I made the changes there. Is there anyway to automatically export the call records for a particular domain once a week or so so that the data can be saved indefinitely? Or is there a 3rd party software that can do it?
  23. Hello. I was wondering how far back the Call Log should go? As of today (7/8/21), nothing shows in the call log before 7/2/21 for most of my domains, but there are a handful of domains that show some records on 7/1/21. Is it limited to a certain number of records system wide? Or does it just delete the records after a certain amount of time? In either case, is there a way to increase the numbers of records that it stores? Any help would be appreciated. Thank you! I am running the multi-tenant PBX version 67.0.4 hosted on Google
  24. Hello. I have a customer who was using the Vodia app on a Galaxy Tab A 2019 version, and they recently noticed that it started to look a little different from the version on their cell phones, so they asked me about it. I realized that the version on the tablet is 4.0.6, but the version on the bell phone is 4.0.13. I tried updating it but it says "This ago isn't compatible with your device anymore. Contact the developers for more info". What are the requirements for the app? Is there a certain Android OS version that the tablet must be running? I checked and the tablet says it's running version 10 and is up to date. The app still mostly works for now, but I'm assuming it's just a matter of time before it stops working. Any help would be appreciated. Thank you!
  25. After uploading the audio file to the server in the correct format and rebooting the phones, it is now playing the audio file. Thanks for your help!
×
×
  • Create New...