| Problem in sending MMS by a phone using Nowsms MMSc |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 21, 2010 ⬆ |
◄ ► |
| Author | Message | ||||
| charlier yohann New member Username: Zucko Post Number: 2 Registered: 06-2009 |
Dear all, At first sorry for my english.... It makes a long time that i try to configure my nowsms but i have some problems: At first, i didn't succeed in receipting MMS via Nowsms but i have no problem to send MMS. In a second time, when i test a mobile i can't send a MMS with it but i have no problem of MMS reception. I note that when i received a MMS, there is no identification number. Could it be the reason why i can't send MMS : a problem of identification of the mmsc ??? I use this configuration for my mobile : "APN: testbouygtel1; mmsc url : http://xxx.bttiv.org:8080 ; No Proxy". I send with my post all the capture and a tracks taken with Wireshark that can help you in order to see all my problems. Thank you for your fast help.....
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1053 Registered: 08-2008 |
Hi, Thank you for including so much detail. That helps me understand. I think you have two problems. Let me try to explain why. 1.) Mobile phone cannot send MMS with NowSMS as MMSC. Error "sending address unresolved". The reason you are getting this error is because when a mobile phone submits an MMS message to an MMSC, it does not include its phone number (sender). Instead, the MMSC is expected to identify/authenticate the sender. How the MMSC does this is outside of the scope of the MMS protocol (although the specifications suggest the use of RADIUS). The NowSMS MMSC performs this identification/authentication in two different ways: a.) The simple way for test environments. You must define each user in the "MMSC Users" list. Each mobile phone has a unique "MMS Server URL". Instead of just "http://xxx.bttiv.org:8080", it becomes "http://xxx.bttiv.org:8080/user=pass". b.) The preferred way for live mobile operator environments. In this scenario, the MMSC receives the sender phone number via an HTTP header inserted by the WAP proxy. The WAP proxy is able to perform this identification because it is configured to receive a RADIUS accounting feed from the the GGSN (or other access server). This is described in more detail at http://www.nowsms.com/support/bulletins/tb-nowsms-002.htm. I see in your MMSC.INI file, that you have added some of the parameters for receiving an MSISDN header from a gateway. However, your mobile is not routing its request to the MMSC via a gateway/proxy. 2.) No identification number (sender?) when you receive an MMS. If you are using the NowSMS "Send MMS Message" web form, be sure to include the sender phone number that you want to appear in the "From" field. -- Des NowSMS Support | ||||
Config Nowsms
