| HTTP response code 503 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 14, 2015 ⬆ |
◄ ► |
| Author | Message | ||||
| Sachin Tewari New member Username: Sachinn91 Post Number: 1 Registered: 03-2015 |
Hi Team, For every WAP Push request that is initiated from my android phone (being used as GSM modem), following response is received. [SMS] SubmitUser=sachinn91 SubmittedBy=127.0.0.1 PhoneNumber=+15124665376 Data=43060403AE81EA02056A0045860B03E2809D687474703A000103596F7520686176652034206 E657720656D61696C7320000101 UDH=0605040B8423F0 pid=00 dcs=F5 Binary=1 [ErrorDetail] RetryCount=3 LastRetryTime=20150312140938 LastErrorInfo=HTTPSMSC: Connection failed, HTTP status code = 503. -- NowSMSModem - sachinphone91 Error Logs: 2015-03-12 14:09:06,54F794BE,127.0.0.1,+15124665376,Retry Pending - HTTPSMSC: Connection failed, HTTP status code = 503. -- NowSMSModem - sachinphone91,SubmitUser=sachinn91;SMSCRouteName=sachinphone91 On further understanding, it came to my knowledge that only HTC phones support initiation of a WAP message possessing a T-Mobile service and I was using Samsung Note 3. However, later I tried utilizing NowSMS as a PPG in which case it should just utilize the SMSC of the mobile operator for triggering a SMS request. But in that case I got the same above error. Connection failed, HTTP status code = 503. -- NowSMSModem - sachinphone91 Note: I am able to send/receive SMS successfully, as an independent operation. I have tried sending WAP push message from the Web menu interface option, also tried to HTTP POST /pap (http://www.nowsms.com/using-nowsms-as-a-wap-push-proxy-gateway-ppg) but with no success. It makes me think that maybe I am missing something else which is hindering the process. Your advise would really be valuable in this case. Please let me know if I can provide you any more inputs to expedite your response. -Sachin | ||||
| Sachin Tewari New member Username: Sachinn91 Post Number: 2 Registered: 03-2015 |
Just to aggregate and frame my question better, below are the pin points. 1) If we input a push message (PAP) to NowSMS which is acting as a PPG. In that case, the make and model of my android phone OR whether the fact that mobile operator's PPG is closed should not hinder the process, right? As now my phone should only be utilized for its SMSC connection as WAP message just requires a SMS bearer to reach destination? I got the HTTP error mentioned in my previous mail while performing similar test keeping the same logic in my mind, which I am now clarifying. 2) It can also be the case that I am not able to correctly follow the instructions for initiating a PAP message. Not sure, how to send the POST /pap message. I tried putting it in the 'Send XML settings' menu, is that correct? If you can explain to me in a couple of steps what to do OR any link that would be helpful 3) Can I use a GSM modem for sending a WAP push message? Everywhere I can see it being used for SMS and MMS purposes, couldn't locate any case studies for its WAP push utility. Please suggest some economic commercial ones. | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8102 Registered: 10-2002 |
Hi, PAP is just an input method. The limitation on WAP Push is with regard to its output method. In other words, it doesn't matter what API you use to submit the WAP Push message to NowSMS...it matters what method is available for NowSMS to deliver it to the network. If you are using an Android device as a modem, WAP push (and other binary messages EXCEPT MMS) can ONLY be sent with HTC devices (running stock firmware) because HTC firmware offers an extra binary SMS API. More details can be found here: http://www.nowsms.com/send-wap-push-and-binary-sms-with-android-phone-as-modem That link also explains a binary SMS solution for rooted Android devices from other manufacturers...but, if your primary goal is WAP Push, you're probably better off with a cheap USB modem. Note that sending WAP push over a modem also requires that the mobile operator allows mobile originated WAP Push, and in the US, only T-Mobile has been known to allow this. Also note that generally speaking, MMS performance is far better using an Android device as a modem. Let me go back and see if I addressed all of your questions... 1. It gets a little confusing because technically NowSMS can accept PAP input as a PPG...and there is also an output option for NowSMS as an MMSC to post MMS notifications out via an operator PPG. The latter is a very unusual configuration and only applies if you are a mobile operator. Looking for an operator PPG to submit to is a dead end...to the best of my knowledge, in the US, Sprint and AT&T used to offer access through a developer program, but those APIs (and probably the PPGs themselves) were closed quite a few years back. 2. Interactively, the XML content can be submitted via "Send XML Settings". When you use PAP, it is multipart HTTP POST. For example, refer to this: http://www.nowsms.com/using-nowsms-as-a-wap-push-proxy-gateway-ppg The "text/vnd.wap.si" part is what you would use for "Send XML Settings". The full PAP HTTP POST is shown in that link. Of course, as I mentioned above, none of this will resolve the 503 error you are seeing. 3. Yes. As long as the mobile operator allows mobile originated WAP Push. To the best of our knowledge, T-Mobile is the only operator that allows this in the US...and only to other T-Mobile subscribers. -bn Bryce Norwood Now SMS/MMS Support | ||||
| Sachin Tewari New member Username: Sachinn91 Post Number: 3 Registered: 03-2015 |
Hi Bryce, Appreciate your detailed explanation on the issue. 1) My original aim was to send OTA (OMA-CP) for APN settings, which I started to achieve by sending a WAP push message. I am hoping that the purchased modem would support my complete objective? 2) What should I do to solve this HTTP error code? Even if I was using incompatible device or non-supported network operator I would probably be getting a different error message. This seems to be caused from something else... I am worried about this error code, as I think it is going to continue harassing me even after I buy a modem. | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8103 Registered: 10-2002 |
Hi Sachin, 1. Yes. As long as the mobile operator allows mobile originated WAP Push (should be ok with T-Mobile US). 2. This 503 error response is being generated by our Android app. We should probably generate a different error code unique to this scenario, but at present, the app returns error 503 for this scenario. You can read a little bit more about interpreting this error in another thread: http://support.nowsms.com/discus/messages/1/72790.html. I expect you will see the same ERROR_NO_BINARY_SUPPORT as that thread. And because it is not an HTC device, you will not see X-NowSMS-PDUMode: Yes. Bottom line, it is a confusing error code, but I am confident that the reason you are seeing it is for the reason I have described. -bn | ||||
| Sachin Tewari New member Username: Sachinn91 Post Number: 4 Registered: 03-2015 |
Hi Bryce, Thanks for your help. I am now using SM-V100T modem (http://www.samsung.com/us/support/owners/product/SM-V100TZKATMB) which uses T-Mobile as the carrier. Got integrated with NowSMS and delivered successful WAP Push messages. While initiating OMA CP (OTA) for sending APN settings the logs don't show any errors. However I don't see any configuration settings received on my phone. For reference, attached the debug log output. For testing purposes, I used sample provisioning documents listed within the standard OMA-CP specification. Am I doing anything wrong?
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5240 Registered: 08-2008 |
Hi Sachin, Well, that is a more complicated issue. Are you certain that the devices support this type of configuration? I know we have a number of customers who are handset manufacturers, and they ask questions about different objects in the XML settings from time to time...but in general, my expectation is that most devices do not support this. (And if they do, operator customized versions have the capability disabled.) There's some more discussion here...and if memory serves me correctly, LG is one of the larger manufacturers that support this. http://support.nowsms.com/discus/messages/485/71508.html -- Des NowSMS Support | ||||
| Sachin Tewari New member Username: Sachinn91 Post Number: 5 Registered: 03-2015 |
Hi Des, Thanks for your usual support. Just to troubleshoot where the issue is I 1) My Moto G2 supports reception of OMA-OTA messages from the service provider, so can there be any other reason why it isn't receiving OTA via NowSMS? * Received android update over OTA * Received APN settings over OTA 2) a) It cannot be an issue with my sending device, right. You saw the success logs, if their was a modem issue we could have seen some errors. b) I would be continuing my testing from India in sometime, will this be an apt device "Huawei-E355-Unlocked-Mobile-21Mbps". Confirmed support of frequency bands of operation in the region. 3) Tried testing by sending an initial bootstrap OMA-CP message too no response. Even if I am mentioning incorrect proxy, wap details it shouldn't matter I should receive something even if it is incorrect. Below link said that Moto devices require PIN to be set in the provisioning document, tried that too still nothing. http://arstechnica.com/civis/viewtopic.php?f=20&t=266274 If my device can receive OMA-OTA messages from my service provider that means it supports OTA, what do you think can be the reason behind my OTA not getting through? -Sachin | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5245 Registered: 08-2008 |
Hi Sachin, Is the Moto G2 unlocked? I tried sending a OMA CP settings message to an unlocked Moto E, and it worked, as long as I supplied a PIN. Both USERPIN and NETWPIN (IMSI) worked in my simple test. I didn't realize that Moto was supporting these settings messages in their Android devices. -- Des NowSMS Support | ||||
Debug Logs
