RE: Need help SMPP PDU Error
-Original Message- From: eddie [mailto:[EMAIL PROTECTED]] I am having this problem with my SMPP v3.4 connection. Seems to work ok with cygwin 1.0.3 version but not withe linux redhat 1.2.0 version. It tells me about unknown PDU type. Error Logs: 2002-08-28 17:18:07 [4] ERROR: Unknown SMPP_PDU type, internal error. 2002-08-28 17:18:07 [4] ERROR: SMPP[Digi]: PDU unpacking failed. 2002-08-28 17:18:07 [4] DEBUG: SMPP[Digi]: Failed PDU follows. 2002-08-28 17:18:07 [4] DEBUG: Octet string at 0x80fd5d8: 2002-08-28 17:18:07 [4] DEBUG: len: 12 2002-08-28 17:18:07 [4] DEBUG: size: 13 2002-08-28 17:18:07 [4] DEBUG: immutable: 0 2002-08-28 17:18:07 [4] DEBUG: data: 80 00 00 00 00 00 00 03 2002-08-28 17:18:07 [4] DEBUG: data: 00 00 00 00 2002-08-28 17:18:07 [4] DEBUG: Octet string dump ends. Make sure you are compiling the same version for both systems. the 0x8000 packet type - generic nack was introduced quite recently and its obivous that the version of Kannel you are running on Linux is not updated with it. -- Oded Arbel m-Wise mobile solutions [EMAIL PROTECTED] +972-9-9581711 (116) +972-67-340014 ::.. Rule of Open-Source Programming #1: Don't whine unless you are going to implement it yourself.
Need help SMPP PDU Error
Hi, I am having this problem with my SMPP v3.4 connection. Seems to work ok with cygwin 1.0.3 version but not withe linux redhat 1.2.0 version. It tells me about unknown PDU type. Error Logs: 2002-08-28 17:18:07 [4] ERROR: Unknown SMPP_PDU type, internal error. 2002-08-28 17:18:07 [4] ERROR: SMPP[Digi]: PDU unpacking failed. 2002-08-28 17:18:07 [4] DEBUG: SMPP[Digi]: Failed PDU follows. 2002-08-28 17:18:07 [4] DEBUG: Octet string at 0x80fd5d8: 2002-08-28 17:18:07 [4] DEBUG: len: 12 2002-08-28 17:18:07 [4] DEBUG: size: 13 2002-08-28 17:18:07 [4] DEBUG: immutable: 0 2002-08-28 17:18:07 [4] DEBUG: data: 80 00 00 00 00 00 00 03 2002-08-28 17:18:07 [4] DEBUG: data: 00 00 00 00 2002-08-28 17:18:07 [4] DEBUG: Octet string dump ends. SMSC config: #Start SMSC group = smsc smsc = smpp smsc-id = Digi #denied-smsc-id = #allowed-smsc-id = preferred-smsc-id = Digi #allowed-prefix = #denied-prefix = #preferred-prefix = #alt-charset = host = 210.48.196.19 port = 2003 #transceiver-mode = receive-port = 2003 smsc-username = try smsc-password = try1 system-type = VMA interface-version = 34 #address-range = #our-host = #my-number = #enquire-link-interval = #max-pending-submits = #reconnect-delay = #dest-addr-npi = #dest-addr-ton = #source-addr-npi = Can anyone help? #source-addr-ton =
Need help : Modify SEMA OIS 2000 protocol
Dear all, I need some help as the SMSC I need to be connecting to has perverted the OIS 2000 protocol slightly. The only difference is when a connection is first established, it requires an authentication (username/password) to be sent. After that the OIS 2000 standard is the same. Could somebody help me to point out exactly which class file I should be looking at? I have been looking but it looks like a jungle in there. -- Michael Tung @ Work [Product Manager] [EMAIL PROTECTED] mobileExec (M) Sdn Bhd (557748-X) 4th Floor, Wisma RA 12 Jalan Dang Wangi 50100 Kuala Lumpur Malaysia Mob: +60 (13) 351 1100 Tel: +60 (3) 2693 5001 Fax: +60 (3) 2693 5007 Help Desk: +60 (3) 2691 7001 Get ahead, go mobile at www.mobileExec.net Visit our e-community for executives at www.asianExec.com -- --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.370 / Virus Database: 205 - Release Date: 6/5/2002
Re: need help
You also need libxml2-dev package. Caesare Morata wrote: Need a simple answer? Im testing the kannel 1.0.3...I already have a SMSC username , password, ip and port and using a CIMD2 protocol. But when i start the bearerbox, it says that The SMSC Center is not responding. When i do a telnet to the the SMSC Server, I get connected just fine. Can anybody help me? Im also trying the 1.1.6. I downloaded the latest version of libxml2 (libxml2-2.4.21-1.i386.rpm). and installed it on my system. But when i do the ./configure. I get to the part that it is checking if libxml-conf is around. It says no...what's missing? Please help, Thanks, Caesare -- David Chkhartishvili Tel: 995 99 182418
need help
Need a simple answer? Im testing the kannel 1.0.3...I already have a SMSC username , password, ip and port and using a CIMD2 protocol. But when i start the bearerbox, it says that The SMSC Center is not responding. When i do a telnet to the the SMSC Server, I get connected just fine. Can anybody help me? Im also trying the 1.1.6. I downloaded the latest version of libxml2 (libxml2-2.4.21-1.i386.rpm). and installed it on my system. But when i do the ./configure. I get to the part that it is checking if libxml-conf is around. It says no...what's missing? Please help, Thanks, Caesare
Re: Timer expiry- strange behaviour, need help!
Hi, [EMAIL PROTECTED] wrote: This probably means that the phone does not get the message at all. What is your configuration ? wdp-interface-name = * Using real IP address here may help. Aarno
Re: Timer expiry- strange behaviour, need help!
This probably means that the phone does not get the message at all. What is your configuration ? Aarno Hi, my kannel configuration is: # /etc/kannel/kannel.conf group = core admin-port = 13000 wapbox-port = 13002 admin-password = wdp-interface-name = * log_file = /tmp/kannel.log box-deny-ip = *.*.*.* box-allow-ip = 127.0.0.1 access-log = access.log group = wapbox bearerbox-host = localhost log-file = /tmp/wapbox.log syslog-level = none my test-setup includes also an Apache-webserver on another machine. With the Nokia Toolkit the setup works, with my Siemens phone the home- page (http://192.168.0.99/test/index.php) is displayed correctly. After that the output in wapbox.log is: ---snip 2001-12-03 06:50:52 [29] DEBUG: data: 2e 33 0d 0a 58 2d 57 41 .3..X-WA 2001-12-03 06:50:52 [29] DEBUG: data: 50 2d 53 65 73 73 69 6f P-Sessio 2001-12-03 06:50:52 [29] DEBUG: data: 6e 2d 49 44 3a 20 35 0d n-ID: 5. 2001-12-03 06:50:52 [29] DEBUG: data: 0a 0d 0a ... 2001-12-03 06:50:52 [29] DEBUG: Octet string dump ends. 2001-12-03 06:50:52 [29] INFO: WSP: Fetched http://192.168.0.99/test/index.php (text/vnd.wap.wml, charset='') 2001-12-03 06:50:52 [2] DEBUG: WSP: machine 0x81c4e38, state CONNECTED, event S_MethodResult_Req 2001-12-03 06:50:52 [2] DEBUG: WSP: method 26, state PROCESSING, event S_MethodResult_Req 2001-12-03 06:50:52 [5] DEBUG: WTP: resp_machine 26, state RESULT_WAIT, event TR_Result_Req. 2001-12-03 06:50:52 [5] DEBUG: WTP_SEND: add_initiator_address 2001-12-03 06:50:52 [5] DEBUG: WTP 26: New state RESULT_RESP_WAIT 2001-12-03 06:50:52 [2] DEBUG: WSP 5/26: New method state REPLYING 2001-12-03 06:50:52 [2] DEBUG: WSP 5: New state CONNECTED 2001-12-03 06:50:52 [29] DEBUG: Thread 29 (gw/wap-appl.c:fetch_thread) terminates. 2001-12-03 06:50:59 [1] DEBUG: TimerTO_R elapsed. 2001-12-03 06:50:59 [5] DEBUG: WTP: resp_machine 26, state RESULT_RESP_WAIT, event TimerTO_R. 2001-12-03 06:50:59 [5] DEBUG: WTP 26: New state RESULT_RESP_WAIT 2001-12-03 06:51:06 [1] DEBUG: TimerTO_R elapsed. 2001-12-03 06:51:06 [5] DEBUG: WTP: resp_machine 26, state RESULT_RESP_WAIT, event TimerTO_R. 2001-12-03 06:51:06 [5] DEBUG: WTP 26: New state RESULT_RESP_WAIT 2001-12-03 06:51:13 [1] DEBUG: TimerTO_R elapsed. 2001-12-03 06:51:13 [5] DEBUG: WTP: resp_machine 26, state RESULT_RESP_WAIT, event TimerTO_R. 2001-12-03 06:51:13 [5] DEBUG: WTP 26: New state RESULT_RESP_WAIT 2001-12-03 06:51:20 [1] DEBUG: TimerTO_R elapsed. 2001-12-03 06:51:20 [5] DEBUG: WTP: resp_machine 26, state RESULT_RESP_WAIT, event TimerTO_R. 2001-12-03 06:51:20 [5] DEBUG: WTP 26: New state RESULT_RESP_WAIT 2001-12-03 06:51:27 [1] DEBUG: TimerTO_R elapsed. 2001-12-03 06:51:27 [5] DEBUG: WTP: resp_machine 26, state RESULT_RESP_WAIT, event TimerTO_R. 2001-12-03 06:51:27 [5] DEBUG: WTP 26: New state RESULT_RESP_WAIT 2001-12-03 06:51:34 [1] DEBUG: TimerTO_R elapsed. 2001-12-03 06:51:34 [5] DEBUG: WTP: resp_machine 26, state RESULT_RESP_WAIT, event TimerTO_R. 2001-12-03 06:51:34 [5] DEBUG: WTP 26: New state RESULT_RESP_WAIT 2001-12-03 06:51:41 [1] DEBUG: TimerTO_R elapsed. 2001-12-03 06:51:41 [5] DEBUG: WTP: resp_machine 26, state RESULT_RESP_WAIT, event TimerTO_R. 2001-12-03 06:51:41 [5] DEBUG: WTP 26: New state RESULT_RESP_WAIT 2001-12-03 06:51:48 [1] DEBUG: TimerTO_R elapsed. 2001-12-03 06:51:48 [5] DEBUG: WTP: resp_machine 26, state RESULT_RESP_WAIT, event TimerTO_R. 2001-12-03 06:51:48 [5] DEBUG: WTP 26: New state RESULT_RESP_WAIT 2001-12-03 06:51:55 [1] DEBUG: TimerTO_R elapsed. 2001-12-03 06:51:55 [5] DEBUG: WTP: resp_machine 26, state RESULT_RESP_WAIT, event TimerTO_R. 2001-12-03 06:51:55 [5] DEBUG: WTP 26: New state LISTEN 2001-12-03 06:51:55 [5] DEBUG: WTP: Destroying WTPRespMachine 0x81c46b0 (26) 2001-12-03 06:51:55 [2] DEBUG: WSP: machine 0x81c4e38, state CONNECTED, event TR_Abort_Ind 2001-12-03 06:51:55 [2] DEBUG: WSP: method 26, state REPLYING, event TR_Abort_Ind 2001-12-03 06:51:55 [2] DEBUG: WSP 5/26: New method state NULL_METHOD 2001-12-03 06:51:55 [2] DEBUG: Destroying WSPMethodMachine 26 2001-12-03 06:51:55 [2] DEBUG: WSP 5: New state CONNECTED when I click on a link on my page nothing happens. This behavior is not every time the same, sometimes I'm able to access an other page from my homepage but after that the TimerTO_R elapsed messages appear. regards Andreas Kerk -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
Re: Timer expiry- strange behaviour, need help!
My problem: I see server not responding message on the phone after about 40-60 seconds, no home page. I tested the gateway using UP 4.1 browser and I am able to see the homepage on the gateway (from a different computer running UP browser). Hi, I've go the same problems in my test-setup. I used the Nokia Toolkit to test the gateway (Kannel) and the Webserver (Apache) configuration. With the Nokia Toolkit erverything worked. When I configured a RAS and want to access my wap-pages with a real phone (Siemens ME 45) the homepage is fetched by the gateway. This is in contrast to your description, but when I click a link on this page the gateway does not respond any more. In my wapbox.log are the same TimerTO_R elapsed messages. 2001-10-29 16:08:03 [5] DEBUG: WTP 21: New state RESULT_RESP_WAIT 2001-10-29 16:08:05 [1] DEBUG: TimerTO_R elapsed. 2001-10-29 16:08:05 [5] DEBUG: WTP: resp_machine 21, state ... I played with timer-freq variable in the kannel.conf but it does not seem to have any effect. If you solve the problem it would be nice, if you post it in the mailinglist (of course I'll do the same). Andreas Kerk -- GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
