| Author |
Message |
Gaurav Singh Kushwaha
New member
Username: Gaurav
Post Number: 1
Registered: 05-2006
| | Posted on Monday, May 01, 2006 - 06:56 am: | |
I believe those are required. The MMSC url that my mobile operator gives doesn't have these. So my question is why should these be mandatory in NowSMS MMSC ?
Further to that, Why do I need to even specify MMSC users. Can't I configure it in a generic fashion wherein anyone can use the MMSC ?
Regards,
Gaurav. |
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce
Post Number: 5862
Registered: 10-2002
| | Posted on Monday, May 01, 2006 - 08:42 pm: | |
Hi,
It is required because the MMSC must be able to identify the connected user.
There is no user identification supplied as part of the MMS protocol.
Instead, there is only a recommendation that the MMSC must obtain authentication/identification from other network elements.
When NowSMS is used as an operator MMSC (there are over 20 such deployments), we obtain this user identification via the WAP Proxy. The WAP Proxy, in turn, obtains user identification most frequently via a RADIUS feed from the access servers. You can read more about this at the following link:
http://www.nowsms.com/support/bulletins/tb-nowsms-002.htm
-bn |
|
Search
Last
