Jump to content

Inbound SMS From Telnyx not working


Recommended Posts

I can send messages from my extension but cannot receive. It was working good before. I did not modify anything since. 

 

[9] 11:01:37.744    Tried to match recvsms
[8] 11:01:37.744    Receive SMS
{"sms_id": "129xxxxx32232848ba", "direction": "inbound", "from": "+xxxxxxxxxx", "to": "+xxxxxxxxxx", "body": "Testing 123"}

Using the app or the desktop interface, nothing shows. The number is added under the SMS ANI and is showing correctly in DID Management going to this extension. SMS is also enabled under my domain.

Link to comment
Share on other sites

Here is the log, i tried several times but that logo stuff keeps on popping up.

 

[9] 13:04:35.836    Accept connection 60 from 192.76.120.11ⓘ
[9] 13:04:35.836    Request /recvsmsⓘ
POST /recvsms HTTP/1.1
Host: 142.132.6.111
X-Telnyx-Signature: t=234234234,h=9VJHY77U0qLF/wDZWjHa/cqqyqP4D8=
Content-Type: application/json
Accept: */*
Accept-Encoding: gzip, deflate
User-Agent: Python/3.7 aiohttp/3.6.2
Content-Length: 150

[7] 13:04:35.836    Provisioning without domain contextⓘ
[9] 13:04:35.836    Tried to match recvsmsⓘ
logo-320x240.jpg logo-480x272.jpg logo-800x480.jpg aastra.cfg startup.cfg 0c1105######.cfg ale_cert.pem config.############.xml auerswald.xml auerswald-phone-############.xml 46xxsettings.txt 46xxdevice.txt J100Supgrade.txt logo-cisco1.png cisco_softkeys.xml snom_bg820-############.tar snom_bg870-############.tar csc############.pem csc############.cfg cyberdata-############.xml 00268B######.xml fanvil-############.xml fanvil-sysconf.xml fanvil-############.txt fanvil.txt logo-fanvil1.bmp logo-fanvil2.bmp logo-fanvil3.bmp logo-fanvil4.bmp ############.boot flyingvoice.cfg 42/2/master.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg000b82###### cfgc074ad###### cfg.xml cfg/cfg001fc1######.xml cfg001fc1######.xml Alert1.wav Alert10.wav Alert2.wav Alert3.wav Alert4.wav Alert5.wav Alert6.wav Alert7.wav Alert8.wav Alert9.wav provisioning.xml logo-mitel-h1.png logo-mitel-h2.png logo-mitel-h3.png logo-mitel-i1.png logo-mitel-i2.png logo-mitel-i3.png Htek.xml cfg001fc1###### cfg00??.xml factory####.bin KX-UTG200B.cfg KX-UTG300B.cfg KX-UT113.cfg KX-UT123.cfg KX-UT133.cfg KX-UT136.cfg KX-UT1363.cfg KX-UT248.cfg KX-UT670.cfg logo-polycom1.jpg logo-polycom2.jpg logo-polycom3.jpg polycom/############-directory.xml polycom/############-all.cfg polycom/############-app.log ############-app.log polycom/############-app.log ############-boot.log polycom/############-boot.log ############.cfg SEP############.cnf.xml SIPDefault.cnf SIP############.cnf F00786######.flag F00786######.cfg logo-snom1.png logo-snom2.png logo-snom3.png logo-snom4.png snom300-############.htm snom320-############.htm snom360-############.htm snom370-############.htm snom_3xx_dialplan_empty.xml snom_3xx_dialplan_row2.xml snom_3xx_dialplan_row3.xml snom_3xx_dialplan_row4.xml snom_3xx_dialplan_usa2.xml snom_3xx_dialplan_usa3.xml snom_3xx_dialplan_usa4.xml snom_3xx_phone-############.xml snom710-############.htm snom_710_phone-############.xml snom720-############.htm snom_720_phone-############.xml snom_745_phone-############.xml snom760-############.htm snom_760_phone-############.xml snom_785_phone-############.xml snom820-############.htm snom821-############.htm snom_820_phone-############.xml snom870-############.htm snom_branding-############.xml snom_buttons-############.xml C520-WiMi.cfg snom_cert-############.xml snom_firmware-############.xml snomM?00KLE.htm snomM?00SC.htm snomM?00.htm snom-m9-############.xml snom-m9-firmware-############.xml snom-m9-settings-############.xml snom_models-############.xml snomMP-############.htm snom300.htm snom320.htm snom360.htm snom370.htm snom820.htm snom821.htm snom870.htm snomMP.htm snomPA1.htm snomPA1-############.htm snom_thumb-############.jpg snom715-############.htm snom725-############.htm snom765-############.htm snomD120-############.htm snomD305-############.htm snomD315-############.htm snomD335-############.htm snomD345-############.htm snomD375-############.htm snomD385-############.htm snomD712-############.htm snomD715-############.htm snomD717-############.htm snomD725-############.htm snomD735-############.htm snomD745-############.htm snomD765-############.htm snomD785-############.htm snom_v10_phone-############.xml /spa9##.cfg spa############.cfg IP????_############.cfg Temporis_IP????_############.cfg V?????_############.cfg vop_data.xml vop.xml 00a859######.cfg vtech_branding-############.xml vtech_buttons-############.xml vtech_cert-############.xml VTechET605-############.htm VTechET635-############.htm VTechET685-############.htm vtech_firmware-############.xml vtech_models-############.xml ############.cfg vtech_phone-############.xml logo-yealink1.png logo-yealink2.png logo-yealink3.png logo-yealink4.png logo-yealink5.png yealink_cert.pem 001565######.cfg 805e0c######.cfg 805ec0######.cfg yealink-############.cfg yealink.cfg yealink-favorite.xml yealink_mcast.xml yealink-webitem.cfg
[8] 13:04:35.836    Receive SMSⓘ
{"sms_id": "eb4e415c-79d9-432bd-91fd-3c23dddebde5", "direction": "inbound", "from": "+32487730xyz", "to": "+32487730xyz", "body": "This is just simple test"}

Link to comment
Share on other sites

27 minutes ago, execcomm said:

{"sms_id": "eb4e415c-79d9-432bd-91fd-3c23dddebde5", "direction": "inbound", "from": "+32487730xyz", "to": "+32487730xyz", "body": "This is just simple test"}

Seems like a successful message was it? If not, you can turn off the web server logs and see if that takes off the "logo" logs (you can also turn them off after knowing which logs are generating it by clicking on "ⓘ") and set the logs to 1000 length. Please also set it back to 100 after done.

You are checking under the message section on the App / user portal correct?

Link to comment
Share on other sites

Just to inform again. This was working in the previous version. When it says to Tried to match recvsms it gets that logo sutff everytime.

 

Turning everything to 0, and only script and IVR events to 9 does not show any logs. Turning everything to 9, then I get the same thing again:

 

[9] 9:44:41.882    Request /recvsms (I WEBSERVER)
POST /recvsms HTTP/1.1
Host: 142.132.6.111
X-Telnyx-Signature: t=162393481,h=uqxssdadsasd2zxc9CqSfKaswxfrw88BulI=
Content-Type: application/json
Accept: */*
Accept-Encoding: gzip, deflate
User-Agent: Python/3.7 aiohttp/3.6.2
Content-Length: 150

