-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to send Short SMS #126
Comments
the same problem #84 (comment) |
Hi. Any news on this? I Sweden the operators are using a non-standard mobile number for the users to response to.
|
@standardgbg : Do you have debug logs, like the OP? Especially this part:
That garbage character at the end looks suspicious for instance. The rest seems legit according to https://www.diafaan.com/sms-tutorials/gsm-modem-tutorial/online-sms-pdu-decoder/ @antonatosn: do you have the PDU that Gammu generates? |
@standardgbg : You could try fiddling with the number-type. Till exempel: diff --git a/pdu.c b/pdu.c
index 94f7427..a6f7b6e 100644
--- a/pdu.c
+++ b/pdu.c
@@ -212,8 +212,7 @@
#define NUMBER_TYPE_INTERNATIONAL (TP_A_EXT_NOEXT | TP_A_TON_INTERNATIONAL | TP_A_NPI_TEL_E164_E163) /* 0x91 */
#define NUMBER_TYPE_NATIONAL (TP_A_EXT_NOEXT | TP_A_TON_SUBSCRIBERNUM | TP_A_NPI_NATIONALNUM) /* 0xC8 */
#define NUMBER_TYPE_ALPHANUMERIC (TP_A_EXT_NOEXT | TP_A_TON_ALPHANUMERIC | TP_A_NPI_UNKNOWN) /* 0xD0 */
-/* maybe NUMBER_TYPE_NETWORKSHORT should be 0xB1 ??? */
-#define NUMBER_TYPE_NETWORKSHORT (TP_A_EXT_NOEXT | TP_A_TON_NETSPECIFIC | TP_A_NPI_PRIVATENUM) /* 0xB9 */
+#define NUMBER_TYPE_NETWORKSHORT (TP_A_EXT_NOEXT | TP_A_TON_NETSPECIFIC | TP_A_NPI_TEL_E164_E163) /* 0xB1 */
#define NUMBER_TYPE_UNKNOWN (TP_A_EXT_NOEXT | TP_A_TON_UNKNOWN | TP_A_NPI_TEL_E164_E163) /* 0x81 */
/* Reject Duplicate */ See https://en.wikipedia.org/wiki/GSM_03.40 for possible combinations. Let us know if changing the value helps. |
Hey folks, I solve it in a different way. I am sending it as a PDU command on asterisk -x. /usr/sbin/asterisk -rx "dongle pdu dongle0 00210005819118F000081003a70391039c039f03930395039b039f" If I recall, the problem was on SMSC. Since the implementation was not sending SMSC each time but relies on SIM to append it later (which for some doesn't do it). |
Hi. Can someone help me figure out why I'm not able to send pdu? My avalible commands: |
|
@standardgbg dongle pdu has been removed on: Currently I am using raspbx which uses the bg111 version. |
I try some changes on PDU.c the also about the garbage char on comment it's not garbage at all. It is the CTRL+Z or CHR(26) Despite that SMS is working now. I suggest we should brink back the cli command to send SMS in PDU form. |
Unable to send message solus*CLI> dongle sms dongle0 +79XXXXXXXXX "This is big sms test"
[dongle0] SMS queued for send
-- [dongle0] Error payload: UNKNOWN
-- [dongle0] Error sending SMS message 0x7f057c050b50
[May 26 19:24:46] ERROR[57]: at_response.c:287 log_cmd_response_error: [dongle0] Error sending SMS message 0x7f057c050b50 SMSTEXT
[May 26 19:24:46] WARNING[79][C-00000005]: pbx.c:4507 __ast_pbx_run: Channel 'Local/report@incoming-00000003;1' sent to invalid extension but no invalid handler: context,exten,priority=incoming,report,1 P.S. Sorry, just don't have any money on my balance sheet 😄 |
Please, enable the debug to see the AT commands and responses. |
I didn't have enough funds to send SMS.
Is there any variable containing the error text to handle it in exten |
Unfortunately, I don't know but nice to have it. |
Hi,
I am trying to send Short type SMS but its failing.
When I send the cmd: dongle sms dongle0 1314 YP
I am getting
-- [dongle0] Error payload: UNKNOWN
-- [dongle0] Error sending SMS message 0x1f84378
From PDU decoders I saw that there is no SMSC number on PDU.
I have also test a normal number and it works.
Other test:
Please could you give me an advice?
Thanks
The text was updated successfully, but these errors were encountered: