| Binary messages and mms messages with nowsms |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 14, 2015 ⬆ |
◄ ► |
| Author | Message | |||
| Teja M New member Username: Tmedasani Post Number: 1 Registered: 08-2014 |
Hi all, I am using Nokia 6682 as a gsm modem with nowsms.I am able to send regular text messages using nowsms but am unable to send any binary sms (wap push,mms notification).I am also unable to send a mms. I can send and receive mms on the phone.I've also tried with samsung sgh-a707. Is there any block on Mobile originated binary messages in Unites states? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4993 Registered: 08-2008 |
Hi, Yes, there are blocks on mobile originated binary messages in the US. When binary messages are supported, you can only send them to subscribers on the same network as your modem. I know that T-Mobile US still supports binary messages, because when we recently added binary message support for HTC phones in our Android app, we did some testing with a T-Mobile US SIM. AT&T has been blocking mobile originated WAP Push messages for a few years. One of our customers discovered a work-around to get around the AT&T block, which is described here: http://www.nowsms.com/wap-push-att-usa-gsm-modem I do not know whether or not that technique still works. Verizon and Sprint are not GSM based, so the binary message formats are different on those networks. And we have not see any modems for those networks that supported binary messages. -- Des NowSMS Support | |||
| Teja M New member Username: Tmedasani Post Number: 2 Registered: 08-2014 |
Hi des, I tried the workaround suggested by you. I have tried the following combinations. PID: 1 PID: 41 PID: 1 PID: 41 DCS: F5 DCS: F5 DCS: 04 DCS: 04 Unfortunately, none of them worked. I want to send binary messages across all the carriers eventually ( across the same carrier is fine for now ).Could you suggest any alternatives for gsm modem.Do you think that an android phone would work better? Any short term solution is also welcome. Thanks Teja | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 4995 Registered: 08-2008 |
Hi Teja, Is the modem on AT&T? Are the messages failing with a particular CMGS error code? I don't think it would make a difference on an Android phone (NowSMS can only send binary with HTC Android phones because they have an extra API), as the same interface is used. I will be in the Us next week and will un come tests with an ATT Sim, but if reaching all carriers is your goal, keep in mind that 50% is non-GSM. You might find a provider that can do binary SMS to AT&T and T-Mobile, but it is rare to find one that supports Sprint or Verizon. Sending MMS through the operator MMSC is doable, just not your own MMS notifications or WAP Push. -- Des NowSMS Support | |||
| Teja M New member Username: Tmedasani Post Number: 3 Registered: 08-2014 |
Hi Des, Thanks for your immediate response.The modem is on ATT. The CMGS error code i get using at commands is "500". The destination number is valid and i am able to send text messages in pdu mode. The error (CMEE error: 500) shows up only in wap push and mms notifications. Interestingly, i am able to send concatenated messages though they have a UDH. | |||
| Teja M New member Username: Tmedasani Post Number: 4 Registered: 08-2014 |
Hi Des, I used the T-mobile sim as suggested and am able to send binary messages successfully. Did you get any favorable result on the ATT sim? Would getting a short code and sending msgs via a sms provider help? Thanks for the help. Teja | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5003 Registered: 08-2008 |
Hi Teja, I was able to run some tests with an AT&T SIM, but unfortunately no solution. In my tests, it seemed very clear that any mobile originated SMS messages directed to port 2948 (the port that WAP Push listens on) are being actively rejected. The modem I used reported CMGS ERROR 111, a protocol error, which suggests the message is being actively rejected. If the port number is changed, the message is properly sent and received, but, of course, it is not understood as a WAP push. I tried a variety of DCS and PID values to no effect. So the work-around that worked last year appears to also have been blocked. I'm going to discuss with colleagues to see if they have other ideas for me to try, but to me it looks like a block based on the port number. Searching for other references, I found this link confirming that AT&T did not support mobile originated WAP Push: http://developer.att.com/developer/forward.jsp?passedItemId=2400430 Then when the links from that page no longer worked, I found an AT&T statement indicating that they were no longer supporting any form of WAP Push. https://developer.att.com/developer/basicTemplate.jsp?passedItemId=13400420 -- Des NowSMS Support | |||
