The APPID is invalid when send oma cp

The APPID is invalid when send oma cp SearchSearch
Author Message
jie.hu
New member
Username: Wony

Post Number: 6
Registered: 12-2014
Posted on Tuesday, January 20, 2015 - 12:38 pm:   

Hello,
I am in China, and want to test the oma cp by nowsms.
we have tested to send wap push msg,it is successful. and we test send oma cp too.

but there is one problem that the APPID is not invalid when send the oma cp. cause the phone can't dispatch the oma cp msg.the attachment is my send config.
So please tell me how to make the APPID value correct? I don't know how to see the send xml,use the view xml, but just show blank page.do you know how to see the send xml?
Thankssend oma cp config
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5169
Registered: 08-2008
Posted on Tuesday, January 20, 2015 - 03:15 pm:   

Hi,

Depending on the browser that you use, if you see a blank page after clicking "View XML", you may need to right-click and "View Source" to see the XML.

What APPID are you referring to?

a.) In the XML/WBXML content?

The form generates several different APPID values depending on the type of settings specified in the form.

For example, if "Home Page URL" is non-blank, the form will generate a w2 APPID section. MMS settings trigger a w4 APPID setting. E-mail settings also generate APPID settings.

b.) In the WSP header, X-WAP-Application-ID?

There is a way to set this header if you use "Send WAP Push"/Advanced instead of Send "XML Settings Document"?

--
Des
NowSMS Support
jie.hu
New member
Username: Wony

Post Number: 7
Registered: 12-2014
Posted on Wednesday, January 21, 2015 - 01:37 am:   

Dear Des,
thanks a lot.
I found use the IE browser can display normal when click view xml.
And the APPID my concern is w2, w4.

Could you tell me how to use the "Send XML Settings Document" option?
Just fill the below in XML Content of Settings Document line is OK?
- <wap-provisioningdoc>
- <characteristic type="BOOTSTRAP">
<parm name="NAME" value="3gnet" />
</characteristic>
- <characteristic type="NAPDEF">
<parm name="NAME" value="3gnet" />
<parm name="NAPID" value="3gnet_NAPID" />
<parm name="BEARER" value="GSM-GPRS" />
<parm name="NAP-ADDRESS" value="3gnet" />
<parm name="NAP-ADDRTYPE" value="APN" />
<parm name="INTERNET" />
- <characteristic type="NAPAUTHINFO">
<parm name="AUTHTYPE" value="PAP" />
<parm name="AUTHNAME" value="ddfd" />
<parm name="AUTHSECRET" value="ddd" />
</characteristic>
</characteristic>
- <characteristic type="APPLICATION">
<parm name="APPID" value="w2" />
<parm name="NAME" value="3gnet" />
<parm name="TO-NAPID" value="3gnet_NAPID" />
- <characteristic type="RESOURCE">
<parm name="NAME" value="3gnet" />
<parm name="URI" value="www.baidu.com" />
<parm name="STARTPAGE" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
jie.hu
New member
Username: Wony

Post Number: 8
Registered: 12-2014
Posted on Wednesday, January 21, 2015 - 07:08 am:   

Dear Des,
New problem happened. We can receive wap push and oma cp msg yesterday.But can't receive wap push and oma cp msg today.

We use same sim card and nokia FP register in China Unicom today.And the same receiver device similar registers in China Unicom.

So what's the possible cause? Whether relevant Nokia FP registration in WCDMA or GSM network?
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5173
Registered: 08-2008
Posted on Wednesday, January 21, 2015 - 10:43 pm:   

Hi,

To use "Send XML Settings Document", just copy + paste from that XML document, making any changes/edits that you want to try.

If "Home Page URL" is non-blank, the form will generate a w2 APPID section. "MMS Message Server URL" non-blank will trigger a w4 APPID section..

I am very confused why sometimes the network will not accept the WAP Push. I suppose it could be a difference between the GSM and WCDMA networks, with one of them blocking, and the other allowing. That would be unusual.

There is a very old thread that might be relevant: http://support.nowsms.com/discus/messages/1/17076.html

That is from the days when 3G was new technology. With early modems on some networks, there were problems sending any SMS on the 3G network. It may be worth trying what Bryce suggests in the 9th post. Add CommandPostInit1=AT+WS46=12 to the [Modem - driver name] section of SMSGW.INI. If the Nokia modem supports that command, that will force the modem to GSM/GPRS/EDGE. An alternative command is also mentioned in that thread to force 3G/WCDMA.

--
Des
NowSMS Support