chrispopp

I see that some values work when i send them to the log server: {from} and {to}. Any other values I can pass?

Is the IVR node server documentation outdated? What about the PHP script in it? I simply cann't get the script to write the cdr file.

It is sending it, but with a null value. Wireshark and the log shows the same thing. 1. I dont understand why I need to specify To-based routing match list? The documentation mentions that only List of actions should be set it action:url. 2. The Connection timeout and Read timeout under the Action URL tab are completely ignored and the call is automatically redirected if the Destination RegEx (e.g. !([0-9]*)!\1): is set to something. 3. Well and the worst part, it is still null. Sorry I dont know what you mean by asking to send an Http packet?

Wireshark says Content Length: 0. Still null...

Yes, in the log there is no mention of anything going to the URL. I was able to use to-based routing to using a random value: !.*!60000!, and it sort of works. It ends up sending it to the action:url but, the call disconnects right away, and the value sent is "" (null).

I also tried entering action:url in the list of actions and same result.

I am following the IVR Node Server documentation here: https://doc.vodia.com/ivrnodes_ext_app I am unable to get vodia to send the Soap message. Am i missing something?

I tried importing a test domain from an old Vodia 57 domain to a new 64.1. It created incorrect extensions, even blank ones.I tried the same exported file from 57 and used the import feature on 62.0 and it worked. Exporting from 62.0 to 64.1 also did not work.

A lot of people have iOS and it doesn't necessarly apply to desktop users. Most users would login to their portals in a desktop environment.

Would be good to have two factor authentication via SMS or Authenticator. Either for admins or users. I think right now it has become a standard in the industry.

I was suprised the new version of Vodia does not support Twilio for messaging. Surprised because it seems that they pride themselves on having the easiest API to integrate... We use it, and it works really well.

It did work. Strange. Thanks a lot!

I tried my own SMTP server over port 25 and the same result. The emails would be sent around midnight.

I tried TLS too. And also automatic. The settings worked fine on 64.0.2. Also, it does eventually send it. So I don't think it's a problem with the settings.

Testing on a 64.1 version, and it seems something broke the emails from gouing out. The emails for voicemails are only sent at midnight. I checked my test server and a gmail account. All the emails are under pending in the email setup. When I look into the logs it says that they are Scheduled for sending. [7] 15:06:22.694 smtp.gmail.com:587: Scheduling email to <email@eeee.com> [7] 15:06:22.694 smtp.gmail.com:587: Start sending to <email@eeee.com> [7] 15:06:22.695 smtp.gmail.com:587: DNS A returned 222.222.222.222 [7] 15:06:22.695 smtp.gmail.com:587: Connect to 222.222.222.222:587 [7] 15:06:22.722 smtp.gmail.com:587: Connected [9] 15:06:22.751 Received 54 SMTP bytes [8] 15:06:22.752 Received SMTP traffic 220 smtp.gmail.com ESMTP [8] 15:06:22.752 Send SMTP traffic EHLO localhost [9] 15:06:22.783 Received 167 SMTP bytes [8] 15:06:22.783 Received SMTP traffic 250-smtp.gmail.com at your service 250-SIZE 250-8BITMIME 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-PIPELINING 250-CHUNKING 250 SMTPUTF8 [8] 15:06:22.783 Send SMTP traffic STARTTLS