re:detecting mobile connected to usb
Can you give us the configuration file for detecting of mobile connected to usb port so that any msg sent to it will be displayed on smsbox. please give us the configuration file(smskannel.conf or kannel.conf) regards, Rashmi. -- View this message in context: http://www.nabble.com/re%3Adetecting-mobile-connected-to-usb-t1283830.html#a3413422 Sent from the Kannel - User forum at Nabble.com.
RE: RE: RE: Imp-Problem in using WAP PPG push
Dear Andy, Have you try Service Loading with your contents link in the sl file? The user just press OK or YES confirming proceed of the content loading. Its kind of like MMS delivery. However Im not sure if that is what you are looking for. Best regards, Rayson Lee InnoAge Hong Kong Limited From: Peter Wilson [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 15, 2006 8:59 AM To: Rayson Lee Subject: Re: RE: RE: Imp-Problem in using WAP PPG push Hi Rayson, Just like to check on the wap push, when I use kannel to perform a wap push, it seems like it can only send a link instead. Can I push the content directly to the mobile handset, like handphone to handphone MMS? Thanks, Andy - Original Message - From: Rayson Lee To: 'Nirav doshi' ; users@kannel.org Sent: Wednesday, March 15, 2006 2:26 AM Subject: RE: RE: RE: Imp-Problem in using WAP PPG push Hi Nirav, Looks like its the URL of carriers WAP Push gateway. My guess is that its not being used by Kannel. For sending WAP Push to a phone number, you can put anything there or simply leave it as it is. Are you using test_ppg to test WAP Push or sending HTTP POST request by your own application? What are the exact error messages you got? By the way, Kannel does not support MMS. You may need other software such as Mbuni. Please search the list for more information. Best regards, Rayson Lee InnoAge Hong Kong Limited From: Nirav doshi [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 14, 2006 12:47 AM To: Rayson Lee; users@kannel.org Subject: Re: RE: RE: Imp-Problem in using WAP PPG push Thank u very much I got the soluiton for the problem but now there is one problem that whenever I try for the wap push command given in the userguide. It shows that the message is snd but gives an error Request ignoring and the message havent reached the destination yet. Can u please tell me what is [EMAIL PROTECTED] Should I replace with some other sites? Can u recommend some sites or ways through which i can send a WAP Push? Please do let me know. i m stuck up here? Please also let me know how i can really try to send MMS using kannel. On Fri, 10 Mar 2006 Rayson Lee wrote : Dear Nirav, The system is complaining about the PAP content. However I don't see thing wrong with it. Perhaps you can try set log-level to 0 for wapbox to try getting more information about the problem. Best regards, Rayson Lee InnoAge Hong Kong Limited _ From: Nirav doshi [mailto:[EMAIL PROTECTED] Sent: Friday, March 10, 2006 3:01 PM To: Rayson Lee Subject: Re: RE: Imp-Problem in using WAP PPG push On Thu, 09 Mar 2006 Rayson Lee wrote : Dear Nirav, You don't need to put the full url here: ppg-url = ""> just use ppg-url = ""> Rayson Lee InnoAge Hong Kong Limited _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Nirav doshi Sent: Friday, March 03, 2006 7:29 PM To: users Subject: Imp-Problem in using WAP PPG push Hello I have been trying to send an ppg msg from kannel using the ppg configuration mentioned in the userguide. i m always getting an error in the WAP Box. After opening the initial bearerbox and WAPbox i m running the command ./test_http_server -p 8900 and then on the next terminal running ./test_ppg -q http://localhost:8900/ppgurl iptestppg.xml sl.xml. After running this i m getting an error. 2006-03-03 17:20:19 [13506] [0] INFO: an input without a configuration file assumed 2006-03-03 17:20:19 [13506] [0] DEBUG: using iptestppg.xml as a content file 2006-03-03 17:20:19 [13506] [0] DEBUG: using sl.xml as a control file 2006-03-03 17:20:19 [13506] [0] DEBUG: Started thread 1 (test/test_ppg.c:push_thread) 2006-03-03 17:20:19 [13506] [1] DEBUG: Thread 1 (test/test_ppg.c:push_thread) maps to pid 13506. 2006-03-03 17:20:19 [13506] [1] DEBUG: TEST_PPG: starting to push job 0 2006-03-03 17:20:19 [13506] [1] DEBUG: Started thread 2 (gwlib/fdset.c:poller) 2006-03-03 17:20:19 [13506] [1] DEBUG: Started thread 3 (gwlib/http.c:write_request_thread) 2006-03-03 17:20:19 [13506] [1] DEBUG: push done 2006-03-03 17:20:19 [13506] [3] DEBUG: Thread 3 (gwlib/http.c:write_request_thread) maps to pid 13506. 2006-03-03 17:20:19 [13506] [3] DEBUG: Parsing URL `http://localhost:8080//wappush': 2006-03-03 17:20:19 [13506] [3] DEBUG: Scheme: http:// 2006-03-03 17:20:19 [13506] [3] DEBUG: Host: localhost 2006-03-03 17:20:19 [13506] [3] DEBUG: Port: 8080 2006-03-03 17:20:19 [13506] [3] DEBUG: Username: (null) 2006-03-03 17:20:19 [13506] [3] DEBUG: Password: (null) 2006-03-03 17:20:19 [13506] [3] DEBUG: Path: //wappush 2006-03-03 17:20:19 [13506] [3] DEBUG: Query: (null) 2006-03-03 17:20:19 [13506] [3] DEBUG: Fragment: (null) 2006-03-03 17:20:19 [13506] [3] DEBUG: HTTP: Opening connection to `localhost:8080' (fd=12). 2006-03-03 17:20:19
RE: binfo
Hmmm... I found it... It is the %B parameter. Rene Kluwen Chimit -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Rene Kluwen Sent: donderdag 9 maart 2006 21:24 To: users@kannel.org Subject: binfo Is there a field in the dlr-url string that is set to the binfo value of the (dlr) message? I have an smsc driver that uses this field (soon to come). Rene Kluwen Chimit
Delivery reports and different return smsc
Hello, I have two smsc groups setup with a smsc-id of A and B. A is in transceiver mode and B is in transmitter mode. A is used for general SMS messages and B is used for sending a SMS which bills the user. The default-sender MSISDNs used are different for both SMSCs. I don't control the SMSCs so I can't change or even view the configs. The problem I am having is in getting delivery reports from smsc B. The delivery_sm comes from smsc A and not smsc B. Hopefully these log snippets will explain (I haved used and to protect the guilty): 2006-03-15 19:38:40 [85471] [7] DEBUG: SMPP[B]: Got PDU: 2006-03-15 19:38:40 [85471] [7] DEBUG: SMPP PDU 0x8103e00 dump: 2006-03-15 19:38:40 [85471] [7] DEBUG: type_name: submit_sm_resp 2006-03-15 19:38:40 [85471] [7] DEBUG: command_id: 2147483652 = 0x8004 2006-03-15 19:38:40 [85471] [7] DEBUG: command_status: 0 = 0x 2006-03-15 19:38:40 [85471] [7] DEBUG: sequence_number: 158 = 0x009e 2006-03-15 19:38:40 [85471] [7] DEBUG: message_id: 0E039FCA 2006-03-15 19:38:40 [85471] [7] DEBUG: SMPP PDU dump ends. 2006-03-15 19:38:40 [85471] [7] DEBUG: DLR[internal]: Adding DLR smsc=B, ts=0E039FCA, src=, dst=, mask=31, boxc= 2006-03-15 19:38:40 [85471] [7] DEBUG: SMSC[B]: creating DLR message 2006-03-15 19:38:40 [85471] [7] DEBUG: SMSC[B]: DLR = 2006-03-15 19:38:40 [85471] [12] DEBUG: send_msg: sending msg to box: 127.0.0.1 2006-03-15 19:38:40 [85471] [12] DEBUG: boxc_sender: sent message to 127.0.0.1 2006-03-15 19:38:40 [85471] [11] DEBUG: boxc_receiver: got ack 2006-03-15 19:44:09 [85471] [6] DEBUG: SMPP[A]: Got PDU: 2006-03-15 19:44:09 [85471] [6] DEBUG: SMPP PDU 0x8103f00 dump: 2006-03-15 19:44:09 [85471] [6] DEBUG: type_name: deliver_sm 2006-03-15 19:44:09 [85471] [6] DEBUG: command_id: 5 = 0x0005 2006-03-15 19:44:09 [85471] [6] DEBUG: command_status: 0 = 0x 2006-03-15 19:44:09 [85471] [6] DEBUG: sequence_number: 5 = 0x0005 2006-03-15 19:44:09 [85471] [6] DEBUG: service_type: NULL 2006-03-15 19:44:09 [85471] [6] DEBUG: source_addr_ton: 1 = 0x0001 2006-03-15 19:44:09 [85471] [6] DEBUG: source_addr_npi: 1 = 0x0001 2006-03-15 19:44:09 [85471] [6] DEBUG: source_addr: y 2006-03-15 19:44:09 [85471] [6] DEBUG: dest_addr_ton: 4 = 0x0004 2006-03-15 19:44:09 [85471] [6] DEBUG: dest_addr_npi: 4 = 0x0004 2006-03-15 19:44:09 [85471] [6] DEBUG: destination_addr: 2006-03-15 19:44:09 [85471] [6] DEBUG: esm_class: 4 = 0x0004 2006-03-15 19:44:09 [85471] [6] DEBUG: protocol_id: 0 = 0x 2006-03-15 19:44:09 [85471] [6] DEBUG: priority_flag: 0 = 0x 2006-03-15 19:44:09 [85471] [6] DEBUG: schedule_delivery_time: NULL 2006-03-15 19:44:09 [85471] [6] DEBUG: validity_period: NULL 2006-03-15 19:44:09 [85471] [6] DEBUG: registered_delivery: 0 = 0x 2006-03-15 19:44:09 [85471] [6] DEBUG: replace_if_present_flag: 0 = 0x 2006-03-15 19:44:09 [85471] [6] DEBUG: data_coding: 0 = 0x 2006-03-15 19:44:09 [85471] [6] DEBUG: sm_default_msg_id: 0 = 0x 2006-03-15 19:44:09 [85471] [6] DEBUG: sm_length: 108 = 0x006c 2006-03-15 19:44:09 [85471] [6] DEBUG: short_message: snip packet contents 2006-03-15 19:44:09 [85471] [6] DEBUG: message_state: 3 = 0x0003 2006-03-15 19:44:09 [85471] [6] DEBUG: receipted_message_id: 0E039FCA 2006-03-15 19:44:09 [85471] [6] DEBUG: SMPP PDU dump ends. 2006-03-15 19:44:09 [85471] [6] DEBUG: SMPP[A] handle_pdu, got DLR 2006-03-15 19:44:09 [85471] [6] DEBUG: DLR[internal]: Looking for DLR smsc=A, ts=0E039FCA, dst=y, type=2 2006-03-15 19:44:09 [85471] [6] WARNING: DLR[internal]: DLR for DSTy not found. 2006-03-15 19:44:09 [85471] [6] ERROR: SMPP[A]: got DLR but could not find message or was not interested in it id0E039FCA dst, type2 2006-03-15 19:44:09 [85471] [6] DEBUG: SMPP[A]: Sending PDU: 2006-03-15 19:44:09 [85471] [6] DEBUG: SMPP PDU 0x8103e00 dump: 2006-03-15 19:44:09 [85471] [6] DEBUG: type_name: deliver_sm_resp 2006-03-15 19:44:09 [85471] [6] DEBUG: command_id: 2147483653 = 0x8005 2006-03-15 19:44:09 [85471] [6] DEBUG: command_status: 0 = 0x 2006-03-15 19:44:09 [85471] [6] DEBUG: sequence_number: 5 = 0x0005 2006-03-15 19:44:09 [85471] [6] DEBUG: message_id: NULL 2006-03-15 19:44:09 [85471] [6] DEBUG: SMPP PDU dump ends. I can receive delivery reports fine for SMS send through smsc A. Fixes for me would include always calling the dlr-url regardless of whether the deliver report can find a match, turning off the smsc name match or getting the incoming smsc-id renamed to B or vice-versa. Thanks, Alan
