| Sending Address Unresolved?? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||||
| Silentsnake New member Username: Silentsnake Post Number: 2 Registered: 07-2005 |
I use NOW Wap Gateway and NOW SMS/MMS, connect to these two to Core Network.. I debuged MMS bearered on WAP1.1 and HTTP. I tried send MMS to NOW MMSC through WAP Gateway. UE can send "MMSE send-request message" to WAP Gateway, and the http connection between NOW SMS/MMS and NOW Wap gateway seems OK, MMSC send "send-confirm" message to WAP gateway with status "sending address unresovled", though I have add the users in NOW MMSC... Anyone help me check this problem? thanks...
| |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4654 Registered: 10-2002 |
The problem is that the MMSC doesn't know who it is that is sending the message. The MMSC needs to be able to obtain this information from the network. And unless you are in control of the complete network (e.g., the access servers that allocate IP addresses to the devices), it can't. When installed in a mobile operator network environment, we rely on the MMSC obtaining the sender identity (MSISDN) from the WAP gateway. And the WAP gateway receives it via a RADIUS feed from the access servers (GGSN in GPRS environment). This is described in some more detail at the following URL: http://www.nowsms.com/support/bulletins/tb-nowsms-002.htm But what if you're not a network operator, or you're in a lab environment but don't have the RADIUS feed capabilities? In that case, users can identify themselves with unique information in the MMSC server URL. See the bottom of the following link: http://www.nowsms.com/documentation/ProductDocumentation/mms_notifications_and_c ontent/MMSC_Messaging_Server.htm | |||||
