| Alphanumeric Recepient |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through July 28, 2010 ⬆ |
◄ ► |
| Author | Message | ||||
| Hussam Dahbour |
Dear, We are required to post SMS Message to a Distribution List @ Operator's Side, we are supposed to send SMS to: dl:1234, when we try to send from NOWSMS, it ignores dl: and send message to 1234, We need to send to dl:1234 urgently is this avalable in nowsms, my version is Nowsms 2006 Thanks | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2089 Registered: 08-2008 |
Hi, I'm sorry, but alphanumeric recipients (destination) are not supported. Alphanumeric senders (source) are supported. What your operator is suggesting is very unusual. I've never encountered a situation that required this. We can investigate adding support for this in a future release, but currently alphanumeric recipients are not supported. -- Des NowSMS Support | ||||
| Hussam Dahbour New member Username: Hussam83 Post Number: 2 Registered: 08-2005 |
Hi Des, Thanks for your reply, Operator required us to integrate with Ericsson SDP, this SDP requires us to send to a Distripution List instead of phone number, distriputin list starts with "dl:" as: dl:12345 | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2131 Registered: 08-2008 |
Hi Hussam, We're working on an update with an optional configuration parameter to enable alphanumeric recipients on SMPP connections. It will be ready in approximately 24 to 48 hours. -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2169 Registered: 08-2008 |
Hi Hussam, My original estimate was incorrect. However, there is an update available now to support this. http://www.nowsms.com/download/nowsmsupdate.zip The readme file neglects to mention it, however the following configuration setting can be applied under the [SMSGW] section of SMSGW.INI: AllowAlphaRecip=Yes This setting will only work for SMPP environments. -- Des NowSMS Support | ||||
| John Marcos |
Dear Des, Thank you allot for your help. what you did make NowSMS at the top of the list that fix this problem compared with other SMSC Gateway. We tried most of the popular Gateway and non of them able to send alphanumeric destination. Now the challenging in MMS. can you pls have the same patch for submitting MMS over MM7 Protocol with alphanumeric recipient? Thanks | ||||
| John Marcos New member Username: Ttagroup Post Number: 2 Registered: 02-2004 |
Also, When we try to select XML Scheme REL-5-MM7-1-2 Only one version of MM7 (V5.3.0) appears!!! while the operators required to have XML Scheme REL-5-MM7-1-2 with MM7 V5.5.0? Any help? | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2268 Registered: 08-2008 |
Hi John, You can manually edit the VASPOUT/accountname/VASP.INI to set the version number that you want. There are so many possible combinations that the configuration only allows combinations that are legal. If you look at http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2, you'll see that the version number field is restricted to an enumerated list of values, of which 5.3.0 is the only valid one. The actual v5.5.0 specification does reference REL-5-MM7-1-2. However, the version number 5.5.0 is not a legal value in the XML. And if you look through the v5.5.0 spec, you'll see that all of the MM7 examples use 5.3.0 as the version number, because the version number is restricted by the XML schema. We didn't used to be so picky in the configuration program. However ... we were having too many problems with users arbitrarily picking different spec/version combinations. If the MMSC performs strict XML schema validation (as some do), invalid version/schema combinations would result in errors. For now, try manually setting it ... if you really need to. If you find that this combination is needed (please let us know), we will lessen the strictness of the configuration program in a future update. -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2269 Registered: 08-2008 |
Hello again John, I almost missed the other part of your question. The problem with alphanumeric recipients in MM7 is also XML related. Individual recipients must be submitted as either <RFC2822Address>, <Number> or <ShortCode>. The fields are not strictly typed, so XML (REL-5-MM7-1-2 and later) would allow you to put in an alpha character in any of these fields. However, the spec itself defines other restrictions. Reading section 7.2.3, and referring back to 7.2.1, it does appear that a non-email address format alphanumeric recipient is legal as a short code. So we are probably too picky in not allowing an alphanumeric short code as a sender or recipient. Can you explain your MMS message flow (you're interfacing to the operator via MM7, how are you interfacing with NowSMS?). I'm going to ask our engineering team to remove this restriction. However, to make sure we don't miss something, I'd like to make sure I understand your message flow. Also, is the MM7 recipient format similar to the one above for SMS? That is, containing a ":" character? I'm concerned that the ":" character isn't technically legal as part of a recipient value, because an alphanumeric short code is defined as an unqualified RFC2822 e-mail address (i.e., the part before the "@" ... which I'll call the mailbox user name). The ":" character is not valid in the mailbox user name part of an e-mail address, unless you put quotes around it. So if I interpret this correctly, in MM7, following these rules, you would encode dl:1234 as "dl:1234" (with quotes). However, I seriously doubt your provider is expecting quotes. I'm probably reading the specs too much, and we should just be loose and allow it. So, please explain your message flow, and I'll see what we can do. I'm assuming that it is the same use case as for SMS ... a distribution list at the provider? -- Des NowSMS Support | ||||
| John Marcos New member Username: Ttagroup Post Number: 3 Registered: 02-2004 |
Hi Des, First of all, thank you for all above details. NowSMS is very lucky to have some one like you in their team. Regarding your questions, our message flow starts when we want to send a message to group of subscribers (Distribution List at the operator side) through operator new SDP. Operator required from us to send the SMS/MMS to recipient with the format dl:12345. the format containing ":" and the operators does not expect quotes around it "dl:12345" We usually use the HTTP to post MMS through NowSMS. Looking forward to hear from you, | ||||
| John Marcos New member Username: Ttagroup Post Number: 4 Registered: 02-2004 |
Dear Des, We got another update regarding the alphanumeric recipient in SMS, we are unable to send long/concatenated SMS to dl:12345, although the short SMS can be sent successfully to dl:12345 BR | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2289 Registered: 08-2008 |
Hi John, With the long SMS, what happens? Do you receive a corrupt message, or some sort of error? This may be more of an issue with the service provider and how they have implemented long SMS support. It may require questions to be asked of the service provider. When you are using SMPP, there are essentially four different ways that NowSMS can be configured to send long SMS messages over the SMPP connection. Different providers may require the use of different techniques (or in the case of the type of system you describe, they may have failed to consider long SMS support completely). Try each of the different ways that NowSMS can encode long SMS for SMPP environments. These settings are all configured under "Advanced Settings" for an SMPP connection. When configuring these settings, remember to press Ok, Ok and Apply to save them. The service then needs to restart to enable the new settings. 1.) "Encode long messages with 7-bit packed encoding" - NOT CHECKED "Use TLV parameters for port numbers and segmentation" - NOT CHECKED 2.) "Encode long messages with 7-bit packed encoding" - CHECKED "Use TLV parameters for port numbers and segmentation" - NOT CHECKED 3.) "Encode long messages with 7-bit packed encoding" - NOT CHECKED "Use TLV parameters for port numbers and segmentation" - CHECKED 4.) "Use WDP Adaptation" - CHECKED (other settings referenced above will be ignored) Long SMS messages (> 160 characters text, or > 140 characters binary, or > 70 characters Unicode) have to be segmented for sending over the air. Options 1 & 2 segment the long message and build the necessary UDH for segmenting the message in GSM environments. (Different SMS providers expect the text to be encoded in different ways when this is done.) Option 3 segments the long message but uses SMPP parameters that tell the other SMPP system how the message is segmented. (These parameters are optional in the SMPP specification, and in the real world, they are not very widely implemented.) Option 4 doesn't segment the long message at all. Instead, the long message is submitted via SMPP using the optionally implemented message_payload interface. (NowSMS logs will show the message being segmented, but it is submitted as a complete long message in a single SMPP transaction.) The naming of this option is admittedly confusing as it was originally implemented for a different purpose. If I had to guess, in your case, I'd guess the provider might support option 4. But basically, you have to try to see if any of these encoding techniques work. If none of them work, then you'd have to ask your provider. It is always possible that they failed to consider this in the distribution list implementation. -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2290 Registered: 08-2008 |
P.S. - I have an update for you on the MM7 alphanumeric recipient issue. The update can be downloaded at http://www.nowsms.com/download/nowsms20100628.zip For now, the alpha recip is only supported via MM7 when the same configuration parameter previously applied for SMS is used: AllowAlphaRecip=Yes under [SMSGW] in SMSGW.INI. | ||||
| Hussam Dahbour New member Username: Hussam83 Post Number: 3 Registered: 08-2005 |
Dear Des, Thanks alot for your support, I tested sending long messages but nothing Logged and in Q Folder I found a file with name "SAR-dl" 0 KBs in Size generated when sending long message to dl:12345 I expect that the character ":" makes a problem when creating File Thanks | ||||
| Hussam Dahbour New member Username: Hussam83 Post Number: 4 Registered: 08-2005 |
In MMS, I am trying to send MMS to dl:12345 but getting Error 4003 Unsupported Operation Knowing that operator required http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2 with 5.5.0 Thanks  | ||||
| John Marcos New member Username: Ttagroup Post Number: 5 Registered: 02-2004 |
Dear Des, I'v tried both the long message (all four options) and MMS after patching. All of them appear in the "Submit" stat in NowSMS, but non of them goes to "Sent". and when we do a TCPDump Capture, we cann't see any traffic coming from NowSMS and going to the operator destination IP. While when we send one SMS, it appears on the Sent and we can see the TCP/network capture for that. It seems that NowSMS is not sending the messages (long message nor MMS) with the distribution list dl:12345 Any suggestions? if you have email, I can sent you the traffic capture and any additional docs. BR | ||||
| John Marcos New member Username: Ttagroup Post Number: 6 Registered: 02-2004 |
Hussam, Check Des post about the Rel-5-MM7-1-2 and v5.5.0, it will help you to fix it BR | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2300 Registered: 08-2008 |
Hussam & John, There is definitely a problem sending a long SMS to a recipient address that contains a ":" character. We are trying to get that resolved. As noted, it has to do with the file naming convention that we are using for long SMS messages. For the MMS issue ... Hussam, please try manually editing the VASPOUT/accountname/VASP.INI to manually set the version number to be used with that schema. (As noted above, the actual XML schema does not allow 5.5.0 to be specified as the version number, which is why it cannot be selected in the user interface.) John ... are you having problems submitting MMS as well? Is any MM7 data going to the operator? If you send to a number instead, does MM7 data go to the operator? If you want to send a trace, you can send it to nowsms@nowsms.com. Put "Attention: Des" in the subject line. Don't bother sending a trace for the long SMS issue ... it is an issue specific to ":" in the address that we will have to work-around. -- Des NowSMS Support | ||||
| Hussam Dahbour New member Username: Hussam83 Post Number: 5 Registered: 08-2005 |
Dear Des, I tried to set 5.5.0 with same error | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2301 Registered: 08-2008 |
Are you able to send MMS messages to regular numbers via this MM7 connection? Enable the MMSCDEBUG.LOG and try again. I'd like to see the MM7 request and response to see if there are any obvious problems with it. (If you want to e-mail it, send it to nowsms@nowsms.com with "Attention: Des" on the subject line.) We may end up needing to get your provider involved in troubleshooting this, as there may be some other trick that is required in order for the message to go out to their distribution list. That's why if you have the ability to send to a normal phone number recipient with this MM7 connection, it would be useful to determine whether the problem is specific to these distribution lists only. If normal phone numbers also fail, it is possible that the provider requires that you use particular VASPID, VASID and/or ServiceCode values that are not being set. -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2302 Registered: 08-2008 |
I got some logs from one of your colleagues, but not the MMSCDEBUG.LOG. I suspect it is going to take some guesswork to figure out what exactly it is that your provider expects. I think we should start with the MMSCDEBUG.LOG. Unfortunately, the MM7 documentation from your provider lacks a lot of detail ... except that it does confirm that the "5.5.0" version number is a non-issue ... the provider ignores your input version number, and always returns "5.3.0". (This is consistent with what I described earlier ... the REL-5-MM7-1-2 schema only allows version "5.3.0".) -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2303 Registered: 08-2008 |
I also have an update for you on the long SMS issue to the distribution list name that contains a ":" character. http://www.nowsms.com/download/nowsms20100630.zip | ||||
| Hussam Dahbour New member Username: Hussam83 Post Number: 6 Registered: 08-2005 |
Dear Des, I will test Long SMS Issue, for Logs, please find MMSCDEBUG.LOG Attached
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2306 Registered: 08-2008 |
Hi Hussam, I think you're going to need to ask your provider for guidance. What I see is that you are attempting to post to http://10.227.19.24:20003/MM7Access/servlet/MM7Servlet (MISCSDP) However, no response at all is coming back from the server to indicate that a problem has occurred. The provider simply closes the connection. Usually what this means is that there is a problem with the URL ... or possibly that the provider needs to open up your IP address in their firewall, or authorise your IP address for your account in their MM7 receiver. There is a 4003 error that occurs, but this is an odd one. What is happening is that NowSMS is running out of retry attempts for this MM7 delivery attempt. When this happens, it is generating a non-delivery report back to the sender. That delivery report is being routed to your MISC connection, and the connection is simply reporting back an error that it will not accept a delivery report. I'm a little confused by this, because NowSMS should not generate a non-delivery report when no delivery report was requested. It should just silently discard the message and record a failure in the log. This issue is not related to the core problem, however, which I think you will need to consult with your provider on .... and ask them what they are seeing from their end. I'm guessing its the wrong URL or port, or your IP address needs to be authorised on their end. -- Des NowSMS Support | ||||
| Hussam Dahbour New member Username: Hussam83 Post Number: 7 Registered: 08-2005 |
I have another log for you, can you take a look again
| ||||
| Hussam Dahbour New member Username: Hussam83 Post Number: 8 Registered: 08-2005 |
Dear Des, for Long SMS it goes fine ... Tahnks a million | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2316 Registered: 08-2008 |
Hi Hussam, Apologies for the delay in response. It is not clear to me why the MMSC is returning an unsupported operation error. I can only think of the following possibilities: 1.) Maybe the MMSC does not like your sender address of "misc". Has the provider told you what sender addresses you are allowed to use? Maybe you could try an e-mail address if you have not been assigned a short code. 2.) I notice that this MMSC is not using any line breaks in its response. There is a checkbox option in NowSMS when defining an MM7 outbound connection to tell NowSMS not to include any white space when submitting to the MMSC. Try checking this option. Beyond that, I think you will have to ask your provider for advice. One thing that would help is if they can give you a working example from another customer or perhaps a test connection that they are running. That may give a clue as to what type of formatting is expected. -- Des NowSMS Support | ||||
| Hussam Dahbour New member Username: Hussam83 Post Number: 9 Registered: 08-2005 |
Dear Des, Here is another Log with your advices above Please take a look
| ||||
| Ahmed New member Username: Ahmedd Post Number: 1 Registered: 06-2010 |
dear is there any release that let us send SMS or MMS to receiver address like this (dl:12345) | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2362 Registered: 08-2008 |
Hi, The updates referenced earlier in this thread allow alphanumeric recipients to be specified for SMPP (SMS) and MM7 (MMS). http://www.nowsms.com/download/nowsms20100630.zip AllowAlphaRecip=Yes must be specified in the [SMSGW] section of SMSGW.INI to enable support for alphanumeric recipient addresses. SMPP is apparently working for sending to an alphanumeric recipient for the above provider. However, MM7 is not working for an alphanumeric recipient. More information is needed from the provider in order to resolve this issue, as it is not clear why the provider is rejecting attempts to send to the supposedly correct alphanumeric recipient address. If the provider could provide an example of a working MM7 submission to one of their alphanumeric addresses, that would provide some clues. Currently, we see no reason why this should not work based upon the specifications supplied by this provider. -- Des NowSMS Support | ||||
MMSCDEBUG
MMSDEBUG
