|
Hi, If it isn’t supposed to be able to send
SMS from the PPG interface, then why does it accept the message and go through
the motions of trying to send it? Other PPGs will send text/plain data as an
SMS…I’d prefer not to have to write special case code for speaking to Kannel
but it looks like I’m going to have to :-/ Brent From: Christian Vandrei
[mailto:[EMAIL PROTECTED] Hi, Hi, This probably the 3rd
time I’ve posted about this and yet I’ve failed to get any response what so
ever. Well, here goes again but with gratuitous details. Here’s what I send to
Kannel: POST / HTTP/1.1Host: demoUser-Agent: testContent-Type: multipart/related; type=application/xml; boundary=WPL38woVbhESdfalYevGqpdzLCsContent-Length: 461--WPL38woVbhESdfalYevGqpdzLCsContent-Type: application/xml; charset=UTF-8<?xml version="1.0"?> <!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 1.0//EN" "http://www.wapforum.org/DTD/pap_1.0.dtd"> <pap><push-message push-id="test837697"><address address-value="WAPPUSH=+61xxx/[EMAIL PROTECTED]"/></push-message></pap>--WPL38woVbhESdfalYevGqpdzLCsContent-Type: text/plainThis is a test--WPL38woVbhESdfalYevGqpdzLCs—
Here’s what Kannel sends in
reply: HTTP/1.1 202 AcceptedServer: Kannel/1.4.0Content-Length: 391Content-Type: application/xml<?xml version="1.0"?><!DOCTYPE pap PUBLIC "-//WAPFORUM//DTD PAP 1.0//EN" "http://www.wapforum.org/DTD/pap_1.0.dtd"><pap><push-response push-id="test837697" sender-name="localhost.localdomain; WAP/1.3 (Kannel/1.4.0)" reply-time="2005-08-21T23:33:20Z" sender-address="/"><response-result code ="1001" desc="The request has been accepted for processing"></response-result></push-response></pap>
Here’s what the log in the
wapbox reads: 2005-08-22 09:33:19 [3452] [11] DEBUG: HTTP: Creating HTTPClient for `192.168.1.53'.2005-08-22 09:33:20 [3452] [14] INFO: PPG: Accept request </> from <192.168.1.53>2005-08-22 09:33:20 [3452] [14] DEBUG: PPG: http_read_thread: pap multipart accepted2005-08-22 09:33:20 [3452] [14] INFO: client address was <+61xxx>, accepted2005-08-22 09:33:20 [3452] [14] DEBUG: PAP COMPILER: doing semantic analysis for address type a phone number2005-08-22 09:33:20 [3452] [14] DEBUG: PAP COMPILER: network orbearer missing, reverting to GSM+SMS2005-08-22 09:33:20 [3452] [14] INFO: reverting to default bearer and network2005-08-22 09:33:20 [3452] [14] DEBUG: PPG: http_read_thread: pap control entity compiled ok2005-08-22 09:33:20 [3452] [14] DEBUG: PPG: transform_message: push message content and headers valid2005-08-22 09:33:20 [3452] [14] DEBUG: PPG: push machine 2 created2005-08-22 09:33:20 [3452] [14] DEBUG: PPG: store_push_data: push machine 2 appended to unit push list2005-08-22 09:33:20 [3452] [14] DEBUG: PPG: send_push_response: telling pi2005-08-22 09:33:20 [3452] [14] DEBUG: HTTP: Resetting HTTPClient for `192.168.1.53'.2005-08-22 09:33:20 [3452] [14] INFO: PPG: handle_push_message: push message accepted for processing2005-08-22 09:33:20 [3452] [14] DEBUG: PPG: OTA request for unit push2005-08-22 09:33:20 [3452] [14] INFO: PPG: unconfirmed push delivered to OTA2005-08-22 09:33:20 [3452] [14] DEBUG: PPG: destroying push machine 22005-08-22 09:33:20 [3452] [9] DEBUG: OTA: event arrived2005-08-22 09:33:20 [3452] [9] DEBUG: OTA: made connectionless session service request2005-08-22 09:33:20 [3452] [2] DEBUG: WSP (UNIT): event arrived2005-08-22 09:33:20 [3452] [2] DEBUG: WSP_UNIT: Connectionless push accepted2005-08-22 09:33:20 [3452] [2] DEBUG: WSP: Mapping `text/plain', WSP 1.2 to 0x0003.2005-08-22 09:33:20 [3452] [2] DEBUG: WSP: Mapping `User-Agent', WSP 1.3 to 0x0029.2005-08-22 09:33:20 [3452] [2] DEBUG: WSP: Mapping `Content-Length', WSP 1.3 to 0x000d.2005-08-22 09:33:20 [3452] [2] DEBUG: WSP: Mapping `Content-Type', WSP 1.3 to 0x0011.2005-08-22 09:33:20 [3452] [2] DEBUG: WSP: Mapping `Encoding-Version', WSP 1.3 to 0x0043.2005-08-22 09:33:20 [3452] [2] DEBUG: WDP (wapbox): delivering 1 segments to bearerbox2005-08-22 09:33:20 [3452] [2] DEBUG: WSP (UNIT): delivering to wdp2005-08-22 09:33:20 [3452] [10] DEBUG: HTTP: Destroying HTTPClient area 0x9d804f0.2005-08-22 09:33:20 [3452] [10] DEBUG: HTTP: Destroying HTTPClient for `192.168.1.53'.2005-08-22 09:33:20 [3452] [0] WARNING: Received other message than wdp/admin, ignoring!
And here’s what the
bearerbox displays: 2005-08-22 09:33:20 [3410] [15] DEBUG: boxc_receiver: got sms from wapbox2005-08-22 09:33:20 [3410] [15] DEBUG: send_msg: sending msg to box: <127.0.0.1>2005-08-22 09:33:22 [3410] [6] DEBUG: AT2[/dev/ttyS0]: TP-Validity-Period: 24.0 hours2005-08-22 09:33:22 [3410] [6] DEBUG: AT2[/dev/ttyS0]: --> AT+CMGS=49^M2005-08-22 09:33:22 [3410] [6] DEBUG: AT2[/dev/ttyS0]: <-- >2005-08-22 09:33:22 [3410] [6] DEBUG: AT2[/dev/ttyS0]: send command status: 12005-08-22 09:33:22 [3410] [6] DEBUG: AT2[/dev/ttyS0]: --> 0051000B911614479064F40004A7230605040B8423F002060B83A974657374008D8EC39354686973206973206120746573742005-08-22 09:33:22 [3410] [6] DEBUG: AT2[/dev/ttyS0]: --> ^Z2005-08-22 09:33:25 [3410] [6] DEBUG: AT2[/dev/ttyS0]: <-- >2005-08-22 09:33:25 [3410] [6] DEBUG: AT2[/dev/ttyS0]: <-- +CMGS: 1852005-08-22 09:33:25 [3410] [6] DEBUG: AT2[/dev/ttyS0]: <-- OK2005-08-22 09:33:25 [3410] [6] DEBUG: AT2[/dev/ttyS0]: send command status: 0
Yet I do not get the SMS?
If I send an SI, it comes through just fine…Does anyone have any ideas? Thanks, Brent |
- RE: Sending SMS's via the PPG interface Brent Goldspring
- Re: Sending SMS's via the PPG interface Christian Vandrei
- RE: Sending SMS's via the PPG interface Brent Goldspring
