Send XML Settings Document

Send XML Settings Document SearchSearch
Author Message
TA
New member
Username: Mhantirah

Post Number: 1
Registered: 08-2005
Posted on Tuesday, August 30, 2005 - 10:56 am:   

I tried the following text:

<wap-provisioningdoc>
<characteristic type="APPLICATION">
<parm name="APPID" value="w5" />
<parm name="TO-NAPID" value="INTERNET" />
<parm name="NAME" value="SyncML Settings" />
<parm name="ADDR" value=" http://Your Server IP Address:8080/sync4j/sync" />
<characteristic type="RESOURCE">
<parm name="URI" value="./contacts" />
<parm name="NAME" value="contacts" />
<parm name="AACCEPT" value="text/x-vcard" />
</characteristic>
<characteristic type="RESOURCE">
<parm name="URI" value="./calendar" />
<parm name="NAME" value="calendar" />
<parm name="AACCEPT" value="text/x-vcalendar" />
</characteristic>
<characteristic type="APPAUTH">
<parm name="AAUTHNAME" value="guest" />
<parm name="AAUTHSECRET" value="guest" />
</characteristic>
</characteristic>
</wap-provisioningdoc>

in the screen "Send XML Settings Document" but I got this error

"- ERROR: Message Length is invalid -- SMPP –"
Please advise if I did anything wrong

Mohamed
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 4829
Registered: 10-2002
Posted on Thursday, September 01, 2005 - 05:48 pm:   

Hi Mohamed,

That should be fine.

It is going to generate 3 SMS messages. But each of the 3 messages will be within the size limits for SMS.

Do you have "Use WDP Adaptation" checked on the "Advanced Settings" page under "Properties" for the SMPP connection? If so, uncheck that setting, as this setting causes NowSMS to submit the entire long message in a single request instead of as 3 separate messages.

I'd like to see more of your log file, so that I can see exactly what NowSMS was trying to send when the SMSC returned that error.

Enable the debug logs (see the "Serial #" page of the configuration dialog), and I would like to see the SMPPDEBUG.LOG to verify that the message being submitted is valid. But unfortunately, I suspect that your provider might be enforcing an incorrect size limit.

-bn