Jump to content

Telnyx not working for SMS


Recommended Posts

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

Link to comment
Share on other sites

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

 

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...