How MMS Forwarding works

How MMS Forwarding works SearchSearch
Author Message
Ashu
New member
Username: Cks

Post Number: 1
Registered: 11-2011
Posted on Tuesday, November 08, 2011 - 03:33 pm:   

Hi All,

MMS forwarding can be a feature offered by an operator. A subscriber may enable/disble this feature through SMS/IVR or by calling customer care. This is useful in case if the subscriber doesn't want to receive MMS, for high charging rates, while in roaming but wants it to be forwarded to another number/email-address.

I want to know, how this works. This is in regards to charging the subscriber/recipient (who has enabled MM Forwarding).

Queries -

1. Where does the translation of the recipient address with the forwarded email/number happens?

2. Does MMS R/S contain the mapping information, i.e. the recipient address to the forwarded to number/email-address?

3. Will the MMS R/S send the forwarded to number/email as the recipient address in the charging call (say via diameter Ro-Interface) towards the OCS?

4. What all difference will the charging call in diameter message will have in this scenario with the normal MMS scenario (where the forwarding is not required)?

Cheers!
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8007
Registered: 10-2002
Posted on Friday, November 11, 2011 - 04:30 pm:   

Hi,

This sounds like a feature specific to an MMSC product that is being used by the operator in question.

It would not necessarily be covered by any standards.

The vendor in question could implement it however they see fit.

That said, it would be difficult to implement as an add-on to an MMSC (intercepting and redirecting MMS traffic local to the operator is easy ... also handling external MM4 traffic would be more problematic). The functionality you describe would be best implemented as a core MMSC function.

-bn

Add Your Message Here, or click here to start a new topic.
Post:
Bold text Italics Underline Create a hyperlink Insert a clipart image
Options: Automatically activate URLs in message
Action: