| Sender ID Missing |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 07, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| tekken New member Username: Tekkenmaster2008 Post Number: 4 Registered: 03-2009 |
Hi, I'm getting null value on FROM field of HTTP response of Huawei's MMSC, any issues on my configuration? I already set a default short code value (sender ID) from the default route. 20:09:01:750 [9] HttpResponseWait: Ok 20:09:01:750 [9] ThreadProcessVASPQ: MM7 - got http ok response 20:09:01:750 [9] ThreadProcessVASPQ: HTTP/1.1 200 OK Server: Resin/3.0.7 SOAPAction: "" x-huawei-mmsc-tid: 20090411200901-FEAC35A3@domain.com x-huawei-mmsc-from: x-huawei-mmsc-to: 009xxxxxxxxxx x-huawei-mmsc-code: 1000 Content-Type: text/xml; charset="utf-8" Content-Length: 666 Date: Sat, 11 Apr 2009 17:09:06 GMT Appreciate if someone can help me to resolve this issue. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7764 Registered: 10-2002 |
Hi, I seem to remember this happening to someone else before. I believe it had to do with the version of the MM7 schema that was being used. Before we get to that ... you do have a "Default Sender Address" configured in the "MMSC Routing" definition, right? Regarding the MM7 Schema version, try using MM7 Schema "REL-6-MM7-1-0" and MMS version "6.3.0". Based upon an earlier thread, this seemed to resolve a problem with a missing sender id when submitting through a Huawei MMSC. -bn | |||
| tekken New member Username: Tekkenmaster2008 Post Number: 5 Registered: 03-2009 |
Hi Bryce, Thanks for response, I set the Default Sender Address as provided by our telco. Also I'm using the MM7 Schema for Huawei MMSC "REL-6-MM7-1-0" and MMS version "6.3.0" Appreciate if you can share with us previous experience with Huawei. Thanks again. | |||
| tekken New member Username: Tekkenmaster2008 Post Number: 6 Registered: 03-2009 |
Hi Bryce, I set the correct MM7 schema for Huawei MMSC and enable default sender address on MMSC Routing definition as well, however still i don't get the Sender ID. Our telco advise us to revise the XML on submitting MMS to them: NowSMS Format: <SenderAddress> <Number>99999</Number> </SenderAddress> Required Format: <SenderAddress>99999</SenderAddress> Is this possible? please advise. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 696 Registered: 08-2008 |
Hi, Bryce was supposed to be covering the discussion boards for me while I was on holiday, but some extenuating circumstances got in the way. As I mentioned in another thread, if they are requiring that other format, then this suggests that they are using one of the older MM7 schemas. Both REL-5-MM7-1-0 and REL-5-MM7-1-1 use that format without "<Number>". Later schemas require "<Number>" (or other elements) within the "<Sender Address>". Try REL-5-MM7-1-0 with MMS version "5.3.0". -- Des NowSMS Support | |||
| tekken New member Username: Tekkenmaster2008 Post Number: 12 Registered: 03-2009 |
Hi Des, It works with the MMS version and XML schema you mentioned, now we are trying to evaluate your product and find out if it meets our requirements. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 717 Registered: 08-2008 |
Thanks for the follow-up! There were a few other threads regarding missing sender ids, with conflicting information ... and possibly some typos. These significant differences in the MM7 schemas between versions can be frustrating ... and in my opinion, are downright irresponsible on the part of the committee that defined them. It's a shame that there is no way to do version querying to avoid these problems ... -- Des NowSMS Support | |||
