Jump to content

OND

Members
  • Posts

    71
  • Joined

  • Last visited

Everything posted by OND

  1. Ok, I have the log on, here's what I get: [6] 8:00:26.465 1 more requests pending to push.vodia.net:443ⓘ [6] 8:00:26.466 2 more requests pending to push.vodia.net:443ⓘ [7] 8:00:26.534 https:speech.googleapis.com:443: DNS A returned 172.217.5.202ⓘ [7] 8:00:26.534 https:speech.googleapis.com:443: Connect to 172.217.5.202ⓘ [7] 8:00:26.570 https:speech.googleapis.com:443: TCP disconnectⓘ [7] 8:00:26.570 https:speech.googleapis.com:443: Return code 500ⓘ [7] 8:00:26.570 Transscript for 9s failed with code 500ⓘ [7] 8:00:26.571 Closing connection https:speech.googleapis.com:443ⓘ [7] 8:00:26.571 https:push.vodia.net:443: DNS A returned 54.175.147.78ⓘ [7] 8:00:26.571 https:push.vodia.net:443: Connect to 54.175.147.78ⓘ [5] 8:00:26.571 Last message repeated 2 timesⓘ [7] 8:00:26.571 https:license.vodia.com:443: DNS A returned 54.175.147.78ⓘ [7] 8:00:26.571 Last message repeated 2 timesⓘ [7] 8:00:26.571 https:license.vodia.com:443: Connect to 54.175.147.78ⓘ [7] 8:00:26.879 https:push.vodia.net:443: Return code 200ⓘ Which part is the URI?
  2. So here's how I have it setup on my Google Console
  3. I just tried it again and here's what came up in the log: [6] 15:10:08.208 1 more requests pending to push.vodia.net:443ⓘ [6] 15:10:08.208 2 more requests pending to push.vodia.net:443ⓘ [7] 15:10:08.252 https:speech.googleapis.com:443: DNS A returned 172.217.14.106ⓘ [7] 15:10:08.252 https:speech.googleapis.com:443: Connect to 172.217.14.106ⓘ [7] 15:10:08.288 https:push.vodia.net:443: DNS A returned 54.175.147.78ⓘ [7] 15:10:08.288 https:push.vodia.net:443: Connect to 54.175.147.78ⓘ [7] 15:10:08.288 https:speech.googleapis.com:443: TCP disconnectⓘ [7] 15:10:08.288 https:speech.googleapis.com:443: Return code 500ⓘ [7] 15:10:08.288 Transscript for 7s failed with code 500ⓘ [7] 15:10:08.288 Closing connection https:speech.googleapis.com:443ⓘ [5] 15:10:08.289 Last message repeated 2 timesⓘ [7] 15:10:08.289 https:license.vodia.com:443: DNS A returned 54.175.147.78ⓘ [7] 15:10:08.289 Last message repeated 2 timesⓘ [7] 15:10:08.289 https:license.vodia.com:443: Connect to 54.175.147.78ⓘ [7] 15:10:08.629 Last message repeated 2 timesⓘ [7] 15:10:08.629 https:license.vodia.com:443: Return code 200ⓘ Date: Wed, 21 Oct 2020 22:10:08 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 7632 Content-Type: audio/mpeg [7] 15:10:08.646 https:push.vodia.net:443: Return code 200ⓘ Date: Wed, 21 Oct 2020 22:10:08 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 5 Content-Type: application/json [7] 15:10:08.766 https:push.vodia.net:443: Return code 200ⓘ Date: Wed, 21 Oct 2020 22:10:08 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 4 Content-Type: application/json [7] 15:10:08.833 https:push.vodia.net:443: Return code 200ⓘ Date: Wed, 21 Oct 2020 22:10:08 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 5 Content-Type: application/json [7] 15:10:09.324 https:api.ipify.org:443: DNS A returned 54.235.182.194ⓘ [7] 15:10:09.324 https:api.ipify.org:443: Connect to 54.235.182.194ⓘ [7] 15:10:09.665 https:api.ipify.org:443: Return code 200ⓘ Server: Cowboy Connection: keep-alive Content-Type: application/json Vary: Origin Date: Wed, 21 Oct 2020 22:10:09 GMT Content-Length: 21 Via: 1.1 vegur [7] 15:10:23.654 Closing connection https:license.vodia.com:443ⓘ [7] 15:10:23.912 Closing connection https:push.vodia.net:443ⓘ [7] 15:10:24.292 https:api.ipify.org:443: DNS A returned 54.235.182.194ⓘ [7] 15:10:24.292 https:api.ipify.org:443: Connect to 54.235.182.194ⓘ [7] 15:10:24.707 https:api.ipify.org:443: Return code 200ⓘ Server: Cowboy Connection: keep-alive Content-Type: application/json Vary: Origin Date: Wed, 21 Oct 2020 22:10:24 GMT Content-Length: 21 Via: 1.1 vegur
  4. I still haven't been able to get this working, any other suggestions?
  5. I finally got around to trying this again and was able to change the folder name to "certificates2". I restarted the server and all of the sudden I could no longer login to the PBX using my admin credentials. I instead was able to get in with the default credentials, but then the interface looked completely off, and none of my domains were showing up, and nothing in the portal in general was working correctly. I was however still able to make and receive calls. I logged back into the server via SSH and was that the system had created a new "certificates" folder. I ended up deleting it and renaming the "certificates2" folder back to "certificates", rebooted, and everything came back up as normal. I an still however not getting transcripts of messages. I check the logfile and still see this in the the log: [7] 22:57:47.310 https:speech.googleapis.com:443: DNS A returned 172.217.5.74ⓘ [7] 22:57:47.310 https:speech.googleapis.com:443: Connect to 172.217.5.74ⓘ [7] 22:57:47.310 Closing connection smtp.gmail.comⓘ [7] 22:57:47.345 Last message repeated 2 timesⓘ [4] 22:57:47.345 Unknown hash algorithm 2A864886F70D01010Bⓘ [5] 22:57:47.345 HTTP 172.217.5.74: Certificate for speech.googleapis.com could not be verifiedⓘ [7] 22:57:47.345 Closing connection smtp.gmail.comⓘ [7] 22:57:47.346 https:speech.googleapis.com:443: TCP disconnectⓘ [7] 22:57:47.346 https:speech.googleapis.com:443: Return code 500ⓘ [7] 22:57:47.346 Transscript for 6s failed with code 500ⓘ [7] 22:57:47.346 Closing connection https:speech.googleapis.com:443ⓘ Any other suggestions? Did I do something wrong?
  6. I tried renaming the folder, but it won't let me. I keep getting a "permission denied" message. Do I maybe need to shut down the server first?
  7. Hello. I have a customer with a Yealink T58V, and for some reason when users try to intercom him, it fails most of the time. They usually need to try 3-5 times before it finally goes through. I was thinking that maybe the phone was going to sleep and wasn't receiving pages while in sleep mode, but that didn't seem to help. Any ideas why this might be happening? The rest of the office has T46S and T27G phones and work fine. Any help would be greatly appreciated. I am using the Vodia multi-tenant hosted PBX running version 66.0.2
  8. Got it. I'll let you know what happens. Thanks again!
  9. Ok, I will try that tonight after business hours. Do you happen to know the directory or where that folder would be located? My PBX is hosted and I'm not super well versed on Linux, but I'm pretty sure I can figure it out if I know where to look.
  10. Thank you for your reply! I reset the certificates but still nothing. I noticed it says: [5] 21:48:54.958 HTTP 216.58.193.202: Certificate for speech.googleapis.com could not be verifiedⓘ Should speech.googleapis.com be in my list of certificates? It's not currently in there. If it should be, how would I go about adding it?
  11. I just tried again and pulled a logfile from the Administrator level this time and got this: [7] 21:48:54.943 https:speech.googleapis.com:443: DNS A returned 216.58.193.202ⓘ [7] 21:48:54.943 https:speech.googleapis.com:443: Connect to 216.58.193.202ⓘ [7] 21:48:54.943 Closing connection smtp.gmail.comⓘ [7] 21:48:54.958 Last message repeated 2 timesⓘ [4] 21:48:54.958 Unknown hash algorithm 2A864886F70D01010Bⓘ [5] 21:48:54.958 HTTP 216.58.193.202: Certificate for speech.googleapis.com could not be verifiedⓘ [7] 21:48:54.958 Closing connection smtp.gmail.comⓘ [7] 21:48:54.958 https:speech.googleapis.com:443: TCP disconnectⓘ [7] 21:48:54.958 https:speech.googleapis.com:443: Return code 500ⓘ [7] 21:48:54.958 Transscript for 12s failed with code 500ⓘ [7] 21:48:54.959 Closing connection https:speech.googleapis.com:443ⓘ [7] 21:48:54.959 Closing connection smtp.gmail.comⓘ There must be something I'm missing. Any help would be greatly appreciated
  12. Hello. I am trying to get my voicemail transcription via Google speech-to-text API working, but haven't been able to get it going. Documentation on this pretty limited, but I followed the instructions on this page: https://doc.vodia.com/voicemail_transcription I have Voicemail to text API enabled in the domain settings and have tried leaving some test messages to see if I get an email with the transcribed message, but I do not. I just get an email with a recording of the message attached. When I check the logfile of the test call, this is what I get: [7] 13:50:47.778 APP: No authentication of call because call comes from trunk [6] 13:50:47.779 MEDI: Port 67: Sending RTP to 67.231.9.93:45614, codec not set yet [5] 13:50:47.780 APP: Port 67: Incoming call in domain bws on port 67 trunk Bandwidth 2 (9) [5] 13:50:47.780 APP: Call 21: New call created with Call-ID 67 [4] 13:50:47.780 APP: Dial number +17029960700 [4] 13:50:47.780 APP: Dial number 801 from user 600 and dial plan Default [7] 13:50:47.781 MEDI: Port 67: Set codec preference count 5 [6] 13:50:47.781 MEDI: Port 67: Choose codec PCMU/8000 [7] 13:50:47.781 SIP: Use codec PCMU/8000 for call-leg 67 [7] 13:50:53.406 MEDI: Port 67: Received RFC4733 DTMF on codec 101 [6] 13:50:53.406 APP: Received DTMF 1, call type attendant [4] 13:50:53.406 APP: Dial number 8201 from user 801 and dial plan Default [5] 13:51:25.420 APP: MWI state 5/2 (0/0) on user 201@qts changed [5] 13:51:25.421 APP: Nothing changed in the MWI state 5/2 (0/0) on user 201@bws [5] 13:51:25.585 APP: Last message repeated 2 times [7] 13:51:25.585 WEBC: https:license.vodia.com:443: DNS A returned 54.175.147.78 [7] 13:51:25.585 WEBC: https:license.vodia.com:443: Connect to 54.175.147.78 [7] 13:51:26.079 WEBC: https:license.vodia.com:443: Return code 200 Date: Sun, 27 Sep 2020 20:51:25 GMT Server: Apache/2.4.29 (Ubuntu) Transfer-Encoding: chunked Content-Type: audio/mpeg [6] 13:51:26.080 APP: Wrote 17496 bytes for to recordings/msg33204.mp3 [7] 13:51:26.084 EMAI: smtp.office365.com:587: Start sending to <daniel@vrxrus.com> [7] 13:51:26.117 EMAI: smtp.office365.com:587: DNS A returned 52.96.70.130 [7] 13:51:26.117 EMAI: smtp.office365.com:587: Connect to 52.96.70.130:587 [7] 13:51:26.127 EMAI: smtp.office365.com:587: Connected [7] 13:51:27.412 EMAI: Sent email to <daniel@vrxrus.com> I may be wrong, but I would expect to see the server attempt the transcription somewhere in the logfile, probably starting with a WEBC, but there is nothing. Is there somewhere else in the system programming that I need to enable the speech-to-text API? Any help would be greatly appreciated! I am running Vodia multi-tenant hosted PBX version 66.0.2 (Debian 64), hosted on Google Cloud Platform
  13. Got it. That worked like a champ! Anonymous calls are now coming through. Thank you for your help!
  14. Hello, I have a cloud based Vodia PBX and when calls come in that have no caller ID information, the calls do not come through. Is there a way to allow them to come through and be routed as other incoming calls do? Thank you for your help!
  15. Sorry, just realized I never came back to this topic. After the server update to 65.0.10, the app works great. Thank you for your help!
  16. Ok, I will try that today after hours and let you know what happens. Thanks again for your help!
  17. Yes, we are using version 1.4 of the app, and are on version 65.0 of the PBX. Is 65.0.10 a more recent version? should I upgrade to that version?
  18. Ok, so from the app I am able to see the other extensions and their status, so it can definitely talk to the PBX. I can also call out with no issue. The only issue is when the iPhone has been idle for a minute or so (screen off in the users pocket for example) and a call comes in. The iPhone will ring, and you can answer the call and talk for about 10-15 seconds and everything seems fine, but then the call drops. If you have the Vodia app open already and a call comes in, you can pickup the call and it works fine. It will not drop. Also, every time the iPhone is idle and receives a call through the Vodia app, I get an email from the server saying this: "Source address for sip:2715@max-solutions has changed from tls:72.19.182.161:62865 to tls:72.19.182.161:62869" Any idea what may be happening? Is anybody else having this same issue? I'm only having issues with the iPhone version of the app which unfortunately is what most of my customers have. Users with Android phones are not having issues with the app.
  19. Thank you for your help. I got everything work well now! I just wanted to come back and post what I found in case anybody else should run into a similar issue. My customer wanted for calls to not only show the company name that the caller called, but also ring on specific buttons on the phones which is why I decided to go with the multiple identity setup. I found that the way the identities line up on a particular phone is based on the extension numbers, and not necessarily what I feel is its "Default" identity. The lowest extension number is identity 1, the next lowest extension number is identity 2 and so on. I also found that i had to set the maximum number of concurrent registrations to the number of phones that were registering to the company's extension, otherwise the system wasn't allowing more than 5 registrations, even if the value was left blank. Thanks again!
  20. Thank you for the reply! Hmm, ok. My PBX is in the cloud and has a direct public IP. Does that mean it should work?
×
×
  • Create New...