| Possible bugs relate to "sender number" |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | ||||
| Min Lu New member Username: Uspepper Post Number: 18 Registered: 08-2005 |
I posted this problem before, but I don't think bn gave a complete solution. 1. If I don't put "[Additional Settings] Sender = xxxx" in vaspfile.ini, the receiver will receive a MMS with blank sender even if I put sender address in the "From:" field in the html page provided by NowSms. 2. If I put "[Additional Settings] Sender = xxxx" in vaspfile.ini, any "sub MMS gateway" connects to this gateway can only send MMS with this fixed sender address
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6879 Registered: 10-2002 |
Hi Min Lu, The puzzling thing is that the sender address should be included within the "SenderIdentification" section of the MM7 submission. Your submission has this: <SenderIdentification> <VASPID>815105</VASPID> <VASID>05339</VASID> </SenderIdentification> And a submission that included a sender address would look like this: <SenderIdentification> <VASPID>815105</VASPID> <VASID>05339</VASID> <SenderAddress><Number>12345678</Number></SenderAddress> </SenderIdentification> The "AdditionalSettings" section in VASP.INI is really just a "hack" to insert additional content into the MM7 XML. But this additional content will not necessarily follow the rules of the MM7 schema. (We have just found over time that some confused MM7 implementations would accept some extra data this way.) So the question is ... why won't the MMSC accept a sender address that is properly encoded. You could try changing the connection type to be "To VASP (Deliver Format)" instead of "To MMSC (Submit Format)". The "To VASP (Deliver Format)" uses a <Sender> element to denote the message sender ... whereas the "From VASP (Submit Format)" uses a <SenderAddress> element within the <SenderIdentification> element. You could also try changing the MM7 schema to "REL-6-MM7-1-0" to match the version that is being returned from the MMSC. But overall, I don't have an explanation for why the MMSC is not accepting a sender address when encoded as directed in the schema. (Your debug log does not include any sender address in the message submissions, I'm just assuming that you have attempted to include a sender address in the standard way and explaining what you would/should see.) -bn | ||||
| Min Lu New member Username: Uspepper Post Number: 19 Registered: 08-2005 |
Problem solved after I changed the MM7 schema to "REL-6-MM7-1-0". Thank you very much. Another question: does NowSms 2006 support USSD? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6882 Registered: 10-2002 |
Excellent. I'm surprised that the schema version made a difference. But there was a change in the MM7 schema for sender address encoding between REL5-MM7-1-1 and REL5-MM7-1-2. Maybe the Huawei MMSC assumes that all REL5 MM7 requests should use the pre REL5-MM7-1-2 encoding of the sender address. Regarding USSD, we support it via SMPP. The only information that I have on it is in the following thread: http://support.nowsms.com/discus/messages/1/11394.html | ||||
