| Configuring MM4 on NowSMS MMSC |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 19, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Nelson New member Username: Nelson Post Number: 10 Registered: 01-2006 |
Hi Bryce, I am working with a small-ish mobile operator that wants to interconnect their NowSMS MMSC to another MMSC (an Ericsson) at another operator. I see in the documentation where the MMSC VASP tab is described. But even with this configuration, they were not able to receive any MMS from the other operator. How do you recommend we troubleshoot this? In addition, from what we understood, the documentation on the NowSMS product only explains how to get MMS from another MMSC through MM4. They would like to be able to both send and receive MMS between the 2 MMSCs. Can you please tell us if this interconnectivity is supported by the NowSMS gateway? How can it be configured? Would you also have answers to their questions below: I have checked the both documents but it does not mention anything about the GRX. Could you confirm whether NOWSMS GRX is compatible for SMTP? Please assist us on this issue; it is quite urgent to get this working. Can you help us with the following? 1. FQDN 2. Address Hiding is supported. 3. Maximum Message Rate? 4. Maximum Message Size? 5. Delivery Report supported? 6. Read Report Supported? Thanks, nelson | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6615 Registered: 10-2002 |
Hi Nelson, The process of interconnecting with another MMSC involves the configuration of two separate "accounts" within the NowSMS MMSC. This initially may seem a little confusing, however we do it this way to provide maximum flexibility. A typical MM4 connection involves defining an "MMSC VASP" account for receiving messages from the other MMSC ... and an "MMSC Routing" account for routing messages to the other MMSC. Now to address your specific questions: First, I want to make reference to the GRX compatibility question. We do not view a GRX any differently from a direct MM4 connection to another MMSC. A GRX is simply viewed as an aggregator. (And MM4 is an SMTP-based protocol. Normally you would connect to a GRX using MM4, but there is also an option in NowSMS, when you configure an MM4 connection that you can use generic SMTP headers instead of MM4 specific SMTP headers, if necessary or desired.)
Considerably more information would be requried in order to troubleshoot this. Simply defining an "MMSC VASP" account authorises another party to connect to the MMSC to deliver messages. However, the other party must successfully connect to the MMSC using this account before any messages will be delivered. At this point, you don't know if there has even been a connection attempt ... the problem could be IP related ... firewall related ... or account authentication related. When initially setting up this type of connection, it can be very difficult to troubleshoot without enabling the MMSCDEBUG.LOG in NowSMS. So I suggest doing this as a first step (checkbox on the "Serial #" page of the configuration). One piece of general advice that I can offer is that most MMSCs do not support any type of authentication for the MM4 connection. They assume that the IP link is secure and firewalled. In NowSMS, this means that you have to define the "MMSC VASP" with an IP address as the account name, as we will authenticate them based upon their source IP address (as there is no other way to authenticate them). When you define this type of setup, leave the password field blank. Beyond that, I suggest enabling the MMSCDEBUG.LOG and looking for any evidence of connection activity from the IP address of the other MMSC. Regarding the other questions.... 1. FQDN - You define the other MMSC's FQDN (a.k.a., Fully Qualfied Domain Name) in the "E-Mail Domain" field when you create the "MMSC Routing" definition for connecting to the other MMSC. Your MMSC's FQDN is the "Domain Name for MMS E-Mail" as defined on the "MMSC" page of the NowSMS configuration. (There are also ways to define aliases for your domain name if necessary ... edit MMSC.INI, and under the [MMSC] section, add DomainNameAlias1=domain1.xyz, DomainNameAlias2=domain2.xyz, etc.) 2. Address hiding is NOT supported. 3. Maximum message rate is dependent on NowSMS license. (We do not throttle received messages over the MM4 interface, but we will throttle delivery of those messages based upon licensing.) 4. We do not impose a maximum message size over the MM4 interface. 5. Yes, delivery report is supported. 6. Read report is supported in NowSMS 2006. Hope that helps! -bn | |||
| sebastian lubinski New member Username: Slubinsk Post Number: 1 Registered: 01-2007 |
Hi, having a MM4 problem on a NowSMS 2006.06.23, in the dialog where you configure the inbound MM4 connection to NowSMS ("MMSC VASP" dialog), I've set the "MM4 Ack Routing:" to an outbound MM4 route previously defined on the ("MMSC Routing" dialog), to specify that any Ack responses will be sent out via that particular MM4 connection instead of via general SMTP. The problem is that the acks are still been sent throught the general SMTP relay defined instead of through the specified routing, is there anything else I'm missing? This MM4 connection is used by intercarrier opertations that, apart from this issue is working ok on both directions. | |||
| Malcolm - Now Support Frequent Contributor Username: Malcolm Post Number: 53 Registered: 12-2006 |
Hi Sebastian, I'm not aware of any issues where the MM4 Ack routing setting is ignored. My guess is that the message is not being properly recognised as coming from the "MMSC VASP" definition for the inbound MM4 connection, causing the "MM4 Ack Routing" setting to be ignored. Is it possible to see an MMSCDEBUG.LOG that shows the MM4 message being received and the ack being routed back out? (You can either post the log in reply here, or e-mail it to nowsms@now.co.uk with "Attention: Malcolm" in the subject line. If you e-mail it, please include a link or description that will allow me to recall this thread, so I know why I asked to see the log file.) Without seeing this debug log file, I'm going to offer a few pointers that might allow you to troubleshoot this problem yourself. Start by confirming that the MMSC is recording the message as originating from the proper "MMSC VASP" definition. Look at the MMSC-yyyymmdd.LOG file, and you should see an "MMSIN" record for messages that come in via an "MMSC VASP" account definition. Somewhere in this "MMSIN" record, there should be a refernece to the "VASP:" account from which the message was received. Make sure that this is what you expect. Next, check VASPIN\mmscVaspAccountName\VASP.INI, and verify that under the [VASP] header in this file is a statement: MM4AckRoute=routename "routename" should be the name of the "MMS Outbound Route" that you want the MM4 acks to be routed via. "routename" should be an MM4 account definition. If this does not help resolve the problem, then I would like to see an MMSCDEBUG.LOG. -- Malcolm Now Wireless Support | |||
| sebastian lubinski New member Username: Slubinsk Post Number: 2 Registered: 01-2007 |
Hi Malcolm, I think I solved the issue, you're right, there was not reference to the VASP account on the log, so I checked the config and have set a string on the VASP account name instead of an IP address. Thanks. | |||
| Pedro Luna New member Username: Pedro01 Post Number: 1 Registered: 05-2007 |
Hi, here's my problem: I've a MM4 problem on a NowSMS 2006.06.23 , I tried to send MMS from an existing MM4 acount , but when I received the MMS , the field "From" appears blank... This is the way: "Other MMSC" ==> my "Zmailer" ==> my "NowSMS" ==> my "Mobile Terminator" In zmailer's log file appears both MSISDN, "Mobile Originator" and "Mobile Terminator". Looking at the NowSMS logs files, I can see something like these : 2007-04-20 17:13:08,MMSIN,172.25.7.7,,+541154650001,20070420/17/FE37DAED,6B0BFFA2.req,10966 0 2007-04-20 17:13:11,6B0BFFA2.req,,+541154650001,OK -- SMPP - 172.25.7.41:5016,SubmitUser=localsystem-mmsc;SMSCMsgId=507_0003E759;Binary=1;DCS =F5;UDH=0605040B8423F0;Data=B906226170706C69636174696F6E2F766E642E7761702E6D6D73 2D6D65737361676500AF848C82984645333744414544008D90890280008A808E0277F08805810309 3A8083687474703A2F2F3137322E32352E372E33312F32303037303432302F31372F464533374441 45442E4D4D533F69643D25326235343131353436353030303100 2007-04-20 17:13:53,MMSRETRIEVE,172.16.0.28,,+541154650001,20070420/17/FE37DAED.MMS,OK,2080 2 In the first and third line, the originator MSISDN isn't present. Had you some similar matter? Do you know the reason of this matter? Many thanks,Regards,Pedro. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7174 Registered: 10-2002 |
For the last message on this thread, see http://support.nowsms.com/discus/messages/485/21388.html | |||
