execcomm Posted August 17, 2021 Report Share Posted August 17, 2021 Followed the guide to install Telnyx, and I'm having problems. Upgraded to the latest version. 67.6 [8] 12:20:45.323 REST: POST /rest/user/testext@192.168.1.100/chat?number=%2B471675864 {"type":"text","text":"This is a test SMS","date":1629217244810} [6] 12:20:45.325 Could not read file chat\356.xml (error code ERROR_FILE_NOT_FOUND) [8] 12:20:45.326 Using system settings for SMS provider telnyx and user [8] 12:20:45.326 REST: Return 200 Ok (application/json) true [7] 12:20:45.327 https:sms.telnyx.com:443: DNS A returned 192.76.120.28 [7] 12:20:45.327 https:sms.telnyx.com:443: Connect to 192.76.120.28 [9] 12:20:45.341 https:sms.telnyx.com:443: Send request (209 bytes) POST https://sms.telnyx.com/messages HTTP/1.1 Host: sms.telnyx.com x-profile-secret: **************** Content-Type: application/json Content-Length: 64 {"from":"+482612144","to":"+471675864","body":"This is a test SMS"} [9] 12:20:45.341 Initialize TLS connection [9] 12:20:45.341 HTTP 192.76.120.28: Send Client Hello(0303611B..00020017) [5] 12:20:45.355 HTTP 192.76.120.28: Alert Fatal (2): Handshake failure (40) [7] 12:20:45.355 https:sms.telnyx.com:443: TCP disconnect [7] 12:20:45.355 https:sms.telnyx.com:443: Return code 500 [8] 12:20:45.355 https:sms.telnyx.com:443: Return content (0 bytes) [7] 12:20:45.356 Closing connection https:sms.telnyx.com:443 Quote Link to comment Share on other sites More sharing options...
execcomm Posted August 17, 2021 Author Report Share Posted August 17, 2021 Was able to wireshark and this is: Frame 828: 167 bytes on wire (1336 bits), 167 bytes captured (1336 bits) on interface 0 Ethernet II, Src: Cisco, Dst: Juniper Internet Protocol Version 4, Src: 192.168.1.100, Dst: 192.76.120.28 Transmission Control Protocol, Src Port: 3149, Dst Port: 443, Seq: 1, Ack: 1, Len: 113 Source Port: 3149 Destination Port: 443 [Stream index: 18] [TCP Segment Len: 113] Sequence number: 1 (relative sequence number) [Next sequence number: 114 (relative sequence number)] Acknowledgment number: 1 (relative ack number) 0101 .... = Header Length: 20 bytes (5) Flags: 0x018 (PSH, ACK) Window size value: 256 [Calculated window size: 65536] [Window size scaling factor: 256] Checksum: 0xc35f [unverified] [Checksum Status: Unverified] Urgent pointer: 0 [SEQ/ACK analysis] TCP payload (113 bytes) Secure Sockets Layer TLSv1.2 Record Layer: Handshake Protocol: Client Hello Content Type: Handshake (22) Version: TLS 1.2 (0x0303) Length: 108 Handshake Protocol: Client Hello Frame 829: 61 bytes on wire (488 bits), 61 bytes captured (488 bits) on interface 0 Ethernet II, Src: Juniper, Dst: Cisco Internet Protocol Version 4, Src: 192.76.120.28, Dst: 192.168.1.100 Transmission Control Protocol, Src Port: 443, Dst Port: 3149, Seq: 1, Ack: 114, Len: 7 Source Port: 443 Destination Port: 3149 [Stream index: 18] [TCP Segment Len: 7] Sequence number: 1 (relative sequence number) [Next sequence number: 8 (relative sequence number)] Acknowledgment number: 114 (relative ack number) 0101 .... = Header Length: 20 bytes (5) Flags: 0x018 (PSH, ACK) Window size value: 501 [Calculated window size: 64128] [Window size scaling factor: 128] Checksum: 0x3261 [unverified] [Checksum Status: Unverified] Urgent pointer: 0 [SEQ/ACK analysis] TCP payload (7 bytes) Secure Sockets Layer TLSv1.2 Record Layer: Alert (Level: Fatal, Description: Handshake Failure) Content Type: Alert (21) Version: TLS 1.2 (0x0303) Length: 2 Alert Message Quote Link to comment Share on other sites More sharing options...
Support Posted August 17, 2021 Report Share Posted August 17, 2021 Hit the "reset" button at the bottom of : /reg_certificate.htm page on the PBX and try this again. Quote Link to comment Share on other sites More sharing options...
execcomm Posted August 17, 2021 Author Report Share Posted August 17, 2021 Not working by pressing the reset button. Quote Link to comment Share on other sites More sharing options...
Support Posted August 17, 2021 Report Share Posted August 17, 2021 2 hours ago, execcomm said: https:sms.telnyx.com:443: Return code 500 Well, the PCAP says it failed but not why it did. Looks like Telnyx can tell more about this since it's 500 from their side? Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted August 17, 2021 Report Share Posted August 17, 2021 The browser does connect through TLS. Do you have that certificate in the PBX CA list? Quote Link to comment Share on other sites More sharing options...
execcomm Posted August 18, 2021 Author Report Share Posted August 18, 2021 Yes, it's on the list. I download it, and check it against the certificate and it matches 100% Telnyx say that everything is working ok with telnyx sms server, and they cannot check anymore without the exact code that sends the pbx. I tried sending the log, but say that is insufficient data. Quote Link to comment Share on other sites More sharing options...
execcomm Posted August 18, 2021 Author Report Share Posted August 18, 2021 This is what telnyx replies: Additionally could you explain in a little more detail why you're trying to set up a TCP connection, as my colleague explained this is generally something we would handle on our side? If you're sending the message through our API the POST is made by us therefore there's no need for you to open a connection. To test this you can send a test message using cURL based on the guide in our developer docs here: https://developers.telnyx.com/docs/v2/messaging/quickstarts/sending-sms-and-mms Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted August 18, 2021 Report Share Posted August 18, 2021 Ok on second look it seems that the problem is that telnyx has changed their TLS setup and now don't accept AES-CBC any more (instead must be AES-GCM). This breaks the interoperability with the PBX. Quote Link to comment Share on other sites More sharing options...
execcomm Posted September 1, 2021 Author Report Share Posted September 1, 2021 Any fix? I tried version 68 and it has problem too. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 1, 2021 Report Share Posted September 1, 2021 No real workaround. You could set up some PHP server that acts like B2B to take the request and then send it to telnyx but it would be easier if they just accept the AES-CBC cipher again. Quote Link to comment Share on other sites More sharing options...
Scott Posted September 11, 2021 Report Share Posted September 11, 2021 Telnyx is NOT going to change. That's like asking Yealink to ask Cisco to change the way they provision so their phones work with Cisco eco-system. This is a Vodia change that needs to happen. You're the interoperability that needs to change NOT the huge telco. I'm not sure why Vodia isn't acknowledging this needs to be addressed and will in next update. 3CX never broke as many other platforms either. I'm not 100% it wasn't broken by Vodia update I'm not a coding guy but doesn't seem that big of a deal to change the TLS mythology your using. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted September 13, 2021 Report Share Posted September 13, 2021 I would not speculate if they would change their TLS setup (back). But I agree it's largely a waste of time unfortunately. The PBX needs to add at least one more cipher that they are using, so that there can be a common cipher. Its not a huge deal but it will require a new build. The good news is that it is very easy to reproduce the problem. Quote Link to comment Share on other sites More sharing options...
execcomm Posted October 18, 2021 Author Report Share Posted October 18, 2021 On 9/13/2021 at 8:56 AM, Vodia PBX said: I would not speculate if they would change their TLS setup (back). But I agree it's largely a waste of time unfortunately. The PBX needs to add at least one more cipher that they are using, so that there can be a common cipher. Its not a huge deal but it will require a new build. The good news is that it is very easy to reproduce the problem. Hi Has this cipher been added? Tests last version and still does not work. The client is growing very impatient. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 19, 2021 Report Share Posted October 19, 2021 You can try version 68.0.3 if it works for you. That one should have the cipher. Quote Link to comment Share on other sites More sharing options...
execcomm Posted October 19, 2021 Author Report Share Posted October 19, 2021 I don't see it in the update. I use Windows x64. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted October 19, 2021 Report Share Posted October 19, 2021 Please try again we made the Windows build. Quote Link to comment Share on other sites More sharing options...
execcomm Posted October 21, 2021 Author Report Share Posted October 21, 2021 [9] 08:39:55.678 Initialize TLS connection [9] 08:39:55.678 HTTP 192.76.120.28: Send Client Hello(03036171..00020017) [5] 08:39:55.692 HTTP 192.76.120.28: Alert Fatal (2): Handshake failure (40) [7] 08:39:55.692 https:sms.telnyx.com:443: TCP disconnect [7] 08:39:55.692 https://sms.telnyx.com/messages: Return code 500 (0 bytes) [8] 08:39:55.692 https://sms.telnyx.com/messages: Return headers [7] 08:39:55.692 Closing connection https:sms.telnyx.com:443 Does not work. Quote Link to comment Share on other sites More sharing options...
Vodia Telephone System Posted October 26, 2021 Report Share Posted October 26, 2021 Sorry about that, it seems it had not made it into that version. Can you please try 68.0.3 version, it should have it. Quote Link to comment Share on other sites More sharing options...
Vodia Telephone System Posted October 29, 2021 Report Share Posted October 29, 2021 This will be a new build of the 68.0.3 that you should try which should have the necessary changes. Quote Link to comment Share on other sites More sharing options...
execcomm Posted November 10, 2021 Author Report Share Posted November 10, 2021 It is now working. Thank you Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.