Jump to content

OND

Members
  • Posts

    71
  • Joined

  • Last visited

Everything posted by OND

  1. So I did the upgrade to 67.0.4 over the weekend and inbound SMS was still not working. I did notice that under Event Notifications in the system level of the administrator programming, "Text messaging enabled for domains by default" was turned off. I tried turning it on and incoming SMS started work again. Not sure if this is something that turned off by default when I upgraded to version 67, but this seems to have been the issue. Also, in the Edit Domain section, "Enable text messaging" was set to on, but incoming SMS still did not work until "Text messaging enabled for domains by default" was turned on in the Event Notifications section. Seems like it should have, but either way, I'm glad it's working now. Thanks for your help!
  2. Got it. I'll do this over the weekend so I can give my customers a heads up that we will be doing some maintenance on our server and will let you know what happens on Monday. Thank you!
  3. Ok, thank you, I'll look into that. Also, in what format should the audio files be? I have looked through the documentation and haven't been able to find that info. I know it should be a wave and mono, just not sure about the Hz (I assume 8000Hz), and if there are any other details I need to adjust.
  4. Hello. I have a customer with Polycom VVX411 phones. Once I set them up on the Vodia PBX, it replaced the original Polycom "low trill" ringtone with one that I believe is provided by the Vodia PBX. I have incoming calls go to a Hunt Group, so I tried setting the "Ring Melody" within the Hunt Group settings to all of the different options, and none of them are the default Polycom ringtone. I even tried deleting all of the custom ringtones which I assume were uploaded to the phone by the PBX while provisioning, and while that did make it use one of the Polycom notification tones as the ringtone, it still won't play the default ringtone. I also tried uploading the default ringtone as a custom ringtone directly to the phone itself, and I named it Alert1.wav which is how the PBX named the custom ringtone, but still no luck. Any idea how I can get the Polycoms to use the default ringtone? My customer reeeeally wants the old ringtone back. Any help would be greatly appreciated. Thank you! I'm using Vodia Multi-Tenant version 67.0.2 hosted on Google
  5. Ok, will do. Do I need to take a backup of each individual domain, or is there a way to do a backup of the entire system in one shot?
  6. Ok, do you suggest I upgrade to 67.0.4? Will that possibly fix the issue? I checked the settings in my Bandwidth account and everything seemed fine. And as I mentioned before, it was when I upgraded to version 67 that incoming SMS stopped working
  7. Hello all. Ever since I have upgraded my server to version 67, my inbound SMS service through Bandwidth no longer works. Outbound however works fine. It worked fine on version 66, and I haven't changed anything since then. In the logfile, it appears that the server is receiving the SMS message, but it's just not getting to the user from there. Here is what I see in the log file: [9] 22:03:28.554 Accept connection 105 from 52.72.24.132ⓘ [9] 22:03:28.554 Request /recvsmsⓘ POST /recvsms HTTP/1.1 Content-Length: 387 Host: 34.104.250.13 Connection: Keep-Alive Accept-Encoding: gzip User-Agent: bandwidth-api Content-Type: application/json; charset=utf-8 [8] 22:03:28.555 Receive SMSⓘ [{"time":"2021-05-05T05:03:28.348Z","type":"message-received","to":"+17255272653","description":"Incoming message received","message":{"id":"1240cc61-df96-44e9-a080-14232fbbeb26","owner":"+17255272653","applicationId":"cfa624ce-3f08-4624-b2d6-6bcf440x8x6x","time":"2021-05-05T05:03:28.225Z","segmentCount":1,"direction":"in","to":["+17255270000"],"from":"+17023253383","text":"Got it"}}] [6] 22:03:28.764 Delete HTTP connection 105 from 52.72.24.132:8285ⓘ I read over a similar topic where someone had the same issue using Telnyx service, but it didn't help me figure out my issue. Any help would be greatly appreciated. Thank you! I am running Vodia Multi-Tenant version 67.0.2 hosted on Google.
  8. Hello all. I have a customer who asked me to have parked calls ring back to the person who originally parked it after a given amount of time. I went into the domain settings and set the "Park Reminder" to 2 minutes, and the calls do ring back after 2 minutes like the customer asked. The problem is that when they do ring, back they'd like some sort of indicator that the call that is ringing is a call that had been parked for 2 minutes. Right now, they just appear as though they are new incoming calls, and so the agents just answer them in that way which sometimes irritates the callers and they say something like "I've already been holding!" Is there a way to change this so the agents know a ringing call is one that is ringing back because of the "Park Reminder" feature? Any help would be greatly appreciated. Thank you! I'm running Vodia Multi-Tenant PBX hosted on Google, version 67.0.1
  9. Very cool. Can't wait to try it out!
  10. Hello all! I have inbound fax to email setup for several of my customers but was wondering if there is any way to send outgoing faxes from email using the Vodia PBX? Several of my customers have asked for this service. Up until now we have used several ATAs (Cisco & Grandstream) for outbound faxing using cutomers' traditional fax machines with mixed results, but none have been what I would call reliable. Inbound faxing through the Vodia PBX however has worked great, so I'd love to be able to use it for outbound faxing as well. Let me know if anybody out there has set this up, or what you have found is the best solution for outbound faxing using the Vodia PBX. Thank you! I'm on Vodia Multi-Tenant 66.0.6 hosted on Google's Cloud.
  11. Sorry I hadn't had a chance to post an update, but I also updated my PBX version to 66.0.6 as recommended, and it's still not working.
  12. I've got mine running on Debian64 on Google's cloud. I recently installed the a Single Tenant Vodia PBX on a customer's Windows PC at their request, I'm thinking I might try getting the transcriptions working on that to see if we can further narrow down the issue to the OS.
  13. My system is hosted in Google’s Cloud
  14. And I was still never able to get it working. I kinda kicked to the back burner because I wasn’t getting anywhere, but I’d definitely like to get it working for my customers
  15. Hello everyone. I have a customer with some existing Audiocodes MP-202 Fax ATAs which they would like to use on the Vodia PBX which I recently setup for them. I factory reset them and put in what I feel is all of the correct information to get them to register with the Vodia PBX, but they don't seem to be working. Looking at the log file, it doesn't appear that they are even attempting to register with the PBX. I found a past topic on this here: I followed the steps laid out by the user in this topic, but still no luck. Has anybody used any of these recently, and if so, would you happen to have a guide to get these to register with the Vodia PBX? Any help would be greatly appreciated. Thank you! I am running the hosted Vodia Multi-Tenant PBX version 66.0.4
  16. I was wondering if anybody knows what the Vodia system sets the "Administrator Login" password to for the "Advanced Settings" area of Snom phones' GUIs. When I initially enter the IP address of the phone in my browser, I get prompted for a user name and password. Here, I am able to use the authentication user name and password which I set in the general settings area of my domain like usual. But when I go into the advanced settings of the phone, I get prompted for an "Administrator Login". The authentication password does not work here. When the phone is still in its original factory state, it does not prompt for this password, only after it has been provisioned by the Vodia server. If anybody knows, I'd appreciate the info. Thank you! I am running Vodia Hosted Multi-Tenant Version 66.0.4
  17. I SSH'ed into my server, which is in Google's cloud when I ran this command
  18. Is the reply that I got from the server what I should have gotten, or is this not right?
  19. I ran it again without the https like this: wget speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY and it replied with this: --2020-10-23 15:39:11-- http://speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXYResolving speech.googleapis.com (speech.googleapis.com)... 172.217.5.74, 172.217.11.74, 142.250.68.106, ...Connecting to speech.googleapis.com (speech.googleapis.com)|172.217.5.74|:80... connected.HTTP request sent, awaiting response... 404 Not Found2020-10-23 15:39:11 ERROR 404: Not Found.
  20. I ran that command, here's what it replied: --2020-10-23 15:33:52-- ftp://https/speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY => ‘.listing’ Resolving https (https)... failed: Name or service not known. wget: unable to resolve host address ‘https’
  21. I ran curl https:speech.googleapis.com/v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY and it responded with curl: (3) Illegal port number I'm assuming that's probably not what I want to see?
  22. Sorry, I'm still relatively new to this. What do you mean by: Is that something I would do in the firewall within my GCP interface? Or something I would do from a command prompt within SSH?
  23. Ok, I’ll try that after hours tonight and let you know what happened. Thank you for all your help!
  24. Ok, here's what I got. I tried to get rid of anything that wasn't related to my test call, but a lot of calls are coming in: [5] 8:19:42.050 SIP Rx 67.231.8.195:5060:ⓘ INVITE sip:+17028577960@34.94.42.237 SIP/2.0 Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bK1531.21abeb32.1 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B413dbeea9f9b06db From: "DAVID HINOJOS " <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90> Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282963 INVITE Max-Forwards: 68 Allow: INVITE,ACK,CANCEL,BYE,REFER,OPTIONS Accept: application/sdp Contact: <sip:+17023253253@192.168.5.233:5060> Content-Length: 330 Content-Disposition: session; handling=required Content-Type: application/sdp Remote-Party-ID: "DAVID HINOJOS " <sip:+17023253253@192.168.5.233:5060>;privacy=off;screen=no v=0 o=Sonus_UAC 768753 791015 IN IP4 192.168.5.233 s=SIP Media Capabilities c=IN IP4 67.231.9.93 t=0 0 m=audio 50648 RTP/AVP 0 18 96 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:96 iLBC/8000 a=fmtp:96 mode=30 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv a=maxptime:30 [8] 8:19:42.051 Find trunk: Message RURI user +17028577960, host 34.94.42.237ⓘ [9] 8:19:42.051 Find trunk: Try expression for 3ⓘ [9] 8:19:42.051 Find trunk: Try expression for 5ⓘ [9] 8:19:42.051 Find trunk: Try expression for 7ⓘ [9] 8:19:42.051 Find trunk: Trunk 8 matches domain localhostⓘ [9] 8:19:42.051 Find trunk: Try expression for 8ⓘ [9] 8:19:42.051 Find trunk: Trunk 9 matches domain localhostⓘ [9] 8:19:42.051 Find trunk: Trunk 9 matches IPⓘ [9] 8:19:42.051 Find trunk: Trunk 9 matches IP and portⓘ [9] 8:19:42.051 Find trunk: Try expression for 9ⓘ [8] 8:19:42.051 Identify trunk (IP address/port and domain match) Bandwidth 2 (9)ⓘ [8] 8:19:42.051 Trying to match number 7028577960 with ERE (.*)ⓘ [8] 8:19:42.051 Send call to extension ERE returned +17028577960ⓘ [8] 8:19:42.051 Global trunk sends call into domain qtsⓘ [5] 8:19:42.052 SIP Tx 67.231.8.195:5060:ⓘ SIP/2.0 100 Trying Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bK1531.21abeb32.1 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B413dbeea9f9b06db Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> From: "DAVID HINOJOS " <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90>;tag=c592475c62 Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282963 INVITE Content-Length: 0 [8] 8:19:42.052 Trying to match number 7028577960 with ERE (.*)ⓘ [8] 8:19:42.052 Send call to extension ERE returned +17028577960ⓘ [8] 8:19:42.052 Global trunk sends call into domain qtsⓘ [8] 8:19:42.053 Trying to match number 7028577960 with ERE (.*)ⓘ [8] 8:19:42.053 Send call to extension ERE returned +17028577960ⓘ [8] 8:19:42.053 Trying to match number 7028577960 with ERE (.*)ⓘ [8] 8:19:42.053 Send call to extension ERE returned +17028577960ⓘ [8] 8:19:42.053 Trying to match number 7028577960 with ERE (.*)ⓘ [8] 8:19:42.053 Send call to extension ERE returned +17028577960ⓘ [5] 8:19:42.055 SIP Tx 67.231.8.195:5060:ⓘ SIP/2.0 183 Session Progress Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bK1531.21abeb32.1 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B413dbeea9f9b06db Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> From: "DAVID HINOJOS " <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90>;tag=c592475c62 Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282963 INVITE Contact: <sip:+17028577960@34.94.42.237:5060;transport=udp> Supported: replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, INFO, UPDATE Allow-Events: refer Accept: application/sdp User-Agent: Vodia-PBX/66.0.2 Content-Type: application/sdp Content-Length: 249 v=0 o=- 1545553338 1545553338 IN IP4 34.94.42.237 s=- c=IN IP4 34.94.42.237 t=0 0 m=audio 54548 RTP/AVP 0 18 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv [5] 8:19:42.056 SIP Tx 67.231.8.195:5060:ⓘ SIP/2.0 200 Ok Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bK1531.21abeb32.1 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B413dbeea9f9b06db Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> From: "DAVID HINOJOS " <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90>;tag=c592475c62 Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282963 INVITE Contact: <sip:+17028577960@34.94.42.237:5060;transport=udp> Supported: replaces, norefersub Allow: INVITE, ACK, CANCEL, BYE, REFER, INFO, UPDATE Allow-Events: refer Accept: application/sdp User-Agent: Vodia-PBX/66.0.2 Content-Type: application/sdp Content-Length: 249 v=0 o=- 1545553338 1545553338 IN IP4 34.94.42.237 s=- c=IN IP4 34.94.42.237 t=0 0 m=audio 54548 RTP/AVP 0 18 101 a=rtpmap:0 PCMU/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=sendrecv [5] 8:19:42.130 SIP Rx 67.231.8.195:5060:ⓘ ACK sip:+17028577960@34.94.42.237:5060;transport=udp SIP/2.0 Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bK1531.21abeb32.3 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B4143fed110553c6f From: <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90>;tag=c592475c62 Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282963 ACK Max-Forwards: 69 Content-Length: 0 [5] 8:20:00.417 SIP Rx 67.231.8.195:5060:ⓘ BYE sip:+17028577960@34.94.42.237:5060;transport=udp SIP/2.0 Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bKe431.987f74b1.0 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B44515a2a10553c6f From: <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90>;tag=c592475c62 Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282964 BYE Max-Forwards: 69 Content-Length: 0 [5] 8:20:00.417 SIP Tx 67.231.8.195:5060:ⓘ SIP/2.0 200 Ok Via: SIP/2.0/UDP 67.231.8.195;branch=z9hG4bKe431.987f74b1.0 Via: SIP/2.0/UDP 192.168.5.233:5060;branch=z9hG4bK08B44515a2a10553c6f Record-Route: <sip:67.231.8.195;r2=on;lr=on;ftag=gK08236e60> Record-Route: <sip:192.168.5.90;r2=on;lr=on;ftag=gK08236e60> From: <sip:+17023253253@192.168.5.233>;tag=gK08236e60 To: <sip:+17028577960@192.168.5.90>;tag=c592475c62 Call-ID: 292037125_134139546@192.168.5.233 CSeq: 282964 BYE Contact: <sip:+17028577960@34.94.42.237:5060;transport=udp> User-Agent: Vodia-PBX/66.0.2 Content-Length: 0 [6] 8:20:00.420 1 more requests pending to push.vodia.net:443ⓘ [6] 8:20:00.420 2 more requests pending to push.vodia.net:443ⓘ [7] 8:20:00.438 https:speech.googleapis.com:443: DNS A returned 216.58.193.202ⓘ [7] 8:20:00.438 https:speech.googleapis.com:443: Connect to 216.58.193.202ⓘ [9] 8:20:00.439 https:speech.googleapis.com:443: Send request (129270 bytes)ⓘ POST /v1/speech:recognize?key=AIzaSyD6XgI-eLss3oX3xl1cLSSUV6Nxg05jCXY HTTP/1.1 Host: speech.googleapis.com Content-Type: application/json; charset=utf-8" Content-Length: 129087 {"config":{"encoding":"LINEAR16","sampleRateHertz":8000,"languageCode":"en-US","maxAlternatives":1,"profanityFilter":true,"model":"phone_call","enableAutomaticPunctuation":true,"enableWordTimeOffsets":false},"audio":{"content":"AAAIAAAAAAD4//j/+P/w//j/+P/w//D/8P/w//D/+P8AAAAA+P8AAAAAAAD4//j/+P8AAAAAAAAIAAgAAAAAAAAACAAIAAAA+P8AAAAAAAAIAAAAAAAIAAAAAAAIgA [9] 8:20:00.439 Initialize TLS connectionⓘ [7] 8:20:00.453 https:speech.googleapis.com:443: TCP disconnectⓘ [7] 8:20:00.453 https:speech.googleapis.com:443: Return code 500ⓘ [8] 8:20:00.453 https:speech.googleapis.com:443: Return content (0 bytes)ⓘ [7] 8:20:00.453 Transscript for 6s failed with code 500ⓘ [7] 8:20:00.454 Closing connection https:speech.googleapis.com:443ⓘ [5] 8:20:00.455 Last message repeated 2 timesⓘ [7] 8:20:00.455 https:license.vodia.com:443: DNS A returned 54.175.147.78ⓘ [7] 8:20:00.455 Last message repeated 2 timesⓘ [7] 8:20:00.455 https:license.vodia.com:443: Connect to 54.175.147.78ⓘ [7] 8:20:00.522 Last message repeated 2 timesⓘ [9] 8:20:00.522 https:license.vodia.com:443: Send request (9994 bytes)ⓘ POST /transcode?code=5NQRWETFB2QZ HTTP/1.1 Host: license.vodia.com Content-Type: audio/wav Content-Length: 9876 [9] 8:20:00.522 Last message repeated 2 timesⓘ [9] 8:20:00.522 Initialize TLS connectionⓘ [7] 8:20:00.657 https:push.vodia.net:443: DNS A returned 54.175.147.78ⓘ [7] 8:20:00.657 https:push.vodia.net:443: Connect to 54.175.147.78ⓘ [9] 8:20:00.724 https:push.vodia.net:443: Send request (536 bytes)ⓘ POST /fcm HTTP/1.1 Host: push.vodia.net Content-Type: application/json Content-Length: 439 {"code":"5NQRWETFB2QZ","message":"{\"notification\":{\"title\":\"\\\"David Hinojos\\\" <sip:201@qts>\",\"text\":\"\\\"David Hinojos\\\" <sip:201@qts> sent you a voicemail.\",\"tag\":\"vodia\"},\"data\":{\"message\":{\"action\":\"voicemail\",\"vmfrom\":\"\\\"David Hinojos\\\" <sip:201@qts>\"}},\"to\":\"a@293D91BF215EE7A841FA0C294F2A4799F7F43922C7DF373BAE2BB85B9E2274A4@1039CDC378534B24D1F964ACBC5F79E56ECF5549B7A672D9808FAA00D8337716\"}"} [9] 8:20:00.724 Initialize TLS connectionⓘ [9] 8:20:00.783 Last message repeated 2 timesⓘ [9] 8:20:00.783 Received 6328 bytesⓘ HTTP/1.1 200 OK Date: Thu, 22 Oct 2020 15:20:00 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 6192 Content-Type: audio/mpeg [9] 8:20:00.783 Last message repeated 2 timesⓘ [7] 8:20:00.783 https:license.vodia.com:443: Return code 200ⓘ Date: Thu, 22 Oct 2020 15:20:00 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 6192 Content-Type: audio/mpeg [7] 8:20:00.783 Last message repeated 2 timesⓘ [8] 8:20:00.783 https:license.vodia.com:443: Return content (6192 bytes)ⓘ [9] 8:20:00.973 Received 144 bytesⓘ HTTP/1.1 200 OK Date: Thu, 22 Oct 2020 15:20:00 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 5 Content-Type: application/json [7] 8:20:00.973 https:push.vodia.net:443: Return code 200ⓘ Date: Thu, 22 Oct 2020 15:20:00 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 5 Content-Type: application/json [8] 8:20:00.973 https:push.vodia.net:443: Return content (5 bytes)ⓘ false [9] 8:20:00.973 https:push.vodia.net:443: Send request (557 bytes)ⓘ POST /fcm HTTP/1.1 Host: push.vodia.net Content-Type: application/json Content-Length: 460 {"code":"5NQRWETFB2QZ","message":"{\"notification\":{\"title\":\"\\\"David Hinojos\\\" <sip:201@qts>\",\"text\":\"\\\"David Hinojos\\\" <sip:201@qts> sent you a voicemail.\",\"tag\":\"vodia\"},\"data\":{\"message\":{\"action\":\"voicemail\",\"vmfrom\":\"\\\"David Hinojos\\\" <sip:201@qts>\"}},\"to\":\"cTchbil1DFA:APA91bEVCIEdQLURgiuqOLaUnd6gs3An2Bt2qdJ_BiIst77DQxa8l7NdAg_3TRk2aaxToa4-g_StXxNlwmZTXAdZq2nTpwT_nUt5OVE8-pbxyj9ulr8FqyjNBYtr0Y-DhNeIbJLUuHCT\"}"} [9] 8:20:01.098 Received 143 bytesⓘ HTTP/1.1 200 OK Date: Thu, 22 Oct 2020 15:20:01 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 4 Content-Type: application/json [7] 8:20:01.099 https:push.vodia.net:443: Return code 200ⓘ Date: Thu, 22 Oct 2020 15:20:01 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 4 Content-Type: application/json [8] 8:20:01.099 https:push.vodia.net:443: Return content (4 bytes)ⓘ true [9] 8:20:01.099 https:push.vodia.net:443: Send request (536 bytes)ⓘ POST /fcm HTTP/1.1 Host: push.vodia.net Content-Type: application/json Content-Length: 439 {"code":"5NQRWETFB2QZ","message":"{\"notification\":{\"title\":\"\\\"David Hinojos\\\" <sip:201@qts>\",\"text\":\"\\\"David Hinojos\\\" <sip:201@qts> sent you a voicemail.\",\"tag\":\"vodia\"},\"data\":{\"message\":{\"action\":\"voicemail\",\"vmfrom\":\"\\\"David Hinojos\\\" <sip:201@qts>\"}},\"to\":\"a@293D91BF215EE7A841FA0C294F2A4799F7F43922C7DF373BAE2BB85B9E2274A4@AD5845087F3AF766567F4F90BE2D6E644D31E316F237A6116B0CDA3259047BFC\"}"} [9] 8:20:01.166 Received 144 bytesⓘ HTTP/1.1 200 OK Date: Thu, 22 Oct 2020 15:20:01 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 5 Content-Type: application/json [7] 8:20:01.166 https:push.vodia.net:443: Return code 200ⓘ Date: Thu, 22 Oct 2020 15:20:01 GMT Server: Apache/2.4.29 (Ubuntu) Content-Length: 5 Content-Type: application/json [8] 8:20:01.166 https:push.vodia.net:443: Return content (5 bytes)ⓘ false
×
×
  • Create New...