Re: validity period
Without digging much into the code: the function for getting the time is called gw_gmtime, so I guess it works with GMT. That sounds sensible to me, for systems across the world to be synchronized. - Hervé Le jeudi 02 avril 2009 à 15:54 +0200, Elton Hoxha a écrit : My Redhat has a CEST time, so kannel should inherit for its usage what operating system providesright? On Thu, Apr 2, 2009 at 3:47 PM, Hervé Nicol h.ni...@cobratelematics.com wrote: Maybe it's an UTC time defining the validity period, while your time is CET (UTC+1) ? - Hervé Le jeudi 02 avril 2009 à 14:02 +0200, Elton Hoxha a écrit : Hi, Can you have a look on this line please? 2009-04-02 13:57:48 [10020] [6] DEBUG: validity_period: 090402120748000+ This is inside submit_sm. Time is 13:57, but kannel sets it to 12:07 backward. I set the validitytime = 10 (minutes) Thanks Elton
smsc_fake: invalid message syntax from client, ignored
Hi I am new to kannel. I have suceesfully installed kannel and I started the bearer and sms box. when I run the testsmsc client in smsbox I am getting following message WARNING: smsc_fake: invalid message syntax from client, ignored. Can someone help me on this. kannel version : kannel 1.4.3 Operating system : Linux libxml :libxml2-2.7.3 regards Haffiz Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com
Re: Wapbox dies when receiving wappush
Hi Alvaro, I have been using PPG 1.4.3 with no problems. The message you see comes from bearerbox complaining that it cannot read the msg-type of the received PDU, which at this point should be wbxml SMS. You shouldn't need to send user and password, since your trusted-pi = true. Logs look exactly right upto the point told us to die. Config is fine, too. This is weird and not obvious from your logs or config. Can you get an output of your transmitted PAP? BR, Nikos - Original Message - From: Alvaro Cornejo cornejo.alv...@gmail.com To: users users@kannel.org Sent: Friday, April 03, 2009 5:57 AM Subject: Wapbox dies when receiving wappush Hi All I had wap working fine sometime ago with version 1.4.1 and migrate to 1.4.3 but didn't used wap since then. Now that I need to test wap again, wapbox dies after sending a wappush. Can someone giveme a hand on this? In bearerbox there is an Msg packet invalid / Failed to unpack data but there is no more info... BEARERBOX LOG: 2009-04-02 20:33:25 [19363] [33] ERROR: Msg packet was invalid. 2009-04-02 20:33:25 [19363] [33] ERROR: Failed to unpack data! 2009-04-02 20:33:25 [19363] [34] DEBUG: send_msg: sending msg to box: 10.10.5.2 2009-04-02 20:33:25 [19363] [34] DEBUG: Thread 34 (gw/bb_boxc.c:boxc_sender) terminates. 2009-04-02 20:33:25 [19363] [33] DEBUG: Thread 33 (gw/bb_boxc.c:function) terminates. 2009-04-02 20:33:25 [19363] [32] DEBUG: send_msg: sending msg to box: 10.10.5.2 2009-04-02 20:33:25 [19363] [32] DEBUG: boxc_sender: sent message to 10.10.5.2 2009-04-02 20:33:25 [19363] [31] DEBUG: boxc_receiver: got ack WAP BOX LOG: 2009-04-02 20:33:03 [19398] [0] INFO: Added logfile `/var/log/kannel/wapbox.log' with level `0'. 2009-04-02 20:33:03 [19398] [0] INFO: Starting to log to file /var/log/kannel/wapbox.log level 0 2009-04-02 20:33:03 [19398] [0] DEBUG: syslog parameter is none 2009-04-02 20:33:03 [19398] [0] INFO: Logging accesses to '/var/log/kannel/wapaccess.log'. 2009-04-02 20:33:03 [19398] [0] INFO: Started access logfile `/var/log/kannel/wapaccess.log'. 2009-04-02 20:33:03 [19398] [0] INFO: 2009-04-02 20:33:03 [19398] [0] INFO: Kannel wapbox version cvs-20071108 starting up. 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 1 (wap/wsp_session.c:main_thread) 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 2 (wap/wsp_unit.c:main_thread) 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 3 (wap/wsp_push_client.c:main_thread) 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 4 (wap/timers.c:watch_timers) 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 5 (wap/wtp_init.c:main_thread) 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 6 (wap/wtp_resp.c:main_thread) 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 7 (gw/wap-appl.c:main_thread) 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 8 (gw/wap-appl.c:return_replies_thread) 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 9 (gw/wap_push_ota.c:main_thread) 2009-04-02 20:33:03 [19398] [0] INFO: HTTP: Opening server at port 8080. 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 10 (gwlib/fdset.c:poller) 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 11 (gwlib/http.c:server_thread) 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 12 (gw/wap_push_ppg.c:ota_read_thread) 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 13 (gw/wap_push_ppg.c:http_read_thread) 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 14 (gw/wap_push_ppg.c:pap_request_thread) 2009-04-02 20:33:03 [19398] [0] INFO: Connected to bearerbox at localhost port 13002. 2009-04-02 20:33:03 [19398] [0] DEBUG: Started thread 15 (gw/heartbeat.c:heartbeat_thread) 2009-04-02 20:33:03 [19398] [2] DEBUG: Thread 2 (wap/wsp_unit.c:main_thread) maps to pid 19398. 2009-04-02 20:33:03 [19398] [3] DEBUG: Thread 3 (wap/wsp_push_client.c:main_thread) maps to pid 19398. 2009-04-02 20:33:03 [19398] [4] DEBUG: Thread 4 (wap/timers.c:watch_timers) maps to pid 19398. 2009-04-02 20:33:03 [19398] [5] DEBUG: Thread 5 (wap/wtp_init.c:main_thread) maps to pid 19398. 2009-04-02 20:33:03 [19398] [6] DEBUG: Thread 6 (wap/wtp_resp.c:main_thread) maps to pid 19398. 2009-04-02 20:33:03 [19398] [7] DEBUG: Thread 7 (gw/wap-appl.c:main_thread) maps to pid 19398. 2009-04-02 20:33:03 [19398] [1] DEBUG: Thread 1 (wap/wsp_session.c:main_thread) maps to pid 19398. 2009-04-02 20:33:03 [19398] [8] DEBUG: Thread 8 (gw/wap-appl.c:return_replies_thread) maps to pid 19398. 2009-04-02 20:33:03 [19398] [9] DEBUG: Thread 9 (gw/wap_push_ota.c:main_thread) maps to pid 19398. 2009-04-02 20:33:03 [19398] [10] DEBUG: Thread 10 (gwlib/fdset.c:poller) maps to pid 19398. 2009-04-02 20:33:03 [19398] [11] DEBUG: Thread 11 (gwlib/http.c:server_thread) maps to pid 19398. 2009-04-02 20:33:03 [19398] [12] DEBUG: Thread 12 (gw/wap_push_ppg.c:ota_read_thread) maps to pid 19398. 2009-04-02 20:33:03 [19398] [13] DEBUG: Thread 13
Re: Trying to understand how to use Kannel
Also you need an smsc. This is the entry point to carrier SMS network. Thanks! How do I even find an SMSC? I looked online and can't figure out which ones even exist. All I can find is SMS gateways.
Re: The modem always shows connecting
Hi Is it a serial modem? Your cable might be broken or you are using the wrong cable. If it is an USB modem, you might need to install an specific driver If trouble with linux, try to connect the modem to a Win machine and use hyperterminal to test cable/modem/conectivity. Then with that info return to linux and adjust config accordingly. Regards Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com On Thu, Apr 2, 2009 at 11:28 PM, Anand Ayyappan anandayyap...@gmail.com wrote: Hi, I tried using wvdialconf wvdial.conf Output Start : Editing `wvdial.conf'. Scanning your serial ports for a modem. ttyS0*1: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud ttyS0*1: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud ttyS0*1: ATQ0 V1 E1 -- and failed too at 115200, giving up. Modem Port Scan*1: S1 S2 S3 Sorry, no modem was detected! Is it in use by another program? Did you configure it properly with setserial? Please read the FAQ at http://open.nit.ca/wiki/?WvDial If you still have problems, send mail to wvdial-l...@lists.nit.ca. : Output End But its connected to the serial port and switched on Thanks Anand Ayyappan Formal education will make you a living; self-education will make you a fortune. - Jim Rohn Post free classified ads at http://www.getkochi.com
Re: Trying to understand how to use Kannel
Hi SMSC are normally on carrier side. Unless you have a very huge volume of traffic and an operator allow you to connect to them... (Glenayre/Movius/Comverse/Logica) Look for agregators like Clickatell, Textmagic, Smsglobal, Smsjunction, etc. all them will provide you a way to send sms worldwide. Regards Alvaro On Fri, Apr 3, 2009 at 8:29 AM, don rhummy donrhu...@yahoo.com wrote: Also you need an smsc. This is the entry point to carrier SMS network. Thanks! How do I even find an SMSC? I looked online and can't figure out which ones even exist. All I can find is SMS gateways.
Re: Wapbox dies when receiving wappush
Hi Nikos I tried again with the bearer info below but still not working. I updated to latest cvs and still nothing Something I see is that wap info -compared to smsbox info) seems incomplete. There is no info about queue. Is that correct?: Box connections: wapbox, IP 10.10.5.2 (on-line 0d 0h 0m 48s) smsbox:(none), IP 10.10.5.2 (0 queued), (on-line 0d 0h 0m 48s) Also, I'm trying to capture info from network with tcpdump but get nothing: [r...@srvcom1 feat]# netstat -an |grep 8080 tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN [r...@srvcom1 feat]# netstat -an |grep 13002 tcp0 0 0.0.0.0:13002 0.0.0.0:* LISTEN tcp0 0 10.10.5.2:13002 10.10.5.2:48950 ESTABLISHED tcp0 0 10.10.5.2:48950 10.10.5.2:13002 ESTABLISHED [r...@srvcom1 sbin]# tcpdump -vv port \( 13002 or 49102 \) tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 0 packets captured 0 packets received by filter 0 packets dropped by kernel [r...@srvcom1 sbin]# tcpdump -vv port 13002 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 0 packets captured 0 packets received by filter 0 packets dropped by kernel however I can capture packets to 13000 but not ports 13001 [r...@srvcom1 sbin]# tcpdump -vv port 13000 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 09:20:05.883484 IP (tos 0x0, ttl 56, id 28127, offset 0, flags [DF], proto: TCP (6), length: 40) dsl-189-141-68-118-dyn.prod-infinitum.com.mx.50957 srvcom1.smsglobal.com.mx.13000: ., cksum 0x2e73 (correct), 3676648555:3676648555(0) ack 2820572204 win 15008 09:20:05.889837 IP (tos 0x0, ttl 56, id 28128, offset 0, flags [DF], proto: TCP (6), length: 40) dsl-189-141-68-118-dyn.prod-infinitum.com.mx.50957 srvcom1.smsglobal.com.mx.13000: ., cksum 0x23fb (correct), 0:0(0) ack 537 win 17152 09:20:05.896755 IP (tos 0x0, ttl 56, id 28129, offset 0, flags [DF], proto: TCP (6), length: 40) dsl-189-141-68-118-dyn.prod-infinitum.com.mx.50957 srvcom1.smsglobal.com.mx.13000: F, cksum 0x19e3 (correct), 0:0(0) ack 976 win 19296 [r...@srvcom1 sbin]# tcpdump -vv port 13001 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 0 packets captured 0 packets received by filter 0 packets dropped by kernel neither 8080 [r...@srvcom1 sbin]# tcpdump - port 8080 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 0 packets captured 0 packets received by filter 0 packets dropped by kernel [r...@srvcom1 sbin]# tcpdump port 13002 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 0 packets captured 0 packets received by filter 0 packets dropped by kernel What is even more extrange is that after wap dies, port 13002 still in listenong mode.. [r...@srvcom1 feat]# netstat -an |grep 13002 tcp0 0 0.0.0.0:13002 0.0.0.0:* LISTEN [r...@srvcom1 feat]# Any ideas? Thanks for your help time Alvaro |-| Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com 2009/4/3 Nikos Balkanas nbalka...@gmail.com: The only curious thing that I observed is bearer missing. Try to supply that as well: quality-of-service priority=high delivery-method=unconfirmed network-required=true network=gsm bearer-required=true bearer=SMS/ If that fails, then you need a tcpdump, or snoop, to capture the packet sent by your application. BR, Nikos
Re: Wapbox dies when receiving wappush
Hi Al, Hope you don't mind the nickname. Please don't delete the mail, it has useful info (like configuration). Anyway from a previous mail i see that your ppg is listening on port 8080. Therefore to capture your PAP document use (if I remember correctly): tcpdump -nxX host applicationIP port 8080 If you are not seeing anything it means you are not sending anything. To see anything your application must reside on a different machine. You probably cannot capture traffic between wapbox and bearerbox, because they are on the same server. Therefore nothing on ports 13002, 13001, etc. BR, Nikos - Original Message - From: Alvaro Cornejo cornejo.alv...@gmail.com To: Nikos Balkanas nbalka...@gmail.com; users users@kannel.org Sent: Friday, April 03, 2009 6:40 PM Subject: Re: Wapbox dies when receiving wappush Hi Nikos I tried again with the bearer info below but still not working. I updated to latest cvs and still nothing Something I see is that wap info -compared to smsbox info) seems incomplete. There is no info about queue. Is that correct?: Box connections: wapbox, IP 10.10.5.2 (on-line 0d 0h 0m 48s) smsbox:(none), IP 10.10.5.2 (0 queued), (on-line 0d 0h 0m 48s) Also, I'm trying to capture info from network with tcpdump but get nothing: [r...@srvcom1 feat]# netstat -an |grep 8080 tcp0 0 0.0.0.0:80800.0.0.0:* LISTEN [r...@srvcom1 feat]# netstat -an |grep 13002 tcp0 0 0.0.0.0:13002 0.0.0.0:* LISTEN tcp0 0 10.10.5.2:13002 10.10.5.2:48950 ESTABLISHED tcp0 0 10.10.5.2:48950 10.10.5.2:13002 ESTABLISHED [r...@srvcom1 sbin]# tcpdump -vv port \( 13002 or 49102 \) tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 0 packets captured 0 packets received by filter 0 packets dropped by kernel [r...@srvcom1 sbin]# tcpdump -vv port 13002 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 0 packets captured 0 packets received by filter 0 packets dropped by kernel however I can capture packets to 13000 but not ports 13001 [r...@srvcom1 sbin]# tcpdump -vv port 13000 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 09:20:05.883484 IP (tos 0x0, ttl 56, id 28127, offset 0, flags [DF], proto: TCP (6), length: 40) dsl-189-141-68-118-dyn.prod-infinitum.com.mx.50957 srvcom1.smsglobal.com.mx.13000: ., cksum 0x2e73 (correct), 3676648555:3676648555(0) ack 2820572204 win 15008 09:20:05.889837 IP (tos 0x0, ttl 56, id 28128, offset 0, flags [DF], proto: TCP (6), length: 40) dsl-189-141-68-118-dyn.prod-infinitum.com.mx.50957 srvcom1.smsglobal.com.mx.13000: ., cksum 0x23fb (correct), 0:0(0) ack 537 win 17152 09:20:05.896755 IP (tos 0x0, ttl 56, id 28129, offset 0, flags [DF], proto: TCP (6), length: 40) dsl-189-141-68-118-dyn.prod-infinitum.com.mx.50957 srvcom1.smsglobal.com.mx.13000: F, cksum 0x19e3 (correct), 0:0(0) ack 976 win 19296 [r...@srvcom1 sbin]# tcpdump -vv port 13001 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 0 packets captured 0 packets received by filter 0 packets dropped by kernel neither 8080 [r...@srvcom1 sbin]# tcpdump - port 8080 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 0 packets captured 0 packets received by filter 0 packets dropped by kernel [r...@srvcom1 sbin]# tcpdump port 13002 tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes 0 packets captured 0 packets received by filter 0 packets dropped by kernel What is even more extrange is that after wap dies, port 13002 still in listenong mode.. [r...@srvcom1 feat]# netstat -an |grep 13002 tcp0 0 0.0.0.0:13002 0.0.0.0:* LISTEN [r...@srvcom1 feat]# Any ideas? Thanks for your help time Alvaro |-| Envνe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier celular y Nextel en el Perϊ, Mιxico y en mas de 180 paises. Use aplicaciones 2 vias via SMS y GPRS online Visitenos en www.perusms.NET www.smsglobal.com.mx y www.pravcom.com 2009/4/3 Nikos Balkanas nbalka...@gmail.com: The only curious thing that I observed is bearer missing. Try to supply that as well: quality-of-service priority=high delivery-method=unconfirmed network-required=true network=gsm bearer-required=true bearer=SMS/ If that fails, then you need a tcpdump, or snoop, to capture the packet sent by your application. BR, Nikos
Re: Wapbox dies when receiving wappush
Good, how about a more readable output? tcpdump -nxX ... Nikos - Original Message - From: Alvaro Cornejo cornejo.alv...@gmail.com To: Nikos Balkanas nbalka...@gmail.com; users users@kannel.org Sent: Friday, April 03, 2009 6:57 PM Subject: Re: Wapbox dies when receiving wappush I was successfull on capture 13002 packets [r...@srvcom1 sbin]# tcpdump -s 3000 -i lo -vv port \( 13002 or 49102 \) tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 3000 bytes 09:54:26.215644 IP (tos 0x0, ttl 64, id 47394, offset 0, flags [DF], proto: TCP (6), length: 60) srvcom1.smsglobal.com.mx.41842 srvcom1.smsglobal.com.mx.13002: S, cksum 0x8b2d (correct), 695324557:695324557(0) win 32792 mss 16396,sackOK,timestamp 2657056431 0,nop,wscale 7 09:54:26.215666 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 60) srvcom1.smsglobal.com.mx.13002 srvcom1.smsglobal.com.mx.41842: S, cksum 0x4125 (correct), 696060802:696060802(0) ack 695324558 win 32768 mss 16396,sackOK,timestamp 2657056432 2657056431,nop,wscale 7 09:54:26.215681 IP (tos 0x0, ttl 64, id 47395, offset 0, flags [DF], proto: TCP (6), length: 52) srvcom1.smsglobal.com.mx.41842 srvcom1.smsglobal.com.mx.13002: ., cksum 0x2948 (correct), 1:1(0) ack 1 win 257 nop,nop,timestamp 2657056432 2657056432 09:54:55.920767 IP (tos 0x0, ttl 64, id 47396, offset 0, flags [DF], proto: TCP (6), length: 348) srvcom1.smsglobal.com.mx.41842 srvcom1.smsglobal.com.mx.13002: P, cksum 0x1f66 (incorrect (- 0xe5a8), 1:297(296) ack 1 win 257 nop,nop,timestamp 2657086136 2657056432 09:54:55.920789 IP (tos 0x0, ttl 64, id 32051, offset 0, flags [DF], proto: TCP (6), length: 52) srvcom1.smsglobal.com.mx.13002 srvcom1.smsglobal.com.mx.41842: ., cksum 0x4007 (correct), 1:1(0) ack 297 win 265 nop,nop,timestamp 2657086136 2657086136 09:54:55.921008 IP (tos 0x0, ttl 64, id 32052, offset 0, flags [DF], proto: TCP (6), length: 68) srvcom1.smsglobal.com.mx.13002 srvcom1.smsglobal.com.mx.41842: P, cksum 0x1e4e (incorrect (- 0x3fe2), 1:17(16) ack 297 win 265 nop,nop,timestamp 2657086136 2657086136 09:54:55.921016 IP (tos 0x0, ttl 64, id 47397, offset 0, flags [DF], proto: TCP (6), length: 52) srvcom1.smsglobal.com.mx.41842 srvcom1.smsglobal.com.mx.13002: ., cksum 0x3fff (correct), 297:297(0) ack 17 win 257 nop,nop,timestamp 2657086136 2657086136 09:54:55.921191 IP (tos 0x0, ttl 64, id 32053, offset 0, flags [DF], proto: TCP (6), length: 52) srvcom1.smsglobal.com.mx.13002 srvcom1.smsglobal.com.mx.41842: F, cksum 0x3ff6 (correct), 17:17(0) ack 297 win 265 nop,nop,timestamp 2657086136 2657086136 09:54:55.922176 IP (tos 0x0, ttl 64, id 47398, offset 0, flags [DF], proto: TCP (6), length: 64) srvcom1.smsglobal.com.mx.41842 srvcom1.smsglobal.com.mx.13002: P, cksum 0x1e4a (incorrect (- 0x3fe1), 297:309(12) ack 18 win 257 nop,nop,timestamp 2657086137 2657086136 09:54:55.922207 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 40) srvcom1.smsglobal.com.mx.13002 srvcom1.smsglobal.com.mx.41842: R, cksum 0x867b (correct), 696060820:696060820(0) win 0 and from port 8080 [r...@srvcom1 sbin]# tcpdump -s 3000 -i lo -vv port 8080 tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 3000 bytes 09:56:40.675445 IP (tos 0x0, ttl 64, id 34695, offset 0, flags [DF], proto: TCP (6), length: 60) srvcom1.smsglobal.com.mx.55540 srvcom1.smsglobal.com.mx.webcache: S, cksum 0x1dcb (correct), 846136430:846136430(0) win 32792 mss 16396,sackOK,timestamp 2657190889 0,nop,wscale 7 09:56:40.675478 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto: TCP (6), length: 60) srvcom1.smsglobal.com.mx.webcache srvcom1.smsglobal.com.mx.55540: S, cksum 0x5885 (correct), 846819464:846819464(0) ack 846136431 win 32768 mss 16396,sackOK,timestamp 2657190889 2657190889,nop,wscale 7 09:56:40.675500 IP (tos 0x0, ttl 64, id 34696, offset 0, flags [DF], proto: TCP (6), length: 52) srvcom1.smsglobal.com.mx.55540 srvcom1.smsglobal.com.mx.webcache: ., cksum 0x40a9 (correct), 1:1(0) ack 1 win 257 nop,nop,timestamp 2657190889 2657190889 09:56:40.675578 IP (tos 0x0, ttl 64, id 34697, offset 0, flags [DF], proto: TCP (6), length: 1126) srvcom1.smsglobal.com.mx.55540 srvcom1.smsglobal.com.mx.webcache: P, cksum 0x2270 (incorrect (- 0x81bc), 1:1075(1074) ack 1 win 257 nop,nop,timestamp 2657190889 2657190889 09:56:40.675589 IP (tos 0x0, ttl 64, id 62304, offset 0, flags [DF], proto: TCP (6), length: 52) srvcom1.smsglobal.com.mx.webcache srvcom1.smsglobal.com.mx.55540: ., cksum 0x3c67 (correct), 1:1(0) ack 1075 win 273 nop,nop,timestamp 2657190889 2657190889 09:56:40.676943 IP (tos 0x0, ttl 64, id 62305, offset 0, flags [DF], proto: TCP (6), length: 598) srvcom1.smsglobal.com.mx.webcache srvcom1.smsglobal.com.mx.55540: P, cksum 0x2060 (incorrect (- 0x8bab), 1:547(546) ack 1075 win 273 nop,nop,timestamp 2657190890 2657190889 09:56:40.676957 IP (tos 0x0, ttl 64, id 34698, offset 0, flags [DF], proto: TCP (6), length: 52)
Re: The modem always shows connecting
HI, I am using a serial modem. I am able to connect to the modem in windows XP using the configuration COM1, 9600 8-N-1 Some output from Hyperterminal is listed below AT+COPS? +COPS: 0,0,BPL USWEST (Kerala) OK I am using a modem SIM300. Thanks Anand Ayyappan Formal education will make you a living; self-education will make you a fortune. - Jim Rohn Post free classified ads at http://www.getkochi.com
Re: unsubscribe;
unsubscribe;
Re: The modem always shows connecting
Hi, My SMSC log says 2009-04-04 10:27:11 [5835] [6] DEBUG: AT2[/dev/ttyS0]: detecting modem type 2009-04-04 10:27:11 [5835] [6] INFO: AT2[/dev/ttyS0]: opening device 2009-04-04 10:27:11 [5835] [6] DEBUG: AT2[/dev/ttyS0]: device opened 2009-04-04 10:27:12 [5835] [6] DEBUG: AT2[/dev/ttyS0]: device opened 2009-04-04 10:27:12 [5835] [6] INFO: AT2[/dev/ttyS0]: speed set to 9600 2009-04-04 10:27:12 [5835] [6] DEBUG: AT2[/dev/ttyS0]: -- ^M so I think its getting modem information. but after ^M no response. Thanks Anand Ayyappan Formal education will make you a living; self-education will make you a fortune. - Jim Rohn Post free classified ads at http://www.getkochi.com On Sat, Apr 4, 2009 at 6:59 AM, Anand Ayyappan anandayyap...@gmail.comwrote: HI, I am using a serial modem. I am able to connect to the modem in windows XP using the configuration COM1, 9600 8-N-1 Some output from Hyperterminal is listed below AT+COPS? +COPS: 0,0,BPL USWEST (Kerala) OK I am using a modem SIM300. Thanks Anand Ayyappan Formal education will make you a living; self-education will make you a fortune. - Jim Rohn Post free classified ads at http://www.getkochi.com
Re: The modem always shows connecting
Hi, You need to look at the starting bearerbox logs at maximum detail and post them. If that fails, and using Linux, do: dmesg | grep tty That should show you your modem device at boot time. If the kernel doesn't read it, no one will. Then you better use a serial program as Alvaro suggested. If you haven't succeeded with wvdial, download and install minicom. It is very easy to use, similar to Hyperterminal. Set the modem device (/dev/ttyS0) and fire a few ATs. You should see OK if the device/modem are right. BR, Nikos - Original Message - From: Anand Ayyappan To: Alvaro Cornejo Cc: users@kannel.org Sent: Saturday, April 04, 2009 8:00 AM Subject: Re: The modem always shows connecting Hi, My SMSC log says 2009-04-04 10:27:11 [5835] [6] DEBUG: AT2[/dev/ttyS0]: detecting modem type 2009-04-04 10:27:11 [5835] [6] INFO: AT2[/dev/ttyS0]: opening device 2009-04-04 10:27:11 [5835] [6] DEBUG: AT2[/dev/ttyS0]: device opened 2009-04-04 10:27:12 [5835] [6] DEBUG: AT2[/dev/ttyS0]: device opened 2009-04-04 10:27:12 [5835] [6] INFO: AT2[/dev/ttyS0]: speed set to 9600 2009-04-04 10:27:12 [5835] [6] DEBUG: AT2[/dev/ttyS0]: -- ^M so I think its getting modem information. but after ^M no response. Thanks Anand Ayyappan Formal education will make you a living; self-education will make you a fortune. - Jim Rohn Post free classified ads at http://www.getkochi.com On Sat, Apr 4, 2009 at 6:59 AM, Anand Ayyappan anandayyap...@gmail.com wrote: HI, I am using a serial modem. I am able to connect to the modem in windows XP using the configuration COM1, 9600 8-N-1 Some output from Hyperterminal is listed below AT+COPS? +COPS: 0,0,BPL USWEST (Kerala) OK I am using a modem SIM300. Thanks Anand Ayyappan Formal education will make you a living; self-education will make you a fortune. - Jim Rohn Post free classified ads at http://www.getkochi.com
Re: The modem always shows connecting
Hi, I tried r...@ubuntu:~# dmesg | grep tty [0.004000] console [tty0] enabled [1.689374] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [1.690469] 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A I have installed minicom but sorry to say i dont understand how to send commands the minicom window after setting up has a cursor blinking but i am not able to type AT commands Thanks Anand Ayyappan Formal education will make you a living; self-education will make you a fortune. - Jim Rohn Post free classified ads at http://www.getkochi.com
