Standard-dep
This module provides a way of communication between SIP network (via SIP MESSAGE) and GSMi [1] networks (via ShortMessageService). Communication is possible from SIP to SMS and vice versa. The module provides facilities like SMS confirmation--the gateway can confirm to the SIP user if his message really reached its destination as a SMS--or multi-part messages--if a SIP messages is too long it will be split and sent as multiple SMS.
Bogdan Iancu
i [2] networks (via ShortMessageService). Communication is possible from SIP to SMS and vice versa. The module provides facilities like SMS confirmation--the gateway can confirm to the SIP user if his message really reached its destination as a SMS--or multi-part messages--if a SIP messages is too long it will be split and sent as multiple SMS.
Errors occurred because of an invalid number or a too long message or because of an internal modem malfunction are reported back to the SIP user via a SIP message containing explanations regarding the error.
Section 1.4, “Functions” [3]).
i [4] require it.
Default is 0 (no).
If the modem should ask for SMS confirmation
from the SMS Center. If the
SMSC reply with an error code, the gateway will
send back to SIP user a SIP message containing the text (or
part of it) that couldn't be send. Two report mechanisms are
implemented:
-
1 - the reports are delivered by the GSM device as
SMS reports (so far supported only by Nokia modems);
-
2 - the reports are delivered as async. CDS responses
(supported by almost all modems, except Ericsson).
Default is 0 (no report).
Default is 0 (no).
If the modem should ask for SMS confirmation from the SMS Center. If the SMSC reply with an error code, the gateway will send back to SIP user a SIP message containing the text (or part of it) that couldn't be send. Two report mechanisms are implemented:
-
1 - the reports are delivered by the GSM device as SMS reports (so far supported only by Nokia modems);
-
2 - the reports are delivered as async. CDS responses (supported by almost all modems, except Ericsson).
Default is 0 (no report).
Put the SIP msg in the specified network queue. The function return error if the number encapsulated into SIP message is malformed, if the content_type is incorrect or because of some internal failures.
Meaning of the parameters is as follows:
-
network_name - Name of network.
Example 9. sms_send_msg_to_net usage
...
if (sms_send_msg_to_net("D1"))
{
if (!t_reply("202", "yes sir, SMS sent over"))
{
# if replying failed, retry statelessly
sl_reply_error();
};
} else {
if (!t_reply("502", "Bad gateway - SMS error"))
{
# if replying failed, retry statelessly
sl_reply_error();
};
break;
};
...
The same as the previous one, but use the default network queue.
Example 10. sms_send_msg usage
...
if (sms_send_msg_to_net())
{
if (!t_reply("202", "yes sir, SMS sent over"))
{
# if replying failed, retry statelessly
sl_reply_error();
};
} else {
if (!t_reply("502", "Bad gateway - SMS error"))
{
# if replying failed, retry statelessly
sl_reply_error();
};
break;
};
...
http://www.iptel.org/ser/doc/modules/sms
Links:
[1] http://www.iptel.org/glossary#term209
[2] http://www.iptel.org/glossary#term209
[3] http://www.iptel.org/sms.html#sms.functions
[4] http://www.iptel.org/glossary#term75