jvoiptel

I think their SMS needs to be revamped before even tackling group SMS. If you take a look at how group SMS messages are delivered in a JSON payload, it's actually treated as MMS. There are also many strange things reported in this forum about the way SMS works in general. An then there's the mobile apps...

Can you share more details on these new push servers for a new Android app? We are having issues with existing Android version and push - but with our customers in South America. It appears that there are latency issues with existing push. Also, I noticed that push-na.vodia.net and push-sa.vodia.net are pointing to the same IP in Ashburn, VA. Are there any plans locating a push server in SA?

I see it with my V69.1.4, although Vodia version history says its available with V69.2 and blog post says V69.1.3 and above... I'm pretty sure you can get multiple providers to work on a single tenant. But I wonder if you'll get group SMS to work.. I don't think that's supported yet..

What error are you getting? What happens when you reset the password? Did you upgrade from v68? Versions after 69+ now use passkey authentication.

Hello, Currently, you can view call history from the following methods: Admin portal Call Log page (system or domain level) Export CDRs to CSV method. You can invoke RESTful methods to ../rest/domain/domain_name/cdrs However, what I do not see are any methods (UX or REST) to view and/or export SMS message delivery reports. It appears Vodia PBX calls this chats. Message delivery is handled by the extension/account. You can report on call history, but not chat history. In an effort to diagnose SMS delivery issues, it would be very helpful to have chat-logs (MDRs) available through any means. This level of reporting would also be helpful for cost-reporting purposes. Interested in hearing your thoughts, thanks!

Thanks Vernon for catching this! I change the Mailbox setting to FAX under mailbox enabled tab and tested again. This time, the call did not disconnect and a 50-page document delivered just fine in about 43 minutes. I appreciate the help. The "maibox enabled" is confusing because you would think it's 0 or 1, not 0,1 and FAX I would put FAX under Extension Feature Set. I think we're good here now. Thanks again.

I would check out this Vodia doc for helpful tips: https://doc.vodia.com/docs/one-way-audio-1 Try narrowing it down. Is it random with any originating caller or same one? Can you obtain SIP traces with your carrier? Try enabling PCAP tracing as suggested although it will be difficult without being able to reproduce it.

Thank you for releasing this beta. But we're on 68.0.32 and much prefer staying on v68x for other reasons. If you guys decide to also improve v68's faxing, please let me know.

I don't see that as an option for mailbox type. We set it as Mailbox Only

Hello, I'm having an issue with large inbound faxes. When there are many pages (10 or more) and the inbound fax call is more than 5 minutes, the call is disconnected. Build: 68.0.32 The extension type is set to mailbox only. Voicemail call duration is set to unlimited under domain settings. Taking a look at the logs, I found this: These are the duration timing logs - notice after 5min: The PBX is disconnecting the call. Is there a timeout setting we're missing? Thank you.

I had the same issue. The mobile apps are quite simplistic and lack business-grade features. The only solution I found was to create a conference room account, set it as ad-hoc, and then blind-transfer your caller to that account. Then, you can into the conference yourself, and you're all tied in. Not the most elegant unfortunately.

Of course, that makes sense! Alright, so adding that extra layer for service-flag checking against a local address book is the solution! If it doesn't match the condition, it flows to final stage which is the Auto-Attendant account. I got it, thanks for your help!

Yes, incoming number is always the same, and call-from number is always the same. I do like your solution - I didn't realize the address book option exists. Problem is that the incoming number routes to an auto-attendant account before flowing to a ring group. I was hoping I can program the inbound flow to catch the call-from number and route it to a dedicated ring group. Not sure I can do that unless we get a dedicated DID for this solution. This gives me something to work with. Thanks!

You image is quite clear- there are messages, but not when you open it. I've seen the same issue with this version. Can you see the messages with the mobile app?

Thanks. Actually, we do not own the DID because we're trying to route based on originating number. Basically, we're looking to do this: <originating external caller--From_10DLC--To-inbound--DID_terminating-->SIPTrunk-->PBX--Domain--<Ringroup>. We have the terminating DID set in DID Management, but we do not own the originating 10DLC number.

Hello, Wondering if this is possible. I have a SIP trunk that does better with outbound faxes. I'd like to route outbound faxes through a particular trunk based on the Dialplan. I would not know the destination DID, but originating ANI. Is this possible? Thank you!

Hello, I just noticed this. Documentation links from our admin pages are broken. It seems you moved to a different platform, but the links from the portal are broken. For example, go to a tenant's extension page, and clicking on the ? or following link gives 404 Not_Found error: 404: NOT_FOUND (vodia.com)

That's wonderful! Thanks for letting us know. Our users will greatly appreciate that.

Did you ever get this to work with dm.server.address = us-device-scheduler.ymcs.yealink.com ? I understand Yealink is going to ultimately migrate all customers to this new endpoint.

Ok, thank you. Then, how do you recommend migrating tenants from one server to another when the migration scenario is from v68 to v69? Is SMS Management the only data that is stored differently. It appears the import works just fine aside from SMS settings. Also, if it's not recommended, it may be good to include a warning or failure. I appreciate your suggestions.

Hello, I'm interested in knowing how to do special call-flow routing based on source DID such as 10DLC. I have a global trunk, where I want to apply a special condition and route to a specific domain's ring-group account. Is this possible? If so how? Or do I need a dedicated SIP Trunk for the domain? I see there are trunk settings settings: Destination for incoming calls - Routing/Redirection - "Use a list of expression" option. Is this where I need to make the change? If so, and if the trunk is global, how can I specify a domain account? What would happen if condition does not match, does it revert to default routing? Thanks for your help.

We have the same need. Vodia PBX does not offer SMS-to-Email feature. We designed a third-party solution for this where all inbound SMS messages are sent to Zapier, email notification is triggered, then SMS message is forwarded to Vodia. Our solution works great, except for MMS. Still working on that...But sure would be nice to have this integrated into Vodia.

Hello, Just noticing the following when migrating a v68 tenant to v69 by using the file backup method. If the tenant has SMS settings (Set in domain) enabled, the SMS settings are not migrated to the new tenants SMS Management page under Trunks. Not sure if this was by design, but you might want to test it. My expectation was to see the domains SMS settings under SMS Management under Providers when migrated using file backup method: Target migrated domain has empty providers:

Do you mean governmental policy? Not sure I understand. The data owners have the right to delete their data. The data owners are asking to delete their chats, but the iOS app has been designed to prevent chat messages from being deleted.

We're interested in testing WhatsApp messaging soon. I noticed it was officially released with v69.0.6, with documentation to follow but I can't seem to find any documentation yet. Also, in checking v69.1.4, with the release of SMS Management, I don't see WhatsApp as a dropdown. It's only available at the system level. So, I'm guessing it's not treated as SMS for obvious reasons, but I do think it may deserve a place at the tenant level too. Thank you.