| MMS over HTTP |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through February 03, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| reddy Unregistered guest |
Hi Bryce, If I plan to implement MMS over HTTP How do I get M-Notifiation.ind?? As far as I understand. Whenever there is a new message A SIR (session initiation request) will be sent via sms which contains url with which I have to establish a push session and during the content push of this session a url(location) where I have to contact to retrieve MMS will be sent to a HTTP server implemented on the handset.. Or is it that SIR itself contains the actual url from where I need to retrieve MMS in such a case there is no need to implement HTTP server in the handset. thank u | |||
| Lydia K Unregistered guest |
Hi I am a new comer in IT,and i need the basic MMS information about the following: 1. DP5 2. Bulk proxy 3. HTTP proxy 4. SMPP proxy Thanks in advance | |||
| Eddy Kvetny New member Username: Eddyk Post Number: 4 Registered: 11-2004 |
Hi Reddy, Bryce will correct me if I am wrong ... Most of MMSCs support connectionless WAP Push over SMS rather than connection-oriented which involves sending the WAP Push SMS with SIR to the device's SIA which, in turn, should establish the HTTP connection to the PPG. So, WAP Push over SMS will contain WSP-encoded M-Notification.ind with the URL of a MMS message to deliver and then your MMS client can establish the HTTP connection to MMSC using the received MMS message URL. I am not aware of MMS implementations using connection-oriented WAP Push with SIR and SIA | |||
