Kannel Hardware Requirements/load
Dear All, I am currently running Kannel on a testing sever ([EMAIL PROTECTED] w/512RAM) and using Kannel via Cygwin. However, we will start a new service with 5-10 SMSC connections and estimated 10-20K msgs/day. can you please advice if this server is capable of handling this service?, if not, what hardware will need? I've looked around for such data, but didn't find anything useful, maybe if each of us shared Hardware/Traffic handled/connection/other things info, we can create somekind of matrix and make it public for other users. Thanks, Hanna Kreitem
Sending a Wap PUSH sms to a destination port
How do I send a wap push to a destination port? I have a MIDP 2.0 application registered at sms://:1669, how do I format a wap push message so that the application activates? I can send regular sl and si messages just fine thought. Regards, Oscar
Kannels (CVS) + mblox
Hi all, I am setting up a connection with mblox(SMPP) in order to provide services in countries where it's difficult for us to be directly connected with the operators. The cvs version seems to include the mblox additions that were available as patches for older versions of kannel, and in general I am able to use the extra functionality ok. What I am looking for is for any pointers on things to watch/avoid when talking to mblox with kannel, from users that have experience with this, before I go to deep with my kannel setup/apps to be able to fix problems properly. thanks in advance, Kyriacos Sakkas -- Kyriacos Sakkas Development Team Netsmart Tel: + 357 22 452565 Fax: + 357 22 452566 Email: [EMAIL PROTECTED] http://www.netsmart.com.cy Taking Business to a New Level! ** Confidentiality Notice: The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution, or copying of this email message is strictly prohibited. If you think that you have received this email message in error, please email the sender at [EMAIL PROTECTED] **
Kannel+ GSM Modem + orange connection
Hello Who can tell me the best GSM modem which can be used with kannel To handle MO/MT SMS message from an orange connection without a big deal Thanks -Message d'origine- De : Kyriacos Sakkas [mailto:[EMAIL PROTECTED] Envoyé : mardi 21 mars 2006 11:49 À : users@kannel.org Objet : Kannels (CVS) + mblox Hi all, I am setting up a connection with mblox(SMPP) in order to provide services in countries where it's difficult for us to be directly connected with the operators. The cvs version seems to include the mblox additions that were available as patches for older versions of kannel, and in general I am able to use the extra functionality ok. What I am looking for is for any pointers on things to watch/avoid when talking to mblox with kannel, from users that have experience with this, before I go to deep with my kannel setup/apps to be able to fix problems properly. thanks in advance, Kyriacos Sakkas -- Kyriacos Sakkas Development Team Netsmart Tel: + 357 22 452565 Fax: + 357 22 452566 Email: [EMAIL PROTECTED] http://www.netsmart.com.cy Taking Business to a New Level! ** Confidentiality Notice: The information contained in this email message may be privileged, confidential and protected from disclosure. If you are not the intended recipient, any dissemination, distribution, or copying of this email message is strictly prohibited. If you think that you have received this email message in error, please email the sender at [EMAIL PROTECTED] ** [E-Mail sent by Pognon Lorys from Paris, France http://www.locatrix.com/emtags.php at 11:53 AM]
Re: Sending a Wap PUSH sms to a destination port
Hi, On Tue, Mar 21, 2006, Oscar Elfving wrote: How do I send a wap push to a destination port? I have a MIDP 2.0 application registered at sms://:1669, how do I format a wap push message so that the application activates? The destination port is in the UDH, the following link has some samples: http://www.nowsms.com/framer.htm?http://www.nowsms.com/discus/messages/132/518.html I suggest you build your own UDH and message and send them via the HTTP interface (via the sendsms CGI). The general format of UDH is specified in GSM 03.40 (ETSI) or 23040 (3GPP). I can send regular sl and si messages just fine thought. You can see the format of the outgoing messages (UDH and text) in the bearerbox access log. The UDH of a WAP PUSH (which implies you're doing WAP over SM) is usually logged as: udh:7:0605040B8423F0 The 0B84 and 23F0 destination and source ports are reserved by IANA (http://www.iana.com/assignments/port-numbers): wap-push2948/tcp WAP PUSH wap-push2948/udp WAP PUSH wap-wsp9200/tcpWAP connectionless session service wap-wsp9200/udpWAP connectionless session service You should pick a high port number to avoid landing on a reserved port. However, if you send it to another destination port, it won't be decoded as a WAP PUSH anymore (the terminal won't act upon the contents and interpret the payload as being connection less WSP). But if you're doing MIDP 2, I understand you might not be interested in WAP PUSH, but in the general payload of the SM. Cheers, -- Loïc Minier [EMAIL PROTECTED] Current Earth status: NOT DESTROYED
Re: Kannel Hardware Requirements/load
Hanna, Don't even think about using Cygwin on a production environment. The threading works horrible and you'll lose a lot of messages even under moderate load. I'd recommend you to use an enterprise-grade Linux distro on decent hardware. My favorite is CentOS (a free RHEL clone built from sources and with the same stability). As an example, we are handling 150-200K messages daily, 15 SMPP connections and even 3 VPN links on a Celeron 1.6 Ghz w/512 Mb RAM and we never have a load issue. I think we could easily double that figures and still be fine. Hope it helps. On 3/21/06, Hanna Kreitem [EMAIL PROTECTED] wrote: Dear All, I am currently running Kannel on a testing sever ([EMAIL PROTECTED] w/512RAM) and using Kannel via Cygwin. However, we will start a new service with 5-10 SMSC connections and estimated 10-20K msgs/day. can you please advice if this server is capable of handling this service?, if not, what hardware will need? I've looked around for such data, but didn't find anything useful, maybe if each of us shared Hardware/Traffic handled/connection/other things info, we can create somekind of matrix and make it public for other users. Thanks, Hanna Kreitem -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/
Service-type in kannel
Hello, Weare tryingto use kannel as gateway between SMSC's. here is ourlog file 2006-03-21 15:28:09 [1342] [7] DEBUG: SMPP[huawei]: Got PDU:2006-03-21 15:28:09 [1342] [7] DEBUG: SMPP PDU 12f320 dump:2006-03-21 15:28:09 [1342] [7] DEBUG: type_name: deliver_sm2006-03-21 15:28:09 [1342] [7] DEBUG: command_id: 5 = 0x00052006-03-21 15:28:09 [1342] [7] DEBUG: command_status: 0 = 0x2006-03-21 15:28:09 [1342] [7] DEBUG: sequence_number: 19634853 = 0x012b9aa52006-03-21 15:28:09 [1342] [7] DEBUG: service_type: "4098"2006-03-21 15:28:09 [1342] [7] DEBUG: source_addr_ton: 1 = 0x00012006-03-21 15:28:09 [1342] [7] DEBUG: source_addr_npi: 1 = 0x00012006-03-21 15:28:09 [1342] [7] DEBUG: source_addr: "99590250141"2006-03-21 15:28:09 [1342] [7] DEBUG: dest_addr_ton: 1 = 0x00012006-03-21 15:28:09 [1342] [7] DEBUG: dest_addr_npi: 1 = 0x00012006-03-21 15:28:09 [1342] [7] DEBUG: destination_addr: "99599166766"2006-03-21 15:28:09 [1342] [7] DEBUG: esm_class: 0 = 0x2006-03-21 15:28:09 [1342] [7] DEBUG: protocol_id: 0 = 0x2006-03-21 15:28:09 [1342] [7] DEBUG: priority_flag: 0 = 0x2006-03-21 15:28:09 [1342] [7] DEBUG: schedule_delivery_time: NULL2006-03-21 15:28:09 [1342] [7] DEBUG: validity_period: NULL2006-03-21 15:28:09 [1342] [7] DEBUG: registered_delivery: 0 = 0x2006-03-21 15:28:09 [1342] [7] DEBUG: replace_if_present_flag: 0 = 0x2006-03-21 15:28:09 [1342] [7] DEBUG: data_coding: 0 = 0x2006-03-21 15:28:09 [1342] [7] DEBUG: sm_default_msg_id: 0 = 0x2006-03-21 15:28:09 [1342] [7] DEBUG: sm_length: 16 = 0x00102006-03-21 15:28:09 [1342] [7] DEBUG: short_message: " Telephone! "2006-03-21 15:28:09 [1342] [7] DEBUG: SMPP PDU dump ends. 2006-03-21 15:28:09 [1342] [7] DEBUG: SMPP[huawei]: Sending PDU:2006-03-21 15:28:09 [1342] [7] DEBUG: SMPP PDU 12f400 dump:2006-03-21 15:28:09 [1342] [7] DEBUG: type_name: deliver_sm_resp2006-03-21 15:28:09 [1342] [7] DEBUG: command_id: 2147483653 = 0x80052006-03-21 15:28:09 [1342] [7] DEBUG: command_status: 0 = 0x2006-03-21 15:28:09 [1342] [7] DEBUG: sequence_number: 19634853 = 0x012b9aa52006-03-21 15:28:09 [1342] [7] DEBUG: message_id: NULL2006-03-21 15:28:09 [1342] [7] DEBUG: SMPP PDU dump ends.2006-03-21 15:28:09 [1342] [8] DEBUG: SMPP[magtimotor]: Sending PDU:2006-03-21 15:28:09 [1342] [8] DEBUG: SMPP PDU 12f320 dump:2006-03-21 15:28:09 [1342] [8] DEBUG: type_name: submit_sm2006-03-21 15:28:09 [1342] [8] DEBUG: command_id: 4 = 0x00042006-03-21 15:28:09 [1342] [8] DEBUG: command_status: 0 = 0x2006-03-21 15:28:09 [1342] [8] DEBUG: sequence_number: 2 = 0x00022006-03-21 15:28:09 [1342] [8] DEBUG: service_type: "4098"2006-03-21 15:28:09 [1342] [8] DEBUG: source_addr_ton: 1 = 0x00012006-03-21 15:28:09 [1342] [8] DEBUG: source_addr_npi: 1 = 0x00012006-03-21 15:28:09 [1342] [8] DEBUG: source_addr: "99590250141"2006-03-21 15:28:09 [1342] [8] DEBUG: dest_addr_ton: 1 = 0x00012006-03-21 15:28:09 [1342] [8] DEBUG: dest_addr_npi: 1 = 0x00012006-03-21 15:28:09 [1342] [8] DEBUG: destination_addr: "99599166766"2006-03-21 15:28:09 [1342] [8] DEBUG: esm_class: 3 = 0x00032006-03-21 15:28:09 [1342] [8] DEBUG: protocol_id: 0 = 0x2006-03-21 15:28:09 [1342] [8] DEBUG: priority_flag: 0 = 0x2006-03-21 15:28:09 [1342] [8] DEBUG: schedule_delivery_time: NULL2006-03-21 15:28:09 [1342] [8] DEBUG: validity_period: NULL2006-03-21 15:28:09 [1342] [8] DEBUG: registered_delivery: 0 = 0x2006-03-21 15:28:09 [1342] [8] DEBUG: replace_if_present_flag: 0 = 0x2006-03-21 15:28:09 [1342] [8] DEBUG: data_coding: 0 = 0x2006-03-21 15:28:09 [1342] [8] DEBUG: sm_default_msg_id: 0 = 0x2006-03-21 15:28:09 [1342] [8] DEBUG: sm_length: 16 = 0x00102006-03-21 15:28:09 [1342] [8] DEBUG: short_message: " Telephone! "2006-03-21 15:28:09 [1342] [8] DEBUG: SMPP PDU dump ends.2006-03-21 15:28:09 [1342] [8] DEBUG: SMPP[magtimotor]: Got PDU:2006-03-21 15:28:09 [1342] [8] DEBUG: SMPP PDU 12fc70 dump:2006-03-21 15:28:09 [1342] [8] DEBUG: type_name: submit_sm_resp2006-03-21 15:28:09 [1342] [8] DEBUG: command_id: 2147483652 = 0x80042006-03-21 15:28:09 [1342] [8] DEBUG: command_status: 21 = 0x00152006-03-21 15:28:09 [1342] [8] DEBUG: sequence_number: 2 = 0x00022006-03-21 15:28:09 [1342] [8] DEBUG: message_id: NULL2006-03-21 15:28:09 [1342] [8] DEBUG: SMPP PDU dump ends. 2006-03-21 15:28:09 [1342] [8] ERROR: SMPP[magtimotor]: SMSC returned error code 0x0015 (Invalid Service Type) in response to submit_sm. should we use service-type option or there is an other way? in our case it was not effective here is our config file: group = coreadmin-port = 13000admin-password = barstatus-password = fooadmin-deny-ip = ""admin-allow-ip = ""log-file = "/var/log/kannel/kannel.log"log-level = 0access-log = "/var/log/kannel/access.log"smsbox-port = 13001box-allow-ip = "*.*.*.*"store-file =
Re: Service-type in kannel
Ask your SMSC operator about the correct value for Service Type. Obviously they are expecting something different than CMT. Hope it helps, On 3/6/05, Vano Porchkhidze [EMAIL PROTECTED] wrote: Hello, We are trying to use kannel as gateway between SMSC's. here is our log file 2006-03-21 15:28:09 [1342] [7] DEBUG: SMPP[huawei]: Got PDU: 2006-03-21 15:28:09 [1342] [7] DEBUG: SMPP PDU 12f320 dump: 2006-03-21 15:28:09 [1342] [7] DEBUG: type_name: deliver_sm 2006-03-21 15:28:09 [1342] [7] DEBUG: command_id: 5 = 0x0005 2006-03-21 15:28:09 [1342] [7] DEBUG: command_status: 0 = 0x 2006-03-21 15:28:09 [1342] [7] DEBUG: sequence_number: 19634853 = 0x012b9aa5 2006-03-21 15:28:09 [1342] [7] DEBUG: service_type: 4098 2006-03-21 15:28:09 [1342] [7] DEBUG: source_addr_ton: 1 = 0x0001 2006-03-21 15:28:09 [1342] [7] DEBUG: source_addr_npi: 1 = 0x0001 2006-03-21 15:28:09 [1342] [7] DEBUG: source_addr: 99590250141 2006-03-21 15:28:09 [1342] [7] DEBUG: dest_addr_ton: 1 = 0x0001 2006-03-21 15:28:09 [1342] [7] DEBUG: dest_addr_npi: 1 = 0x0001 2006-03-21 15:28:09 [1342] [7] DEBUG: destination_addr: 99599166766 2006-03-21 15:28:09 [1342] [7] DEBUG: esm_class: 0 = 0x 2006-03-21 15:28:09 [1342] [7] DEBUG: protocol_id: 0 = 0x 2006-03-21 15:28:09 [1342] [7] DEBUG: priority_flag: 0 = 0x 2006-03-21 15:28:09 [1342] [7] DEBUG: schedule_delivery_time: NULL 2006-03-21 15:28:09 [1342] [7] DEBUG: validity_period: NULL 2006-03-21 15:28:09 [1342] [7] DEBUG: registered_delivery: 0 = 0x 2006-03-21 15:28:09 [1342] [7] DEBUG: replace_if_present_flag: 0 = 0x 2006-03-21 15:28:09 [1342] [7] DEBUG: data_coding: 0 = 0x 2006-03-21 15:28:09 [1342] [7] DEBUG: sm_default_msg_id: 0 = 0x 2006-03-21 15:28:09 [1342] [7] DEBUG: sm_length: 16 = 0x0010 2006-03-21 15:28:09 [1342] [7] DEBUG: short_message:Telephone! 2006-03-21 15:28:09 [1342] [7] DEBUG: SMPP PDU dump ends. 2006-03-21 15:28:09 [1342] [7] DEBUG: SMPP[huawei]: Sending PDU: 2006-03-21 15:28:09 [1342] [7] DEBUG: SMPP PDU 12f400 dump: 2006-03-21 15:28:09 [1342] [7] DEBUG: type_name: deliver_sm_resp 2006-03-21 15:28:09 [1342] [7] DEBUG: command_id: 2147483653 = 0x8005 2006-03-21 15:28:09 [1342] [7] DEBUG: command_status: 0 = 0x 2006-03-21 15:28:09 [1342] [7] DEBUG: sequence_number: 19634853 = 0x012b9aa5 2006-03-21 15:28:09 [1342] [7] DEBUG: message_id: NULL 2006-03-21 15:28:09 [1342] [7] DEBUG: SMPP PDU dump ends. 2006-03-21 15:28:09 [1342] [8] DEBUG: SMPP[magtimotor]: Sending PDU: 2006-03-21 15:28:09 [1342] [8] DEBUG: SMPP PDU 12f320 dump: 2006-03-21 15:28:09 [1342] [8] DEBUG: type_name: submit_sm 2006-03-21 15:28:09 [1342] [8] DEBUG: command_id: 4 = 0x0004 2006-03-21 15:28:09 [1342] [8] DEBUG: command_status: 0 = 0x 2006-03-21 15:28:09 [1342] [8] DEBUG: sequence_number: 2 = 0x0002 2006-03-21 15:28:09 [1342] [8] DEBUG: service_type: 4098 2006-03-21 15:28:09 [1342] [8] DEBUG: source_addr_ton: 1 = 0x0001 2006-03-21 15:28:09 [1342] [8] DEBUG: source_addr_npi: 1 = 0x0001 2006-03-21 15:28:09 [1342] [8] DEBUG: source_addr: 99590250141 2006-03-21 15:28:09 [1342] [8] DEBUG: dest_addr_ton: 1 = 0x0001 2006-03-21 15:28:09 [1342] [8] DEBUG: dest_addr_npi: 1 = 0x0001 2006-03-21 15:28:09 [1342] [8] DEBUG: destination_addr: 99599166766 2006-03-21 15:28:09 [1342] [8] DEBUG: esm_class: 3 = 0x0003 2006-03-21 15:28:09 [1342] [8] DEBUG: protocol_id: 0 = 0x 2006-03-21 15:28:09 [1342] [8] DEBUG: priority_flag: 0 = 0x 2006-03-21 15:28:09 [1342] [8] DEBUG: schedule_delivery_time: NULL 2006-03-21 15:28:09 [1342] [8] DEBUG: validity_period: NULL 2006-03-21 15:28:09 [1342] [8] DEBUG: registered_delivery: 0 = 0x 2006-03-21 15:28:09 [1342] [8] DEBUG: replace_if_present_flag: 0 = 0x 2006-03-21 15:28:09 [1342] [8] DEBUG: data_coding: 0 = 0x 2006-03-21 15:28:09 [1342] [8] DEBUG: sm_default_msg_id: 0 = 0x 2006-03-21 15:28:09 [1342] [8] DEBUG: sm_length: 16 = 0x0010 2006-03-21 15:28:09 [1342] [8] DEBUG: short_message:Telephone! 2006-03-21 15:28:09 [1342] [8] DEBUG: SMPP PDU dump ends. 2006-03-21 15:28:09 [1342] [8] DEBUG: SMPP[magtimotor]: Got PDU: 2006-03-21 15:28:09 [1342] [8] DEBUG: SMPP PDU 12fc70 dump: 2006-03-21 15:28:09 [1342] [8] DEBUG: type_name: submit_sm_resp 2006-03-21 15:28:09 [1342] [8] DEBUG: command_id: 2147483652 = 0x8004 2006-03-21 15:28:09 [1342] [8] DEBUG: command_status: 21 = 0x0015 2006-03-21 15:28:09 [1342] [8] DEBUG: sequence_number: 2 = 0x0002 2006-03-21 15:28:09 [1342] [8] DEBUG: message_id: NULL 2006-03-21 15:28:09 [1342] [8] DEBUG: SMPP PDU dump ends. 2006-03-21 15:28:09 [1342] [8] ERROR: SMPP[magtimotor]: SMSC returned error code 0x0015 (Invalid Service Type) in response to submit_sm. should we use service-type
Speed not detected,bearer box not running.
I am not able to run 1600 nokia as smsc.I have a doubt that it may be because of speed not being detected.I commented the speed parameter in conf file and foll is the output, I have a doubt that it may be because of speed..I commented the speed line and tried and foll is the output, 2006-03-21 12:43:47 [4438] [0] INFO: Debug_lvl = 1, log_file = none, log_lvl = 0 2006-03-21 12:43:47 [4438] [0] WARNING: DLR: using default 'internal' for storag e type. 2006-03-21 12:43:47 [4438] [0] INFO: DLR using storage type: internal 2006-03-21 12:43:47 [4438] [0] INFO: HTTP: Opening server at port 13000. 2006-03-21 12:43:47 [4438] [0] INFO: BOXC: 'smsbox-max-pending' not set, using d efault (100). 2006-03-21 12:43:48 [4438] [0] INFO: DLR rerouting for smsc id FAKE disabled. 2006-03-21 12:43:48 [4438] [0] INFO: DLR rerouting for smsc id (null) disabled . 2006-03-21 12:43:48 [4438] [0] INFO: AT2[/dev/ttyUSB0]: configuration shows mode mtype nokiaphone 2006-03-21 12:43:48 [4438] [0] INFO: AT2[/dev/ttyUSB0]: read modem definition fo r Nokia Phone 2006-03-21 12:43:48 [4438] [0] INFO: 2006-03-21 12:43:48 [4438] [0] INFO: Kannel bearerbox II version 1.4.0 starting 2006-03-21 12:43:48 [4438] [7] INFO: AT2[/dev/ttyUSB0]: trying to use speed 960 0 from modem definition 2006-03-21 12:43:48 [4438] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2006-03-21 12:43:48 [4438] [0] INFO: MAIN: Start-up done, entering mainloop 2006-03-21 12:43:51 [4438] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 9600 2006-03-21 12:44:05 [4438] [7] INFO: AT2[/dev/ttyUSB0]: closing device 2006-03-21 12:44:05 [4438] [7] INFO: AT2[/dev/ttyUSB0]: speed in modem definition don't work, will autodetect 2006-03-21 12:44:05 [4438] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2006-03-21 12:44:10 [4438] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 115200 2006-03-21 12:44:24 [4438] [7] INFO: AT2[/dev/ttyUSB0]: closing device 2006-03-21 12:44:24 [4438] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2006-03-21 12:44:29 [4438] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 57600 2006-03-21 12:44:43 [4438] [7] INFO: AT2[/dev/ttyUSB0]: closing device 2006-03-21 12:44:43 [4438] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2006-03-21 12:44:48 [4438] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 38400 2006-03-21 12:45:02 [4438] [7] INFO: AT2[/dev/ttyUSB0]: closing device 2006-03-21 12:45:02 [4438] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2006-03-21 12:45:07 [4438] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 19200 2006-03-21 12:45:21 [4438] [7] INFO: AT2[/dev/ttyUSB0]: closing device 2006-03-21 12:45:21 [4438] [7] INFO: AT2[/dev/ttyUSB0]: opening device 2006-03-21 12:45:26 [4438] [7] INFO: AT2[/dev/ttyUSB0]: speed set to 9600 2006-03-21 12:45:40 [4438] [7] INFO: AT2[/dev/ttyUSB0]: closing device 2006-03-21 12:45:40 [4438] [7] INFO: AT2[/dev/ttyUSB0]: cannot detect speed the last lines repeating.. Does this mean there is a problem with speed?How can I rectify? Regards, Rashmi. -- View this message in context: http://www.nabble.com/Speed-not-detected%2Cbearer-box-not-running.-t1317445.html#a3512757 Sent from the Kannel - User forum at Nabble.com.
Re: Kannel Hardware Requirements/load
thank a lot for your feedback, I'll defenetly switch to a real Linux. On Tuesday 21 March 2006 10:33, Alejandro Guerrieri wrote: Hanna, Don't even think about using Cygwin on a production environment. The threading works horrible and you'll lose a lot of messages even under moderate load. I'd recommend you to use an enterprise-grade Linux distro on decent hardware. My favorite is CentOS (a free RHEL clone built from sources and with the same stability). As an example, we are handling 150-200K messages daily, 15 SMPP connections and even 3 VPN links on a Celeron 1.6 Ghz w/512 Mb RAM and we never have a load issue. I think we could easily double that figures and still be fine. Hope it helps. On 3/21/06, Hanna Kreitem [EMAIL PROTECTED] wrote: Dear All, I am currently running Kannel on a testing sever ([EMAIL PROTECTED] w/512RAM) and using Kannel via Cygwin. However, we will start a new service with 5-10 SMSC connections and estimated 10-20K msgs/day. can you please advice if this server is capable of handling this service?, if not, what hardware will need? I've looked around for such data, but didn't find anything useful, maybe if each of us shared Hardware/Traffic handled/connection/other things info, we can create somekind of matrix and make it public for other users. Thanks, Hanna Kreitem -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/
Kannel as SMS relay ?
Hi! I got a question regarding Kannel's ability to act as an SMS relay. I got this setup: ___ A -| SMS-C | GSM-network B -|___| Terminals A and B are clients that talks CIMD2 (or SMPP). The problem is that the SMSC only takes one connection at the time. The terminals have to wait on each other to release the connection to SMS-C before proceeding. Now I wonder if I can set up Kannel like this: ______ A -|Kannel |-| SMS-C | GSM-network B -|___| |___| This way, A and B would be possible to send SMS all the time. Is this possible with Kannel? Many Thanks, Jon Bjoerkeback
smsbox response
I'm trying to set a sms-service that don't have to respond anything. I meant the service don't need to send an answer to the sender. I used a get-url to invoque the cgi-bin script, or a exec to run the script, but if the scripts don´t return anything (like they do) the smsbox respond with an error to the sender. Is there an option to invoke a script on a incoming msg without the need to respond to it? thanks for your help, Leonardo.
Re: smsbox response
Check the User Guide for the max-messages configuration directive. Regards, On 3/21/06, Leonardo Torrella [EMAIL PROTECTED] wrote: I'm trying to set a sms-service that don't have to respond anything. I meant the service don't need to send an answer to the sender. I used a get-url to invoque the cgi-bin script, or a exec to run the script, but if the scripts don´t return anything (like they do) the smsbox respond with an error to the sender. Is there an option to invoke a script on a incoming msg without the need to respond to it? thanks for your help, Leonardo. -- Alejandro Guerrieri Magicom http://www.magicom-bcn.net/
RE: Kannel as SMS relay ?
The short answer: Yes, this is possible. The trick here is that Kannel doesn't accept CIMD2 nor SMPP incoming connections natively. The only thing you will have to do here is rewrite the A B terminals to talk Kannel's HTTP protocol. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jon Björkebäck Sent: dinsdag 21 maart 2006 19:06 To: users@kannel.org Subject: Kannel as SMS relay ? Hi! I got a question regarding Kannel's ability to act as an SMS relay. I got this setup: ___ A -| SMS-C | GSM-network B -|___| Terminals A and B are clients that talks CIMD2 (or SMPP). The problem is that the SMSC only takes one connection at the time. The terminals have to wait on each other to release the connection to SMS-C before proceeding. Now I wonder if I can set up Kannel like this: ______ A -|Kannel |-| SMS-C | GSM-network B -|___| |___| This way, A and B would be possible to send SMS all the time. Is this possible with Kannel? Many Thanks, Jon Bjoerkeback
Nokia Smart Messaging using Kannel
Hello I have been trying to find some info. on sending the Nokia Smart Messages using kannel gateway. I am not able to find anything in this regard. Can somebody who did this help on how to start on, or refer to some useful info/mails. Thanks a lot Ajay
