| Clarification on MT provisioning & UAprof retrieval |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 21, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| Kumara New member Username: Dial12345 Post Number: 6 Registered: 07-2009 |
Hi, I'am currently using NOW SMS MMS GW trial version for MMS testing . please update me on following concerns. 1. Is it possible to enable MT provisioning for MMS ? ( i.e - if the recipient is not provisioned , Is it possible to provision the recipient & then send him the wap push ) 2. Need a clarification on transcoding mechanism used. According to our knowledge ,when a MMS is delivered , the content is adopted according to the recipient handset preferences using the UAprof details of the recipient handset. what is the method used if the recipient handset does not send the UAprof with the HTTP GET request . (As we have observed there are some handsets which do not send UAprof with the HTTP GET request ) Thanks. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1057 Registered: 08-2008 |
Hi Kumara, 1.) There are at least three ways to handle MMS account provisioning. a.) User accounts are automatically provisioned the first time that a user sends an MMS. This is the best way to confirm that the handset is configured correctly for MMS. b.) Manually provision the accounts via HTTP. The interface to do this is described here: http://www.nowsms.com/support/bulletins/tb-nowsms-013.htm c.) Maintain your own database of which accounts should be enabled for MMS, and use the routing callbacks of the MMSC to tell the MMSC how to process the message. In this scenario, the NowSMS MMSC performs an HTTP callback each time it needs to route a message. This callback is normally used to deal with mobile number portability, but by returning "Route=Direct", this signals that the message should be direct delivered by the MMSC. The following link describes the routing callbacks: http://blog.nowsms.com/2008/04/mobile-number-portability-mnp-and.html 2.) If no UAProf header is present, then no transcoding is performed. Some people would prefer that a "lowest common denominator" basic transcoding be employed. Here is a link with information on how this can be configured: http://support.nowsms.com/discus/messages/485/21796.html -- Des NowSMS Support | |||
| Kumara New member Username: Dial12345 Post Number: 8 Registered: 07-2009 |
hello Des, When a MMS submitted , is it possible to check whether the recipient is provisioned or not & to provision the recipient in the system if not provisioned yet. Thanks, | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1081 Registered: 08-2008 |
Hi Kumara, I can't give a clear answer, because I'm not sure what you are trying to accomplish by provisioning the user at this point. For example, we don't really know if the number is even valid ... so I don't think it would be a good idea to provision an account without some verification. If you configure the MMSC "Default Route" as "Direct Delivery" (the default setting), then it doesn't really matter if the recipient is provisioned or not, because we will try to deliver the message to them. Or ... if you implement the HTTP routing callback, and you return "Type=Direct", then this tells the MMSC to deliver the message directly. We don't actually provision an account at this time, but it's not really necessary. So I think it depends on what you're trying to accomplish through this provisioning. On a lot of systems (particularly those that use routing callbacks), whether or not an account is officially provisioned doesn't really matter. -- Des NowSMS Support | |||
| Kumara New member Username: Dial12345 Post Number: 9 Registered: 07-2009 |
Hello Des , I am interested to learn more about the transcoding process of NOW SMS MMS GW. 1. Does now sms mms GW have a inbuilt transcoding engine ? 2. If so , can you please provide me the function of transcoding engine. Thanks, | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1113 Registered: 08-2008 |
Hi Kumara, The primary transcoding that occurs has to do with the sizing of images to address limitations of the more limited receiving devices. There is also some transcoding of image formats. However, with modern phones that is rarely required any more (in the early days of MMS it was more common). -- Des NowSMS Support | |||
| Kumara New member Username: Dial12345 Post Number: 10 Registered: 07-2009 |
Hello Des, Do you use a proprietary Trnascoding engine for this ? Does the now sms system has capability to integrate with an external transcoding engine if required ? Thanks, | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1137 Registered: 08-2008 |
Hi Kumar, It is a proprietary transcoding engine. We haven't seen a lot of external transcoding engines. There was an industry group that was working on defining a standard transcoding interface, but in my opinion it never gained traction because they over complicated it. We have seen a few companies over the years try to sell transcoding products that were specific to MMS. The architecture of how these products interface with an MMSC is actually quite simple. The transcoding server works like an HTTP proxy. If you recall how MMS works (a good summary can be found at http://www.nowsms.com/howmmsworks.htm), when the MMSC sends a message out to a recipient, it sends out an HTTP link that the recipient can connect to to receive the content from the MMSC. When you're using a separate transcoding proxy, the server address in that HTTP link resolves to the proxy instead of the MMSC directly. The proxy retrieves the content from the MMSC on behalf of the client, and performs its transcoding before delivering it to the client. It's so simple to implement a transcoding service in this way, and it can work with any vendor's MMSC ... that's why the other attempts at defining a standard transcoding interface never made much progress. That said, in the early days of MMS there were quite a few companies talking about transcoding proxies, and there is considerably less talk about it these days. -- Des NowSMS Support | |||
