| Sender address being left blank when forwarding from mobile to VASP |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 14, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Bobby Lam Unregistered guest |
Here's what I am trying to do: I have a VASP configured with the NOW gateway, and have the gateway forward any MMS to a particular phone number to this VASP (through MM7 with deliver request). Then I send the MMS from a mobile to the gateway directly through WAP (connecting to the gateway's MMSC). The gateway forwards the message fine, and the VASP receives the msg successfully. However when I look at MMSCDEBUG.log, which shows the deliver request being sent to the VASP, the <Sender> field is being left out in the DeliverReq header. In the VASP configuration, I have the 'Allow Sender Address Override' CHECKED, and 'Default Sender Address' left blank. Aside from this problem, everything seems to work fine. Any help would be greatly appreciated. Thanks! | |||
| Bobby Lam Unregistered guest |
I should clearify that I did the above configuration in the 'MMSC Routing' tab, not the 'MMSC VASP' tab. | |||
| Bobby Lam Unregistered guest |
Another note: I also tried sending the MMS message using the NOW gateway's HTTP interface, and have that message routed to my MM7 server. Same result, the sender field is not present in the MM7 deliver request header... | |||
| Wolfgang Röckelein Unregistered guest |
I can confirm this. I also get only empty sender addresses, and AFAIK the sender is requiered in MM7. See my messages about the problem with the Nokia libraries (which I use to receive the MM7 connection) about a week ago. | |||
| Bobby Lam Unregistered guest |
Apparently this is a bug in the NOW gateway, and it has been fixed in the 5.50 release (I was using 5.01 release with Patch 4 applied). I upgraded my gateway this morning and it fixed the problem. Hope this helps you Wolfgang. | |||
| Wolfgang Röckelein Unregistered guest |
Unfortunatly not, as I am using 5.5final already and yet have the problem! | |||
| Wolfgang Röckelein Unregistered guest |
OK, I am bit wiser now: NowSMS sends: <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header> <mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2" env:mustUnderstand="1"> 20040601/16/2ACAEFE8@pckl735.uni-regensburg.de </mm7:TransactionID> </env:Header> <env:Body> <DeliverReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2"> <MM7Version>5.3.0</MM7Version> <Sender> <Number>+491751804646</Number> </Sender> <Sender>+491751804646/TYPE=PLMN</Sender> <Recipients> <To> <Number>234</Number> </To> </Recipients> <Subject>Multimedia Message</Subject> <Content href="cid:mms_cid" /> </DeliverReq> </env:Body> </env:Envelope> I think the problem is the second <Sender> element, which has no subentry of RFC2822Address, Number or Shortcode and thus leads to no sender number. As I read the scheme, <Sender> should occur only once... Wolfgang | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2765 Registered: 10-2002 |
Wolfgang, Yes, the problem that you are experiencing is different. I've contacted you via e-mail, but also wanted to cross-reference this thread here: http://support.nowsms.com/discus/messages/485/4340.html -bn | |||