[7] 9:44:41.882    Provisioning without domain context (I PROV)
[9] 9:44:41.882    Tried to match recvsms (I WEBSERVER)
logo-320x240.jpg logo-480x272.jpg logo-800x480.jpg aastra.cfg startup.cfg 0c1105######.cfg ale_cert.pem config.############.xml auerswald.xml auerswald-phone-############.xml 46xxsettings.txt 46xxdevice.txt J100Supgrade.txt logo-cisco1.png cisco_softkeys.xml snom_bg820-############.tar snom_bg870-############.tar csc############.pem csc############.cfg cyberdata-############.xml 00268B######.xml fanvil-############.xml fanvil-sysconf.xml fanvil-############.txt fanvil.txt logo-fanvil1.bmp logo-fanvil2.bmp logo-fanvil3.bmp logo-fanvil4.bmp ############.boot flyingvoice.cfg 42/2/master.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg############.xml cfg000b82###### cfgc074ad###### cfg.xml cfg/cfg001fc1######.xml cfg001fc1######.xml Alert1.wav Alert10.wav Alert2.wav Alert3.wav Alert4.wav Alert5.wav Alert6.wav Alert7.wav Alert8.wav Alert9.wav provisioning.xml logo-mitel-h1.png logo-mitel-h2.png logo-mitel-h3.png logo-mitel-i1.png logo-mitel-i2.png logo-mitel-i3.png Htek.xml cfg001fc1###### cfg00??.xml factory####.bin KX-UTG200B.cfg KX-UTG300B.cfg KX-UT113.cfg KX-UT123.cfg KX-UT133.cfg KX-UT136.cfg KX-UT1363.cfg KX-UT248.cfg KX-UT670.cfg logo-polycom1.jpg logo-polycom2.jpg logo-polycom3.jpg polycom/############-directory.xml polycom/############-all.cfg polycom/############-app.log ############-app.log polycom/############-app.log ############-boot.log polycom/############-boot.log ############.cfg SEP############.cnf.xml SIPDefault.cnf SIP############.cnf F00786######.flag F00786######.cfg logo-snom1.png logo-snom2.png logo-snom3.png logo-snom4.png snom300-############.htm snom320-############.htm snom360-############.htm snom370-############.htm snom_3xx_dialplan_empty.xml snom_3xx_dialplan_row2.xml snom_3xx_dialplan_row3.xml snom_3xx_dialplan_row4.xml snom_3xx_dialplan_usa2.xml snom_3xx_dialplan_usa3.xml snom_3xx_dialplan_usa4.xml snom_3xx_phone-############.xml snom710-############.htm snom_710_phone-############.xml snom720-############.htm snom_720_phone-############.xml snom_745_phone-############.xml snom760-############.htm snom_760_phone-############.xml snom_785_phone-############.xml snom820-############.htm snom821-############.htm snom_820_phone-############.xml snom870-############.htm snom_branding-############.xml snom_buttons-############.xml C520-WiMi.cfg snom_cert-############.xml snom_firmware-############.xml snomM?00KLE.htm snomM?00SC.htm snomM?00.htm snom-m9-############.xml snom-m9-firmware-############.xml snom-m9-settings-############.xml snom_models-############.xml snomMP-############.htm snom300.htm snom320.htm snom360.htm snom370.htm snom820.htm snom821.htm snom870.htm snomMP.htm snomPA1.htm snomPA1-############.htm snom_thumb-############.jpg snom715-############.htm snom725-############.htm snom765-############.htm snomD120-############.htm snomD305-############.htm snomD315-############.htm snomD335-############.htm snomD345-############.htm snomD375-############.htm snomD385-############.htm snomD712-############.htm snomD715-############.htm snomD717-############.htm snomD725-############.htm snomD735-############.htm snomD745-############.htm snomD765-############.htm snomD785-############.htm snom_v10_phone-############.xml /spa9##.cfg spa############.cfg IP????_############.cfg Temporis_IP????_############.cfg V?????_############.cfg vop_data.xml vop.xml 00a859######.cfg vtech_branding-############.xml vtech_buttons-############.xml vtech_cert-############.xml VTechET605-############.htm VTechET635-############.htm VTechET685-############.htm vtech_firmware-############.xml vtech_models-############.xml ############.cfg vtech_phone-############.xml logo-yealink1.png logo-yealink2.png logo-yealink3.png logo-yealink4.png logo-yealink5.png yealink_cert.pem 001565######.cfg 805e0c######.cfg 805ec0######.cfg yealink-############.cfg yealink.cfg yealink-favorite.xml yealink_mcast.xml yealink-webitem.cfg
[8] 9:44:41.882    Receive SMS (I WEBSERVER)
{"sms_id": "0c5ccfad-bfd8-4s32-a38b-1be9dasd3b8a6", "direction": "inbound", "from": "+32487730xyz", "to": "+32487730xyz", "body": "This is a 3rd test"}
[8] 9:44:42.110    Last message repeated 2 times (SIP)

