| Wap Push over IP |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through May 02, 2013 ⬆ |
◄ ► |
| Author | Message | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 51 Registered: 08-2006 |
Hi Des, Have gone through all the posts in the forum regarding Notifications over IP. As i understood "Bottom line ... I would not expect WAP Push over IP to work in an environment where you are sending from outside the operator network." Lets say NowMMSC and NowWap are running in a network which is outside the operators network. The MMS APN has the NowMMSC URL and its getting routed via NowWap as the proxy. This MMS APN uses the operators GPRS/Internet APN so its allowed access to the NowMMSC URL. In this scenario is it possible that NowWap assigns some kind of private IP or some kind of identification to the mobile users handset so that wap push over IP can be sent to the users mobile? I mean without using the IPNotify parameter? For this to happen NowWap needs to identify the mobile handset via the IP address/cookies/something else. Can this be used: http://www.nowsms.com/routing-mms-notifications-via-a-wap-push-proxy-gateway Any way of identifying the header/msisdn so that the wap push over IP can happen? Kindly let me know Thanks Sam | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3625 Registered: 08-2008 |
Hi Sam, At present, the only way to support this is by assigning fixed IP addresses to the devices, and configuring the IPNotify parameter to point phone number to device. We have considered alternative solutions, such as NowMMSC polling NowWAP for the IP address (assuming RADIUS provides this information), or actually routing the push notification through NowWAP. However, to date, there hasn't been a commercially compelling reason for us to implement. The scenario that you describe is complicated by the fact that you are using the operator's GPRS/Internet APN. Devices are generally given private IP addresses in this scenario, and they connect to the outside internet via NAT. As such, there is no way to initiate an IP connection back to the device. It is possible to get around this with a private APN, but on a public APN you are stuck. -- Des NowSMS Support | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 52 Registered: 08-2006 |
Hi Des Appreciate your reply. I understand the limitations. But maybe..and i mean maybe the user connects via NowWap Proxy..and hes assigned username/password. Possible for NowMMSC then to recognise the device/user based on his login credentials and then send the IP Notification? "However, to date, there hasn't been a commercially compelling reason for us to implement." I am consulting a potential client who would really use this. Maybe we can discuss this on email? Kindly let me know Sam | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 8009 Registered: 10-2002 |
Hi Sam, Des asked me to jump into this conversation. The problem is that the client does not maintain an open connection with NowWAP. It only connects to it when it has an MMS to send. Even then, if the device is connecting to NowWAP via a NAT, and the device is using WAP2/HTTP, there is no way to insert a push into the stream. (If the device is using WAP1/WSP, it is possible to insert a push into the stream. But, this is only possible in the NAT scenario when the device connects to send a message.) There are WAP2 push protocols designed to overcome this limitation. The Push OTA-HTTP defines two mechanisms. PO-TCP (proxy originated) is not NAT compatible. TO-TCP (terminal originated) is NAT compatible. The problem is that we don't know of any phones that support TO-TCP. With this protocol, the phone registers to the push proxy server by establishing at TCP/IP connection to it when it has data availability. This connection is kept open so that the push proxy can send push messages to the phone as needed. So, in a lot of scenarios it becomes an academic discussion. Without RADIUS or static IP, there is no way to know the current IP address associated with a phone number. (TO-TCP could be a way around this, but we know of no devices that implement it.) Without static IP, there is no way to send a push to a device. Note that static IP can be on a private network. So for an operator system, as long as the push proxy has visibility to that same private IP device address space (without NAT), a solution is technically feasible. A private APN can fulfill these requirements. But using a public APN, the only feasible solution is sending the MMS notification push messages over SMS. If you want to provide more potential client details via e-mail, we can start a dialog if you send an e-mail to nowsms@nowsms.com with Attention: Bryce in the subject line. I just want to caution that technical considerations tend to trump commercial ones in most scenarios. -bn | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 53 Registered: 08-2006 |
Hi Bryce, Appreciate your time on this. I would again recheck with the client and update you asap. Thanks once again. Sam | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 54 Registered: 08-2006 |
Hi Bryce & Des, Discussed with the client. Wap Push over IP as you both have mentioned wont work out. My remaining query is that for MMS delivery reports is it possible to use Wap Push over IP? or some other mechanism? Currently lets say we send the MMS notification via SMS. The MMS delivery reports are also happening via SMS. This increases the SMS cost per MMS. Any way out for the MMS reports? Kindly let me know Thanks in advance, Sam | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 55 Registered: 08-2006 |
Hi Bryce & Des Possible to use in-transit delivery report for the MMS reports? If DisableDeliveryReceipt=Yes and DeliveryReportEnroute=Yes are set for a connection, and a message requests a delivery report, an in-transit delivery report will be generated when the message is successfully dispatched to the modem (DeliveryReportEnroute=Yes). The message sent via the modem will NOT request further delivery reports (DisableDeliveryReceipt=Yes). Kindly let me know Sam | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3635 Registered: 08-2008 |
Hi Sam, Those configurations are SMS specific, but there is a configuration option to disable MMS delivery receipts in the MMSC configuration. That is what I would recommend. -- Des NowSMS Support | |||
| sam Frequent Contributor Username: Samdsouza Post Number: 56 Registered: 08-2006 |
Thanks a million Des will check on the option to disable MMS reports. Thanks once again Sam | |||
