Jump to content

Enzo Matrix

Members
  • Posts

    47
  • Joined

  • Last visited

1 Follower

About Enzo Matrix

  • Birthday December 19

Profile Information

  • Gender
    Male
  • Location
    Australia

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Enzo Matrix's Achievements

Newbie

Newbie (1/14)

  • One Year In Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done Rare

Recent Badges

0

Reputation

  1. Great to see that SMS is working again. I have also got Alpha numeric sender id's working too with Twilio which is good. My problem is that regardless of what I put in the Vodia SMS ANI field, it converts it all to lowercase. I know that the API for Twilio accepts any case, so is it possible to get this fixed? For example, in the ANI field it shows 'MyComp' but the actual api call is sending it as 'mycomp'.
  2. I am sure there is a solution for this, I just haven't found it. One of our directors, who doesn't want to put the Vodia App on his cell phone is in an Agent Group. When a call from the group gets to him, the call goes to his cell voicemail if it rings out, rather than continuing on to the next user in the group. Does anyone know how I can overcome this?
  3. Excellent, uninstalled and reinstalled and back to normal now. Thanks.
  4. Hi there, My Microsoft Store updated my Vodia app to version 3.6.0 and now it is having some issues. Here is a list of things that I have noticed: Profile button doesn't show information, avatar etc None of the buttons under the profile drop down work ACD only shows a single group I am sure there are more issues, but that's all I have found at the moment. Two screenshots - one showing the app, other showing the web interface Anyone else having these issues?
  5. Just want to point out that I don't specifically think this was now an issue with upgrading - I think Twilio may have changed their API.
  6. It appears that Twilio now requires me to have a 'Message Service' in programmable messaging to send. The Twilio API service now has 'messagingServiceSid' tag that seems to be required (which you get by creating a 'Messaging Service' under programmable messaging - here is the code from Twilio which I have tested and it works: // Update the path below to your autoload.php, // see https://getcomposer.org/doc/01-basic-usage.md require_once '/path/to/vendor/autoload.php'; use Twilio\Rest\Client; $sid = "TWILIO ACCOUNT API KEY HERE"; $token = "[AuthToken]"; $twilio = new Client($sid, $token); $message = $twilio->messages ->create("+PHONE_NUMBER_HERE", // to array( "messagingServiceSid" => "MESSAGING_SERVICE_SID_HERE", "body" => "This is a test" ) ); print($message->sid); What would be AMAZING would be if Vodia was updated to allow a seperate MessagingServiceID per domain! I have been able to test this using my own PHP code, and it would be a very simple way for Twilio users to be able to separate out their services for reporting. From what I can see (and I may be wrong): PBX Settings need: Twilio API Key and Twilio API Secret Domain Settings need: Twilio Messaging Service ID When sending the SMS request to Twilio, Vodia pulls the API information from the PBX, and the service id from the domain - in Twilio, all the SMS's sent are seperated into their service IDs, allowing for me to charge for them accordingly.
  7. Hi all, Is anyone else having issues with Twilio SMS after upgrading to 67.0.2? We could all use it fine prior to the upgrade, but now nothing is being sent, and there is nothing hitting the Twilio API. Is there somewhere I can debug this in logs or something in Vodia? Thanks.
  8. Thanks! One main problem is that it is too easy to close the Vodia app on windows.
  9. Thanks for the response, So would I be better creating a generic logo for the PBX, rather than using our companies logo?
×
×
  • Create New...