| How to config a NowSMS server to send OMA CP? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| jie.hu New member Username: Wony Post Number: 1 Registered: 12-2014 |
I wanna config a NowSMS server, which could send "OMA Provisioning Content". What should I do ? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5154 Registered: 08-2008 |
Hi, At a basic level, you need an SMSC connection that supports binary SMS messages. Many HTTP based connections do not, and the Android app interface does not, except in special circumstances (http://www.nowsms.com/send-wap-push-and-binary-sms-with-android-phone-as-modem). Try sending simple WAP Push SI messages first. -- Des NowSMS Support | |||
| jie.hu New member Username: Wony Post Number: 2 Registered: 12-2014 |
Thanks for you support. But this is not I want. ------------------------ I config NowSMS with Nokia Phone. And NowSMS could send SMS and MMS. But Wap Push and OMA CP message can not be sent. Could you give me further support? Thanks. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5159 Registered: 08-2008 |
OMA CP is sent over WAP Push. So for testing purposes, it is useful to test with WAP Push SI first. Some mobile operators block mobile originated WAP Push (with "security issues" as their reason). When this block is in place, it affects all forms of WAP Push, including OMA CP. Check the SMSOUT-yyyymmdd.LOG to see if an error is being reported when trying to send the message. If there is an error, this definitely suggests that the operator is refusing the message. If there is no error, it is still possible that the operator is discarding the message. We have seen several reports that Chinese operators do not allow mobile originated WAP Push. Also, we have confirmed that in the USA, only T-Mobile allows mobile originated WAP Push. The only suggestion we have is to try the settings to use a different DCS or PID value. See http://www.nowsms.com/wap-push-att-usa-gsm-modem ... PushDCS=4 is a good setting to try. But unfortunately, it may be a case that all mobile originated WAP Push is being blocked by the operator. When mobile originated WAP Push is blocked, the only alternative is to find a service provider that can support it, instead of using a modem. -- Des NowSMS Support | |||
| jie.hu New member Username: Wony Post Number: 3 Registered: 12-2014 |
Hello, we have tried your advice. 1,Check the SMSOUT-yyyymmdd.LOG,there is an error as below: 2015-01-14 13:47:42,54251AA0,10.120.0.235,18582512073,Retry Pending - ERROR - Modem Response (2): 0891683110801105F041330B818185522170F300F4330605040B8423F0DE0601AE02056A0045C60D 0342414944552E434F4D000701035445535420574150205055534820534900010 +CMS ERROR: 500 -- Nokia USB Modem And there is more detail error in SMSDEBUG.LOG as below: 13:47:39:550 [19] ThreadProcessConnection: Processing request /Send%20WAP%20Push%20Message.htm?WAPSL=&PhoneNumber=18582512073&WAPURL=WWW.BAIDU.COM&Text=TEST+WAP+PUSH+SI&WAPSIACTION=signal-medium&WAPSIID=&WAPSICREA TED=&WAPSIEXPIRES= 13:47:39:550 [19] Debug: 1 recipient entries 13:47:39:552 [19] CheckPreferredRouteMulti: Default Route Available 13:47:39:552 [19] CheckPreferredRouteMulti: Nokia USB Modem 13:47:39:552 [19] MessageRoutesAdd: 54251AA0.req 13:47:39:552 [17] ReceiveModemCommand: Signaled 13:47:39:552 [19] MessageRoutesAdd: Nokia USB Modem 13:47:39:554 [17] ThreadProcessModem: Processing 54251AA0.req... 13:47:39:561 [17] ThreadProcessModem: OUT: AT+CMGS=64 13:47:39:568 [17] ThreadProcessModem: IN: > 13:47:39:568 [17] ThreadProcessModem: OUT: 0891683110801105F041330B818185522170F300F4330605040B8423F0DE0601AE02056A0045C60D 0342414944552E434F4D0007010354455354205741502050555348205349000101 13:47:39:739 [17] ReceiveModemCommand: Sending extra CR 13:47:41:589 [17] ThreadProcessModem: ERROR - Modem Response (2): 0891683110801105F041330B818185522170F300F4330605040B8423F0DE0601AE02056A0045C60D 0342414944552E434F4D000701035445535420574150205055534820534900010 +CMS ERROR: 500 13:47:41:589 [17] ThreadProcessModem: OUT: 13:47:41:690 [17] ThreadProcessModem: OUT: \r 13:47:41:690 [17] ThreadProcessModem: OUT: AT 13:47:41:691 [17] ThreadProcessModem: IN: ERROR ERROR 13:47:41:693 [17] ThreadProcessModem: IN: OK 13:47:42:001 [17] ThreadProcessModem: Error: ERROR - Modem Response (2): 0891683110801105F041330B818185522170F300F4330605040B8423F0DE0601AE02056A0045C60D 0342414944552E434F4D000701035445535420574150205055534820534900010 +CMS ERROR: 500 2, we have tried your suggestion about adding the PushDCS=F5 and PushPID=41(PushPID=1) in SMSGW.INI,it doesn't work too. 3, we are using unicom network in China Chengdu, and another company in China Shenzhen.They use unicom network can send wap push and oma cp success by nowsms. Does the operator policy will differ between two cities? Another question is the WAPPUSH don't care about MMSC using only SMSC? We need your help and waiting for your reply. | |||
| jie.hu New member Username: Wony Post Number: 5 Registered: 12-2014 |
Hi Des, We have asked China shenzhen colleague test 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? Thanks  | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5170 Registered: 08-2008 |
Hi, See my reply at http://support.nowsms.com/discus/messages/1/72775.html I am not sure what APPID you refer to. -- Des NowSMS Support | |||
