chrispopp

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

Ok, problem is that it doesnt seem to have a timeout. We had 4 hour calls just standing there... further problem is that these calls were toll free, and are quite costly. Seems to be an ongoing fraud issue.

This feature in the auto attendant, has a value of "Default". What is this default value? Also where would it be changed from?

Edit: found the answer.

I erased everything on the test machine and a fresh new install worked fine. Recovered a backup from 63.0.x (i dont remember) and it doesn't work. Maybe the update?

No redirections. Just checked. Are you testing on a Win64?

Exactly. I had it set to 20, and it seemed that it was close enough. But i used a stop watch and it's every 30 seconds.

My apologies, it doesn't seem to follow the ring durations. It's at exactly 30 seconds intervals. See attached screenshots. Here are some logs that look off: [8] 11:14:08.889 Hangup: Call 668 not foundⓘ [7] 11:14:08.889 lookup_index error: Call port index is 668ⓘ [8] 11:14:08.889 Last message repeated 3 timesⓘ [9] 11:14:08.889 Using outbound proxy sip:xx.xx.xxx.xxx:55714;transport=tls because of flow-labelⓘ [7] 11:14:08.889 47 callids pendingⓘ or [9] 11:13:32.800 Traffic from 163.172.207.104 ignored because of user-agentⓘ [9] 11:13:33.652 Resolve 121803: aaaa udp 110.111.111.111 49737ⓘ [9] 11:13:33.652 Resolve 121803: a udp 110.111.111.111 49737ⓘ [9] 11:13:33.652 Resolve 121803: udp 110.111.111.111 49737ⓘ [9] 11:13:34.662 Message repetition, packet droppedⓘ [9] 11:13:39.833 Last message repeated 2 timesⓘ [9] 11:13:39.833 Resolve 121806: udp 159.65.251.173 49789ⓘ [9] 11:13:41.326 Resolve 121808: aaaa udp 110.111.111.111 43083ⓘ [9] 11:13:41.326 Resolve 121808: a udp 110.111.111.111 43083ⓘ [9] 11:13:41.326 Resolve 121808: udp 110.111.111.111 43083ⓘ [9] 11:13:42.663 Message repetition, packet droppedⓘ [9] 11:13:46.674 Last message repeated 2 timesⓘ [7] 11:13:46.674 31 callids pendingⓘ [9] 11:13:46.674 Resolve 121809: aaaa udp 110.111.111.111 49737ⓘ [9] 11:13:46.674 Resolve 121809: a udp 110.111.111.111 49737ⓘ [9] 11:13:46.674 Resolve 121809: udp 110.111.111.111 49737ⓘ [9] 11:13:46.675 Resolve 121810: url sip:555@110.111.111.111:49737;line=eogked7iⓘ [9] 11:13:46.675 Resolve 121810: udp 110.111.111.111 49737ⓘ [9] 11:13:50.666 Message repetition, packet droppedⓘ [9] 11:13:54.948 Last message repeated 2 timesⓘ [9] 11:13:54.948 Resolve 121814: udp 159.65.251.173 29261ⓘ [8] 11:13:55.119 Last message repeated 8 timesⓘ [7] 11:13:55.119 Port 670: Clear last INVITEⓘ [5] 11:13:55.119 INVITE Response 408 Request Timeout: Terminate cc620b26@pbxⓘ [7] 11:13:55.119 lookup_index error: Call port index is 670ⓘ [8] 11:13:55.119 Hangup: Call 670 not foundⓘ [9] 11:13:55.120 Using outbound proxy sip:12.12.12.12:55714;transport=tls because of flow-labelⓘ [9] 11:13:55.120 Resolve 121816: url sip:555@110.111.111.111:49737;line=eogked7iⓘ [9] 11:13:55.120 Resolve 121816: udp 110.111.111.111 49737ⓘ [9] 11:13:55.121 Resolve 121818: url sip:555@110.111.111.111:49737;line=eogked7iⓘ [9] 11:13:55.121 Resolve 121818: udp 110.111.111.111 49737ⓘ [9] 11:13:55.121 Last message repeated 2 timesⓘ [7] 11:13:55.121 Port 672: Clear last INVITEⓘ [5] 11:13:55.121 INVITE Response 408 Request Timeout: Terminate 8ee95a84@pbxⓘ [7] 11:13:55.122 Port 673: Clear last INVITEⓘ [5] 11:13:55.122 INVITE Response 408 Request Timeout: Terminate be778a5a@pbxⓘ [7] 11:13:55.123 lookup_index error: Call port index is 672ⓘ [8] 11:13:55.123 Hangup: Call 672 not foundⓘ [9] 11:13:55.123 Using outbound proxy sip:159.65.251.173:49789;transport=udp because of flow-labelⓘ [9] 11:13:55.123 Resolve 121819: url sip:159.65.251.173:49789;transport=udpⓘ [9] 11:13:55.123 Resolve 121819: udp 159.65.251.173 49789ⓘ [5] 11:13:55.124 SIP Tx 159.65.251.173:49789:ⓘ

Did you let the phones ring over several ring durations? For example, let it ring 361 seconds in the above example, it will show 4 calls on my phones. I tried with a Snom and a Yealink. In the active calls lists it only shows 1... I checked that too.

We are testing on 64.0 and it seems there's something wrong with the agent group. The agent group now opens a new call after every call duration. For example. Say someone calls into the agent group, and the stage duration is 20 seconds. It will ring for 20 seconds, add a new agent, and then it will show up as 2 calls the phone. After another 20 seconds, 3 calls are active, 20 seconds later, 4 calls, and so on... When picking up, it doesn't do anything. You just need to pick up the latest call in order for it to hear the person. So you need to go through all, and hangup until you reach the last call. The Active Calls list shows 1 call only. Was working fine in the older versions. This example says 90 seconds, but I tried with 20 seconds.

Yes. Provisioning a new MAC...