| HTTP PUT |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | ||||
| lohith.m@gmail.com New member Username: Lohithm Post Number: 1 Registered: 10-2006 |
HI We are developping MMS With SIP (According to 3GPP standard) According to 3GPP Specification they have mentioned for sending MMS we need to use HTTP PUT message instead of HTTP POST method. So I would like to know whether the NowSMS's webserver support the HTTP PUT message?? And also even when we send a MMS with HTTP PUT whether MMSC will generate Notification indication or not? Regards Lohith | ||||
| MedSalimALI Frequent Contributor Username: Salim Post Number: 108 Registered: 04-2005 |
Hi Lohithm, In this case you need to know which protocol you will use, because any connection type has a specific protocol... example via MM7, of course the MMS submission request will be an HTTP PUT or get even in the NowSMS side.... so you need one of two choices: 1. Build your own script to send MMS submission request to the MMSC mobile operator and request also a notification. 2. Or use NowSMS to interface between your HTTp get and the MMSC of your mobile operator... in the case of NowSMS and also MM7 as protocol, just request from your mobile operator an MM7 account and then create VASP account and VASPout in NowSMS whcich will be using to route your MMS mesage to the MMSC... Bryce will give you more details, just to give you some pushing ideas... Salim..... | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6706 Registered: 10-2002 |
Hi Lolith, I assume that you are developing an MMS client. We do not support HTTP PUT ... only HTTP POST for MMS submissions from a client. I'd like to know specifically what standard document you are working from (and a specific section reference would be helpful). The 3GPP MMS specifications ... TS 23.140 (the most recent revision being v6.13.0) ... only describe the MM1 client-to-server interaction in an abstract fashion. The 3GPP MMS specifications for MM1 only cover the information elements and transactions, but not the actual binary formats or transport. The 3GPP MMS specs don't define the actual binary format in which an MMS message is transmitted via the MM1 interface, and they don't specify that HTTP is the transport. The real world implemenatation of MM1 comes from the OMA. Specifically, the MMS Encapsulation Protocol Specification defines the format of the data that is used for MM1 transactions ... and the MMS Client Transactions Specification defines how the abstract MM1 transactions defined by the 3GPP are implemented over WSP or HTTP. It is the OMA MMS Client Transactions Specification that defines that HTTP POST is used for submitting an MMS message to the MMSC. Basically, any current generation MMSC is going to be expecting HTTP POST, because it is working off of these specifications. So I'd like a pointer to whatever MMS over SIP specification that you are working with ... perhaps it is a work-in-progress that is still evolving ... as I can't understand what the logic would be of changing the HTTP POST to HTTP PUT for the MMS submission transaction. -bn | ||||
| lohith.m@gmail.com New member Username: Lohithm Post Number: 2 Registered: 10-2006 |
Hi Bryce Please see the attachment. This specification(3GPP2) talks about MMS using SIP. Here they talk about using HTTP PUT request instead of HTTP POST. At the time of Signalling ( Registration ) we will be getting the URI where to store the MMS. So by using HTTP PUT we are sending MMS to MMS Relay. I'd like to know whether this is possible in NowSMS or not. regards Lohith.M
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6746 Registered: 10-2002 |
Hi Lohith, There appears to be more differences in the MMS MM1 implementation in that specification than just that particular HTTP PUT transaction. In that specification, the MMSC needs to implement SIP, as there is an initial SIP registration message that needs to be implemented ... and the actual MMS submission process is SIP based. The Now SMS MMSC does not implement these transactions. I find this all very puzzling, because 3GPP appears to have decided that there is no need to redefine the MM1 transactions for implementation of MMS over SIP. A report from the group within the 3GPP that studied this issue concluded: "Delivery of MMS over 3GPP IP Access was studied as part of TR 23.804 and it was concluded as part of that study that OMA specifications cover the requirements for delivery of MMS over IP access and no enhancements to 3GPP stage 2 or stage 3 specifications are needed to support MMS over IP." The most recent version of 3GPP TR 23.804 defines the MMS over SIP implementation for 3GPP, and indeed, it uses the existing MM1 implementation. I am wondering if the 3GPP2 spec that you've referenced has not been superceded by another specification ... as I can't see why 3GPP2 would implement things so differently from 3GPP for this implementation. -bn | ||||
3GPP2 Specification for MMS using SIP
