| M-send-req problem |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | ||||
| Matias E. Fabiano New member Username: Mfabiano Post Number: 1 Registered: 04-2006 |
Hi all, I'm a customer of nowsms and i'm trying to connect our new wapgw to the NowSms (v5.51k) via MM1 interface, with no success. There are two differences between a working connection (using NowWAP) and a not working one (using the new wapgw): 1. The version of http used by the wapgw is 1.0, and the MMSC is using v1.1. 2. There is no x-up-calling-line-id attribute present on the POST of the m-send-req. May any of these differences be the cause of the failure? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5803 Registered: 10-2002 |
Hi Matias, The HTTP version issue is not likely to be significant. Either HTTP 1.0 or 1.1 is ok (and the MMSC returns HTTP 1.0 format responses if 1.0 was specified in the request). Since you mention the "x-up-calling-line-id" header, I suspect that is the more significant issue. In order to accept an MMS message, the MMSC needs to know the identity of the sender. This is done in one of two different ways. 1.) The "MMS Server URL" configured on the device needs to include a userid and password (e.g., http://server:port/username=password), corresponding to an account provisioned in the "MMSC Users" list. 2.) The MMSC identifies the user based upon an HTTP header that is (usually) generated by the WAP gateway. Approach #1 is usually only practical in lab/test environments, or environments with a limited number of users. Approach #2 is more typically used in operator environments. When #2 is used, the NowSMS MMSC is usually configured to look for an "X-MSISDN" header to identify the phone number of the device. This is the header generated by NowWAP and some other gateways. You mention, "x-up-calling-line-id", and that is an alternative header that is usually generated by an Openwave gateway. Is there any HTTP header present in the failing request that you observe which contains the sender's phone number? The following document talks about this type of configuration: http://www.nowsms.com/support/bulletins/tb-nowsms-002.htm The one thing that I would add to the information in the above document is that it is possible for the NowSMS MMSC to look for multiple different HTTP headers to contain phone number information, which is useful for environments where there are WAP proxies from multiple vendors. The "MSISDNHeader" setting can contain a comma delimited list of multiple headers to check for the phone number, for example: MSISDNHeader=X-MSISDN,x-up-calling-line-id -bn | ||||
| Matias E. Fabiano New member Username: Mfabiano Post Number: 2 Registered: 04-2006 |
Bryce, thanks for your answer. I'm sending you two files, which contains two captures in pcap format (I believe that at first sight you'll find the problem here). - mm1.eth will show you a mm1 trace between NowWAP and NowSMS, and the MMS is sent correctly. In this capture i found the x-up-calling-line-id and the X-MSISDN headers. - mms-hua2.eth will show you a mm1 trace between the other gateway and NowSMS. Best regards and thanks in advance!
| ||||
| Matias E. Fabiano New member Username: Mfabiano Post Number: 3 Registered: 04-2006 |
Hi again Bryce, EUREKA!!! Martin solved it. We missed to configure a field (the IP address of wapgw into the msisdnHeaderGateways category) on the mmsc.ini. Then we restarted the application and worked OK. Now the question is ... should the MMSC update this field when you configure the MM1 part on the VASP tab? Thanks and best regards, Matias | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5807 Registered: 10-2002 |
Hi Matias, Great, glad to hear it was resolved. I'm not sure that I understand the new question, can you explain it with more detail? -bn | ||||
Packet captures
