| Cannot send MMS (One MMSC for users in multiple countries) |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 09, 2011 ⬆ |
◄ ► |
| Author | Message | ||||
| Mark B. Matatquin New member Username: Matatquin Post Number: 1 Registered: 12-2010 |
Hi Team, Good day! We would like to raise an issue where the customer cannot send MMS. Below are the details from their email: - Currently some users cannot send MMS messages but are able to receive them (within the network as well). They took a look at the event logs on the server and saw many warnings similar to the message quoted - "NowSMS Error Report. SMS message could not be sent to 7921509, Error: No SMSC defined to route message". It was noticed that these messages occur for messages to the other local carrier as well as international carriers. They are not sure if the first problem mentioned is related to the messages in the event log since there were no messages occur for Digicel numbers but they thought that they should mention it. - The errors were found in the Windows Event Viewer logs on the MMS server. They would like to reiterate that they are not sure if what they are seeing in the logs is related to the service related problem they are having right now. What they can say for sure is that some users are unable to send MMS messages. Thus far, an MSISDN is unable to retrieve MMS messages and receive the following "Could not retrieve message content". Some MSISDN receive a red x on their phone display when sending MMS. The service in use is postpaid. - Attached is an excerpt from the WAPGW logs. They tried sending MMS messages with MSISDN 18683748100, the results are shown in the log file (WAPGW-20101202_4.rar).
We hope to hear from you soon! Thank you in advance! | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2697 Registered: 08-2008 |
Hi Mark, This means that there is no route defined for sending to a recpient address of 7921509. No "MMSC Routing" definition exists to handle this recipient number, and the MMSC is trying to treat this number like a local number ... delivering the MMS notification via SMS. Yet, there is no SMSC routing either. Basically, this is a configuration issue, but I don't know enough (or anything really) about how this system was intended to be configured. I assume this is a new (or relatively new) installation? It appears to be incompletely configured. I do notice that phone numbers are not being internationalised, which is most likely the root of the problem. From the logs, I can see that you are trying to service users in multiple countries: +1868 - Trinidad and Tobago +597 - Suriname However, the MMSC needs to know what countries it is servicing. Without this, the MMSC does not know that 18683748100 is an international number, and it is not applying any international number conversions to recipient addresses. In other words, if +18683748100 tries to send to recipient 7921509, we know that it should be internationalised to +18687921509 ... but the MMSC needs to be configured to do this. It is easy to configure this for a single country, as described here: http://www.nowsms.com/nowsms-operator-mmsc-considerations However, multiple countries, like your setup, is more complex. There is a solution for a similar scenario described in the following thread (an MMSC serving users in both Honduras and El Salvador): http://support.nowsms.com/discus/messages/485/41962.html However, your situation is even more complex than that one, because one of your countries is within an area code within country code +1, which requires special handling. Based upon my limited understanding of your intended configuration, here is what I think you need to configure. Edit MMSC.INI, and under the [MMSC] header, add: MSISDNHeaderPrefixConvert=1868:+1868,597:+597 This setting should allow your 597 subscribers to send MMS messages to each other without any problem. If +5979999999 tries to send to 8888888, the MMSC will see this recipient as +5978888888 and the message will be routed properly. However, the same won't happen automatically for 1868 subscribers, because +1 is the country code, and 868 is an area/city code. (If a 1868 subscriber sends a message to a recipient using the format 1868 or 868, it will be routed properly.) To fix this, you need to enable city code support in the MMSC by adding the following settings to MMSC.INI under the [MMSC] header: LocalNumberMaxLength=7 CityCodeLength=3 The settings won't have any effect on the +597 numbers, because they do not follow this pattern. However, they will affect +1868 numbers. Let's revisit the example of +18683748100 sending to recipient 7921509. The MMSC will evaluate the sender address, and recognise that +1 is the county code. The city code is 3 digits: 868. The local number portion is 7 digits: 3748100. The recipient number matches the local number length, so the city code and country code of the sender are added to it. 7921509 becomes +18687921509. Unfortunately, we're not done yet. I assume that you want subscribers from both country codes to be able to send MMS messages to each other, without requiring them to prefix the recipient addresses with "00" or "+", correct? If +18681234567 tries to send to 005979999999 or +5979999999 or 0115979999999, it will be routed correctly. However, if +18681234567 tries to send to 5979999999, the MMSC will convert this to +15979999999. Simiarly, if +5979999999 tries to send to 0018681234567 or +18681234567, it will be handled correctly. However, if +5979999999 tries to send to 18681234567, the MMSC will convert this to +59718681234567, which is incorrect. The MMSC has additional configuration settings to clean up after these incorrect conversion assumptions. The following settings would allow +1868 and +597 senders to send to each other without requiring them to specify the recipient in international formats. MSISDNRecipientPrefixConvert=+1597:+597,+5971868:+1868,+597868:+1868 Let me summarise all of the above settings recommendations... Edit MMSC.INI, and under the [MMSC] header, add: MSISDNHeaderPrefixConvert=1868:+1868,597:+597 LocalNumberMaxLength=7 CityCodeLength=3 MSISDNRecipientPrefixConvert=+1597:+597,+5971868:+1868,+597868:+1868 Restart the MMSC service after applying these changes. Then try with sending some messages with different recipient formats to verify that all of the formats in common use on your network are handled correctly. It may be necessary to add some more MSISDNRecipientPrefixConvert settings to handle other addressing formats on your network. -- Des NowSMS Support | ||||
