| MSISDNHeaderDefaultCountryCode & MSISDNHeaderLocalPrefix |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| David Chkhartishvili New member Username: Datoch Post Number: 32 Registered: 06-2004 |
Hi, As I read in the documantation, those two configuration directives should apply to MSISDN numbers presented in the MSISDNHeader, but in fact they apply also to destination MSSIDN numbers. Is it correct behavour? | |||
| David Chkhartishvili New member Username: Datoch Post Number: 33 Registered: 06-2004 |
P.S. MSISDNHeaderPrefixConvert behaves exaclty as tow mentioned above. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4723 Registered: 10-2002 |
Hi David, When the sender of a message has a phone number in international format, we evaluate the recipient phone number, and we will also convert it to international format to allow for proper routing. If this conversion is not working properly, can you please give me an example, using your settings, so that I can understand the problem? I'm guessing that the conversion is working properly, but one of the complaints that we frequently get is that the conversion is "not friendly" to the recipient, because the majority of mobile phone users do not understand international number format. For that reason, we have another setting that can be placed in MMSC.INI under the [MMSC] header. MSISDNHeaderConvertToLocalNumber=Yes This setting is not very well documented, but it is safe to use as I know a number of customers who are successfully using this setting. (When people complain about the phone numbers always appearing in international format within MMS messages, I tell them about this setting.) Basically, this setting only effects the way phone numbers appear within MMS messages when messages are delivered to local recipients. So it is still safe to use if you have any international connections. And the MMS notifications that go out over SMS still go out with the recipient phone number in international format. -bn P.S. - I'm not sure whether this answers your question or not. I'm just making a guess about the reasoning behind your asking the question ... so if this doesn't answer it, please provide an example using your actual settings. | |||
| David Chkhartishvili New member Username: Datoch Post Number: 34 Registered: 06-2004 |
Hi Bryce, I will try to explain what I'm trying to do: Our country code is 995 and network prefix is 99. MSISDNs look like 99599xxxxxx. All I want is to add '+' sign to submitters MSISDN so they will look like +99599xxxxxx. I don't want to touch destination MSISDN numbers. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4725 Registered: 10-2002 |
David, My preference would be to try to fix any problems that are occurring with the number conversion. If there is a problem, I'd probably need an example to understand what is going wrong. But, if you just want to disable the conversion, then I suppose there is a back door way of doing this. Edit MMSC.INI, and under the [MMSC] header, add ShortCodeMaxLength=15. The intent of this particular setting is to disable destination number conversion for messages being sent to short codes. The default value is 4 (it probably should be 5). So increasing this value would have only the side effect of disabling all destination phone number conversion. -bn | |||
| David Chkhartishvili New member Username: Datoch Post Number: 35 Registered: 06-2004 |
Thanks Bryce, I've added two directives: ShortCodeMaxLength=20 MSISDNHeaderPrefixConvert=995:+995 and now it converts only source MSISDNs. BTW, could you post all this undocumented configuration directives? It would make your life simplier  . Thanks again. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4745 Registered: 10-2002 |
Hi David, It definitely would make my life simpler. Not just because people could refer to them here, but I'd have one place to go to look them up when I need to answer a question. I think my main concern is that there are a few undocumented settings that are quite hard to explain. Especially the MSISDNHeader related options for dealing with "DN" codes in Argentina. But still, I did managed to get the SMSGW.INI settings described here: http://support.nowsms.com/discus/messages/1/5972.html ... and I think there may be more settings in SMSGW.INI and MMSC.INI. I may go ahead and give this a go today, so forgive me for other questions that go unanswered. -bn | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4747 Registered: 10-2002 |
Sigh ... time for me to take a deep breath ... I may have missed a few (and made some gramatical and possibly syntactical errors in the process), but I tried to collect all of the MMSC.INI settings that I was aware of. The previous thread has been updated: http://support.nowsms.com/discus/messages/1/5972.html | |||
