Does "Routing SMS messages to a Specifc SMSC Route" applicable to ... | Search |
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 22, 2009 ⬆ |
◄ ► |
Author | Message | |||
krishna vardhan dasari New member Username: Krishnavardhan Post Number: 1 Registered: 10-2008 |
Hi, I am using NOWSMS as PushProxy gateway (PPG) for sending WAP messages using http interface of NowSMS. I am using SMSC connection type as 'SMPP over TCP/IP'. Recently i read article "Routing SMS messages to a Specifc SMSC Route" , this articall is saying that using HTTP parameter ""&SMSCRoute=xxxxx" we can explicitly route a message via a particular SMSC, so that you don't have to use the sender/recipient matching logic if it is not appropriate for your configuration. my doubt is can use this http parameter to send WAP message using http interface "http://ipaddress:port/pap". Regards, krishna Vardhan. }} | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 128 Registered: 08-2008 |
Hi, No, that parameter is not currently supported for the PAP interface. (User and password are the only URL parameters supported in that interface). I'm going to check with engineering to see if this could be added. In the meantime, depending on the type of push that you are sending, it might be possible to use the XML settings POST interface, which does support this parameter. Is it possible to send the push content that you are sending via the "Send XML Settings" web interface? If so, you could post that XML to: POST /OTA=POST?SMSCRoute=routename HTTP/1.0 Content-type: application/xml Content-length: (required) (*blank line here*) <xml content here> -- Des NowSMS Support | |||
krishna vardhan dasari New member Username: Krishnavardhan Post Number: 2 Registered: 10-2008 |
Hi Des, Thank you for your response . My application is an mobile content management system , I have to send a wap push link of type service indication ( SI ) which contains a download url.As you mentioned I checked NOWSMS documentation for “Send XML Settings Document” and found that it is supporting WAP PUSH messages . The "Send XML Settings Document" interface supports the following types of XML settings documents: WAP Push Service Indication, Service Load and Cache Operation The operations use the root XML element <si>, <sl> or <co>. I need explanation about programmatically accessing web interface of “Send XML Settings Document” in my application. Can you please elaborate about “ HTTP POST of send XML DOC “ POST /OTA=POST?SMSCRoute=routename HTTP/1.0 Content-type: application/xml Content-length: (required) (*blank line here*) <xml content here> WAP PUSH message I am sending : Content-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-message push-id="CDS1210746874109" source-reference="CDS" ppg-notify-requested-to="http://localhost:9000" progress-notes-requested="false"> <address address-value="WAPPUSH=+919849103666/TYPE=PLMN@airtel.com"/> <quality-of-service priority="high" delivery-method="unconfirmed" networ k="GSM" network-required="true" bearer="SMS" bearer-required="false"/> </push-message> </pap> Content-Type: text/vnd.wap.si <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE si PUBLIC "-//WAPFORUM//DTD SI 1.0//EN" "http://www.wapforum.org/DTD/si.dtd"> <si> <indication href="http://59.90.17.86:9002/fs/main/fd/4001/Krish1 .mid?type=5&ct=7008&step=one" si-id="CDS 1210746865453" created="2008-05-14T12:04:25Z"> Download: Krish1 </indication> </si> Regards, Krishna Vardhan. | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 132 Registered: 08-2008 |
Hi Krishna, This example should help explain. Presently, you are performing an HTTP POST like this: POST /pap HTTP/1.0 Content-Type: multipart/related; boundary=mime-boundary; type="application/xml" Content-Length: xxxxx --mime-boundary Content-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-message push-id="CDS1210746874109" source-reference="CDS" ppg-notify-requested-to="http://localhost:9000" progress-notes-requested="false"> <address address-value="WAPPUSH=+919849103666/TYPE=PLMN@airtel.com"/> <quality-of-service priority="high" delivery-method="unconfirmed" networ k="GSM" network-required="true" bearer="SMS" bearer-required="false"/> </push-message> </pap> --mime-boundary Content-Type: text/vnd.wap.si <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE si PUBLIC "-//WAPFORUM//DTD SI 1.0//EN" "http://www.wapforum.org/DTD/si.dtd"> <si> <indication href="http://59.90.17.86:9002/fs/main/fd/4001/Krish1 .mid?type=5&ct=7008&step=one" si-id="CDS 1210746865453" created="2008-05-14T12:04:25Z"> Download: Krish1 </indication> </si> --mime-boundary-- Instead, change it to this: POST /?PhoneNumber=%2B919849103666&OTA=POST&SMSCRoute=routename HTTP/1.0 Content-type: application/xml Content-length: xxxxx <?xml version="1.0" encoding="ISO-8859-1"?> <!DOCTYPE si PUBLIC "-//WAPFORUM//DTD SI 1.0//EN" "http://www.wapforum.org/DTD/si.dtd"> <si> <indication href="http://59.90.17.86:9002/fs/main/fd/4001/Krish1 .mid?type=5&ct=7008&step=one" si-id="CDS 1210746865453" created="2008-05-14T12:04:25Z"> Download: Krish1 </indication> </si> Basically ... what you are doing is getting rid of the PAP component. Instead of posting multipart content, only the SI document is posted. Instead of specifying the recipient phone number in the PAP content, it is specified in a URL parameter (the "+" must be URL encoded). SMSCRoute= can also be specified as a URL parameter in this interface. -- Des NowSMS Support | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 174 Registered: 08-2008 |
Follow-up ... We've posted an interim update for NowSMS That includes support for the "&SMSCRoute=" parameter when submitting WAP push messages via the PAP/PPG interface. This update can be downloaded from http://www.nowsms.com/download/nowsmsupdate.zip. Basically, this update allows you to include "SMSCRoute=routename" in the PAP URL like this: /PAP?SMSCRoute=routename or /PAP?user=username&password=password&SMSCRoute=routename -- Des NowSMS Support |