UCP-53
Hello List, I'm using Kannel version 1.4.1 on EMI/UCP protocol. I'm already using DLR - however the ACK/ or NACK/ comes from the SMS G/W and not from the Operator SMSC In order to check if the message was received by the user I need to implement Delivery notification operation -53 UCP-53. I was guided by the SMS G/W integrators - to change the following parameters NrqNotification Request set with value 1 NT Notification Typeset with value 3 See 1 and 3 after the largeaccount (short code number) .07/00347/O/51/msisdn/largeaccount//1//3/4/904/024A3A6DB9BD7DBDB9957DB5BDB9BC04009916A65AB6551649A2D9845A2A8B86916CC30AB2C9365A2AC26CB2447708C2D138592B0B459B6CB32D1561661541365B2292A8B44D061055170D22D9865A2AC26C2AC26CB6446461689C0AC2D966DA2CC2AC2CCB6551689B0AB2C9365A226000///1/1//01070605041581FE09323632373338393132///C8 Does anyone knows if Kannel supports this operation, and how to implement it? I was also explained that this query is not in RealTime and I will have to check the status. In return I'm suppose to receive 0 for positive delivery or one of the following error codes: Table B-3: Error Messages and Reason Codes in Notifications Reason Code Meaning 000 Unknown subscriber 001 Service temporary not available 002 Service temporary not available 003 Service temporary not available 004 Service temporary not available 005 Service temporary not available 006 Service temporary not available 007 Service temporary not available 008 Service temporary not available 009 Illegal error code 010 Network time-out 100 Facility not supported 101 Unknown subscriber 102 Facility not provided 103 Call barred 104 Operation barred 105 SC congestion 106 Facility not supported 107 Absent subscriber 108 Delivery fail 109 Sc congestion 110 Protocol error 111 MS not equipped 112 Unknown SC 113 SC congestion 114 Illegal MS 115 MS not a subscriber 116 Error in MS 117 SMS lower layer not provisioned 118 System fail 119 PLMN system failure 120 HLR system failure 121 VLR system failure 122 Previous VLR system failure 123 Controlling MSC system failure 124 VMSC system failure 125 EIR system failure 126 System failure 127 Unexpected data value 200 Error in address service centre 201 Invalid absolute Validity Period 202 Short message exceeds maximum 203 Unable to Unpack GSM message 204 Unable to convert to IRA ALPHABET 205 Invalid validity period format 206 Invalid destination address 207 Duplicate message submit 208 Invalid message type indicator Thanks in advance, Oren Ein-Gal Chief Operating Officer Volas Entertainment | unleash your content T +972 73 252 5252 (ext. 129) F +972 9 956 7481 M + 972 54 522 4183 o...@volasent.com www.VolasEnt.com Part of the LogiaGroup
Silent SMS
Hello List, I'm using Kannel version 1.4.1 on EMI/UCP protocol. Does anyone know if Kannel support Silent SMS. I understood from the Operator that I need to change the RPID from to 0064. RPID = 0064 msg MT Silente # T 2006/08/22 12:10:05.230271 80.207.105.251:5153 - 10.6.67.120:4147 [AP] .70/00161/O/51/335847/4015500///2208061444/0064/3//54692 073 6F6E6F207374617469206164646562697461746920312E3030206575726F//02 011 1060100///D1. # T 2006/08/22 12:10:05.267685 10.6.67.120:4147 - 80.207.105.251:5153 [A] # T 2006/08/22 12:10:05.309729 10.6.67.120:4147 - 80.207.105.251:5153 [AP] .70/00043/R/51/A//3358476930:220806121053/48. RPID = MT non silente # T 2006/08/22 12:15:46.147055 80.207.105.251:5153 - 10.6.67.120:4147 [AP] .75/00161/O/51/335847/4015500///2208061450//3//54692 073 6F6E6F207374617469206164646562697461746920312E3030206575726F//02 011 1060100///C9. # T 2006/08/22 12:15:46.182927 10.6.67.120:4147 - 80.207.105.251:5153 [A] # T 2006/08/22 12:15:46.215573 10.6.67.120:4147 - 80.207.105.251:5153 [AP] .75/00043/R/51/A//3358476930:220806121634/52. Thanks in advance, Oren Ein-Gal
limit the queued messages
Hello Group, I'm using Kannel 1.4.1 with EMI/UCP protocol. Is there a way to limit the queued outgoing messages? Sometimes due to network failures (I assume) the SMSC connection goes from online to re-connecting status, and the messages are being queued. Is there a way to configure the Kannel that the sendsms http interface will return an error in case the SMSC connection is not online. Thanks, Oren Ein-Gal VP Professional Services Volas Entertainment T +972 73 252 5252 (ext. 103) F +972 9 956 7481 M + 972 54 522 4138 www.VolasEnt.com http://www.volasent.com/ Unleash Your Content
RE: limit the queued messages
Hi Falko, Thanks for the fast answer. However I'm looking for a way to limit the outgoing messages queue. I don't want outgoing message to be queued at all. Thanks, Oren Ein-Gal VP Professional Services Volas Entertainment T +972 73 252 5252 (ext. 103) F +972 9 956 7481 M + 972 54 522 4138 www.VolasEnt.com Unleash Your Content -Original Message- From: Falko Ziemann [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 08, 2008 7:22 PM To: Oren Ein-gal Cc: users@kannel.org Subject: Re: limit the queued messages Hi, see core configuration on page 22: sms-incoming-queue-limit number of messages Set maximum size of incoming message queue. After number of messages has hit this value, Kannel began to discard them. Value 0 means giving strict priority to outgoing messages. -1, default, means that the queue of infinite length is accepted. (This works with any normal input, use this variable only when Kannel message queues grow very long). Regards Falko 2008/7/8 Oren Ein-gal [EMAIL PROTECTED]: Hello Group, I'm using Kannel 1.4.1 with EMI/UCP protocol. Is there a way to limit the queued outgoing messages? Sometimes due to network failures (I assume) the SMSC connection goes from online to re-connecting status, and the messages are being queued. Is there a way to configure the Kannel that the sendsms http interface will return an error in case the SMSC connection is not online. Thanks, Oren Ein-Gal VP Professional Services Volas Entertainment T +972 73 252 5252 (ext. 103) F +972 9 956 7481 M + 972 54 522 4138 www.VolasEnt.com Unleash Your Content
RE: binfo and NACK Status
Hello list, Does any one have an answer? Thanks, Oren -הודעה מקורית- מאת: Oren Ein-gal נשלח: ד 30/04/2008 16:15 אל: users@kannel.org נושא: binfo and NACK Status Hello list, I have a Kannel version 1.4.1 with EMI2 configuration working perfectly. The operator wants me to send a transaction ID (number) together with the message (Extra Service section - XSER) I have read the manual and it seems I can use the “binfo” parameter when sending the message using http interface. Has anyone tried it before? Do I need to change the Kannel configuration? In addition in case there is a problem with the transaction ID the operator will send me a NACK response. What will be the Kannel response via http and behavior? Thanks in advance, Oren Ein-Gal
binfo and NACK Status
Hello list, I have a Kannel version 1.4.1 with EMI2 configuration working perfectly. The operator wants me to send a transaction ID (number) together with the message (Extra Service section - XSER) I have read the manual and it seems I can use the binfo parameter when sending the message using http interface. Has anyone tried it before? Do I need to change the Kannel configuration? In addition in case there is a problem with the transaction ID the operator will send me a NACK response. What will be the Kannel response via http and behavior? Thanks in advance, Oren Ein-Gal
