There is actually a way to get the extension number based on DID but it’s a really long database query, see below.
mysql -u root -D ombutel -s -N -e "select ext.extension from ombu_extensions ext left join ombu_destinations dest on (dest.index = ext.extension_id) left join ombu_inbound_routes ir on (ir.destination_id = dest.id) left join ombu_destinations_category destcrid on (destcrid.id = dest.category_id) left join ombu_modules module on (destcrid.module_id = module.module_id ) where ir.did = '${var_containing_did}' and module.name = 'extensions';"
I have not tested this from within a dialplan, so I’m not sure if you’ll be able to use root or you’ll have to create a new user and password with access to the ombutel database.
Any update on MMS specifically being supported by Vital Connect? Or at least with other softphone apps such as GroundWire by Acrobits etc.? We really need to be able to compete with other companies who are offering softphone solutions with Rich Messaging/MMS and not just offer plain text SMS to them. We’ll accept a workaround as well, if you’ve got one to offer.
I would also like to suggest adding the possibility to manually configure a custom SMS provider, not just rely on pre-integrated ones.
For example, using platforms like smswapi.com allows for much cheaper and more flexible SMS/WhatsApp messaging, which is especially useful for resellers and companies managing costs across multiple tenants.
Having an interface to input API details (e.g. endpoint, headers, token, callback URL) would make the SMS/MMS feature significantly more extensible, without relying on fixed providers.
I got this working by using the sms api from my trunk provider and then setting it up in VitalPBX with the Custom Provider option. It took a bit of trial and error with the URL and parameters, but once that was sorted, messages started flowing fine. Just make sure your sms api supports both sending and receiving if you’re planning on full two-way SMS inside VitXi.