Thread: [In development] Brainstorm: MMS Support
View Single Post
Framstag's Avatar
Framstag is offline Framstag
2009-10-19 , 14:08
Posts: 72 | Thanked: 51 times | Joined on Jul 2008 @ Germany
#59
Originally Posted by Performer View Post
In IMS infrastructure MMS agent shoud request service thru SIP before applying MM1. Just check specs of MM1st3.

Sorry, but my experience shows that most of operators uses private IP-networks for their services. I'm employee of one of them who has about 70 million of subscribers. Most parts of data-interchange between operators performs thru private networks like GRX by reasons of security and stability.
It's about 1 1/2 ago I looked at MMS/IMS integration. But I'm sure that the provider will want all the old devices out their to still work - and their definitely do not SIP. So if we assume that legacy device support will continue for 5-10 years we should not care about SIP now.

MMS for the device is TCP/IP for retrieval and PUSH (IP, SMS but possibly also SIP in future) for sending.

GRX is something that is not relevant for the device. GRX is used (as above mentioned) for inter-operator communication between providers, in the MMSC case communication between MMSC.

From the view of the device it does use SMS and IP roaming.

AFAIK there is no device lock-out. Every device that can handle the procotol should be able to do MMS.

I personally based on my work for my former employer only know the communication after WAP gateway and similar network elements and thus cannot tell you anything about APs and kernel requirements. But I can help if it comes to MMS protocol/messsage/PDU handling.

Feel free to ask.

Gruß...Tim
 

The Following 3 Users Say Thank You to Framstag For This Useful Post: