| Getting out of the walled garden! |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through July 24, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| John O'Brien New member Username: Bigemu Post Number: 1 Registered: 06-2007 |
Anyone who has mucked around with MMS and WAP push messages will have found out that there are nice mobile operators like Vodafone who have the APN's for WAP the same as for MMS. Means you can deliver a M_Notify SMS to handset and it will retrieve it from a WAP server. I was wondering in the case where operators have built the walled garden it is possible to convince the handset to use the WAP APN instead of the MMS APN. I know you can reset the handset configuration but I was wondering if there are any options available in the construction of the retrieval URL that might direct it to use the WAP APN. Lets face it I'm wishing this was a feature! | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7308 Registered: 10-2002 |
Hi John, It is a frustrating issue, but from my vantage point, I don't see any changes coming. The issue is that the mobile operators who use separate MMS and WAP APNs were really going into this thinking that they were doing their customers a favour. You see, when a customer connects to the MMS APN, they are generally not charged for any data access that occurs over this APN. The idea was that the sender of the MMS would get charged for the actual sending of the message ... but they would not get charged separately for the data traffic associated with the sending, and the recipient would not get charged for the data traffic associated with message retrieval. As a result, the MMS APN is locked down to prevent abuse. At this point, there's no incentive for the operator to make any changes. It is a side effect of the above configuration that MMS messages from other MMSCs cannot be delivered directly to their customers ... but now that they see this, they don't want to change it because they want to make sure they get paid when someone sends an MMS to one of their customers. It would be great to see some changes that might allow more flexibility, but nothing seems to be in the works. MMS 1.3 is currently in late candidate release, and its protocol changes are very minor.  | |||
