| NowSMS v 5.51k produces (DeliverReq) xml that is not well formed ... |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| irwin williams New member Username: Irwin Post Number: 1 Registered: 02-2006 |
Hello, I am working with NowSMS v5.51k as a test MMSC. I am sending SubmitReq.s to it, and routing them back as DeliverReq.s. I am consistently receiving DeliverReq.s with the following content: <?xml version="1.0" ?> <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">20060208170504-4D7F475E@192.168.0.122</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> <Recipients> <To> <RFC2822Address>irwin.williams@somewhere.com<RFC2822Address> </To> </Recipients> <Subject>Multimedia Message</Subject> <Content href="cid:mms_cid"/> </DeliverReq> </env:Body> </env:Envelope> Which would be fine, except that the RFC2822Address element doesn't have a closing element. It wraps the content in two opening element. Has this been adjusted? Or am i doing something wrong? Thanks. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5536 Registered: 10-2002 |
Hi Irwin, That is definitely a bug, which I guess would occur when an e-mail address is defined as routed via a VASP. Unfortunately, between the 3GSM conference this week, and our pending release of NowSMS 2006 the following week, I don't think we can release a patch for this until the NowSMS 2006 release. For now, I'd suggest using phone number recipients in your tests. Thanks for bringing this item to our attention. -bn | |||