Link to comment
Share on other sites

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

Hi, Sorry for the late reply. Now even outgoing is not working. 

[9] 13:15:21.704	Request /rest/user/765@pbx.local.com/chat?number=%2B17025932233ⓘ
POST /rest/user/765@pbx.local.com/chat?number=%2B17025932233 HTTP/1.1
Host: pbx.local.com
Connection: keep-alive
Content-Length: 56
Accept: */*
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US
Content-Type: application/json; charset=utf-8
Cookie: session=xonvj9c4dels4gzjm1sm
Origin: localhost
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) VodiaPBX/3.5.5 Chrome/ Electron/4.2.12 Safari/537.36

[9] 13:15:21.704	Last message repeated 2 timesⓘ
[8] 13:15:21.704	REST: POST /rest/user/765@pbx.local.com/chat?number=%2B17025932233ⓘ
{"type":"text","text":"hello moto","date":1618334122010}
[6] 13:15:21.705	Could not read file chat\266.xml (error code ERROR_FILE_NOT_FOUND)ⓘ
[8] 13:15:21.707	Using system settings for SMS provider telnyx and user ⓘ
[8] 13:15:21.707	Last message repeated 2 timesⓘ
[8] 13:15:21.707	REST: Return 200 Ok (application/json)ⓘ
true
[7] 13:15:21.707	https:sms.telnyx.com:443: DNS A returned 192.76.120.28ⓘ
[7] 13:15:21.707	https:sms.telnyx.com:443: Connect to 192.76.120.28ⓘ
[9] 13:15:21.722	https:sms.telnyx.com:443: Send request (208 bytes)ⓘ
POST https://sms.telnyx.com/messages HTTP/1.1
Host: sms.telnyx.com
x-profile-secret: ****************
Content-Type: application/json
Content-Length: 63

{"from":"+17022502582","to":"+17025932233","body":"hello moto"}
[9] 13:15:21.722	Initialize TLS connectionⓘ
[9] 13:15:21.722	HTTP 192.76.120.28: Send Client Hello(..00020017)ⓘ
[9] 13:15:21.739	HTTP 192.76.120.28: Receive Server Hello(..03000102)ⓘ
[9] 13:15:21.739	HTTP 192.76.120.28: Receive Certificate(..21165953)ⓘ
[9] 13:15:21.739	HTTP 192.76.120.28: Received chain with 2 certificatesⓘ
[8] 13:15:21.740	HTTP 192.76.120.28: Certificate name *.telnyx.com matchesⓘ
[9] 13:15:21.740	HTTP 192.76.120.28: Receive Server Key Exchange(03001741..4221DB5F)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Pre Master Secret(9466BA2A..FDE4358B)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Client Random(..43FBA0C5)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Server Random(..41662906)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Master Secret(..48C05556)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Receive Server Hello Done()ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Send Client Key Exchange(..64BB2363)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Send Change Cipher Spec(01)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Perform Change Cipher Spec(c014)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Key Block(..E061A75D)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Client Write MAC Secret(..127B4B3C)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Server Write MAC Secret(..CAD5E339)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Client Write Key(..E719AF5C)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Server Write Key(..A86AE93A)ⓘ
[9] 13:15:21.747	HTTP 192.76.120.28: Send Finished(..F1987F0C)ⓘ
[9] 13:15:21.762	HTTP 192.76.120.28: Receive Change Cipher Spec(01)ⓘ
[9] 13:15:21.763	HTTP 192.76.120.28: Receive Process Finished(..1A1EB376)ⓘ
[9] 13:15:21.798	Received 496 bytesⓘ
HTTP/1.1 400 Bad Request
Content-Type: application/json; charset=utf-8
Content-Length: 284
Date: Tue, 13 Apr 2021 17:15:21 GMT
Server: Python/3.7 aiohttp/3.6.2
Strict-Transport-Security: max-age=15552000

[7] 13:15:21.798	https:sms.telnyx.com:443: Return code 400ⓘ
Content-Type: application/json; charset=utf-8
Content-Length: 284
Date: Tue, 13 Apr 2021 17:15:21 GMT
Server: Python/3.7 aiohttp/3.6.2
Strict-Transport-Security: max-age=15552000
[8] 13:15:21.798	https:sms.telnyx.com:443: Return content (284 bytes)ⓘ
{
  "code": "40305",
  "success": false,
  "status": 400,
  "message": "The 'from' address should be string containing a valid phone number or alphanumeric sender ID associated with the sending messaging profile.",
  "url": "https://developers.telnyx.com/docs/overview/errors/40305"

 

Link to comment
Share on other sites

It looks to me like the number is not set up for sending SMS. There is a checklist on https://developers.telnyx.com/docs/v2/messaging/quickstarts/portal-setup that might be helpful. IMHO the message itself looks okay. They might have change the authorization header, but it does not looks like they broke the previous version. 

Link to comment
Share on other sites

  • 2 months later...
  • 3 years later...

We are facing similar issues now on version 69.3.4  We can send and receive SMS on the previous version 68.0.20  but when we test the same Telnyx SMS configuration on the new version 69 we can only send an outbound SMS but no inbound SMS is received.

We opened a support ticket for days now and no response as this appears to be a bug in the current version 69.3.4.

As anyone successfully validated both inbound and outbound SMS on version 69.3.4 with Telnyx ?

Link to comment
Share on other sites

The main difference between 68 and 69 is that SMS is now (mostly) in the tenant. When you upgrade, you might have to set the SMS provider up again. Apart from that, I would choose a non-trivial prefix for the SMS provider — this is essentially the password to post content to the PBX. The log should contain some clue what the PBX is doing with the incoming web request, I would turn on web server logging even if it is very noisy just to make sure that you see the request from Telnyx and when its clear that the PBX detects it as SMS, you can then reduce it to those log messages (e.g. SCRIPT). But there should be be a way to figure out what is going on looking at the logs.

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.

×
×
  • Create New...