MMSRoutingURL and DirectDelivery

MMSRoutingURL and DirectDelivery SearchSearch
Author Message
No Name
New member
Username: Ncblx

Post Number: 15
Registered: 02-2014
Posted on Friday, October 31, 2014 - 07:38 pm:   

How can we disable the Default Route to during sending to the inside network MMS not sent DirectDelivery and through the specified Aditional Route
This file was added on MMSC.INI DisableMMSDirectDelivery = Yes and ForceRoutingCallback = Yes
How to create Aditional Route whatever subscriber within the network sent using it.
We need that during sending MMS in all directions, even within the network causes MMSRoutingURL
No Name
New member
Username: Ncblx

Post Number: 16
Registered: 02-2014
Posted on Saturday, November 01, 2014 - 12:23 pm:   

And we have another problem

ThreadProcessConnection: TO: D3000516808301/TYPE=PLMN
ThreadProcessConnection: Invalid Recip: TO: D3000516808301/TYPE=PLMN
ThreadProcessConnection: No valid recipients!

MSISDN before you need to add the value of D100,D200 or D300
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5102
Registered: 08-2008
Posted on Tuesday, November 04, 2014 - 04:32 pm:   

Hi,

I'll answer the easy question first:

Alphanumeric recipient values (except email addresses) are not not normal, and are rejected because they are usually a mistake.

However, there is a setting to enable alpha numeric recipient. When set it applies both to SMS and MMS. In the SMSGW.INI file, under the [SMSGW] header, add AllowAlphaRecip=Ye--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5103
Registered: 08-2008
Posted on Tuesday, November 04, 2014 - 04:34 pm:   

On the first question, I'm sorry but I don't understand. Can you explain with an example?
No Name
New member
Username: Ncblx

Post Number: 17
Registered: 02-2014
Posted on Friday, November 07, 2014 - 09:34 am:   

On the first question we solved.

How can send MMS to E-Mail?
a can not find configuration istruction.

Thanks.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 8098
Registered: 10-2002
Posted on Monday, November 10, 2014 - 06:23 pm:   


quote:

How can send MMS to E-Mail?




By default, the MMSC acts as an SMTP server and will attempt to send MMS to email directly if a message is addressed to an email address.

Configuration settings are on the MMSC or E-Mail page depending on the version.

"Smart Mailer" means that the MMSC performs DNS MX record lookups directly and connects directly to external SMTP servers to send email.

Alternatively, another SMTP server can be used as a relay host, which means that when there is an outbound email to send, the MMSC makes an SMTP connection to the relay host to send email messages.

Newer versions have an alternate configuration to route all email via a common shared mailbox, instead of the MMSC having its own email domain name.

-bn

Bryce Norwood
Now SMS/MMS Support
No Name
New member
Username: Ncblx

Post Number: 18
Registered: 02-2014
Posted on Wednesday, November 12, 2014 - 08:32 am:   

send mms to email worked normaly,
but we can not recive mms.
can you help configure?
NowSMS v.2014.06.30
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5110
Registered: 08-2008
Posted on Thursday, November 13, 2014 - 05:24 pm:   

If NowSMS is configured to act as an SMTP mail server, the same considerations apply as for any other SMTP server.

An SMTP server listens for incoming email, waiting for other SMTP mail servers to connect on TCP port number 25 when there are messages to be delivered.

In order for this to happen, other SMTP servers need to know how to connect to your server when they have a message to deliver to your domain.

Within an enterprise mail system, another SMTP server may be configured to relay messages for your SMS domain name. Otherwise the following steps must be taken:

1.) An internet DNS hostname (A or CNAME) record must exist and resolve to an IP address that allows external connections to the SMTP Port (TCP Port 25) on the NowSMS server.

2.) If the NowSMS server is behind a router or firewall, a port forward entry may need to be defined in the router or firewall to allow external connections.

3.) An internet DNS MX (Mail eXchange) record must exist for the domain name portion of the SMS e-mail address, pointing to the A or CNAME record that points to the NowSMS server.

DNS considerations such as the above are not specific to NowSMS, they are basic considerations for any SMTP server.

An additional note about sending email out from the MMSC.

As I mentioned earlier, NowSMS can either function as an “SMTP Smart Mailer” or relay all outbound mail through another SMTP server that acts as an “SMTP Relay Host”. When acting as a smart mailer, NowSMS performs DNS MX record lookups and connects directly to destination SMTP servers to deliver e-mail messages. Some SMTP servers may consider your e-mail messages to be SPAM if you are connected to an ISP with a consumer (not business) account. Some SMTP servers will also reject your e-mail if there is no reverse DNS record (in-addr.arpa PTR record) associated with the IP address of your NowSMS server.

These DNS considerations can be very complex. Further information on these DNS concepts can be found in the following Wikipedia articles:
http://en.wikipedia.org/wiki/Domain_Name_System
http://en.wikipedia.org/wiki/List_of_DNS_record_types
http://en.wikipedia.org/wiki/MX_record
http://en.wikipedia.org/wiki/Reverse_DNS_lookup


--
Des
NowSMS Support
No Name
New member
Username: Ncblx

Post Number: 20
Registered: 02-2014
Posted on Thursday, December 04, 2014 - 01:12 pm:   

Hello.
I can not configure send delivery report VASP accoun

I crate VASP accout via MM7.
I look trace and I find X-MMS-Delivery-Report=Yes

but dont sent report to VASP
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5126
Registered: 08-2008
Posted on Thursday, December 04, 2014 - 05:25 pm:   

Hi,

I don't have enough information to answer your question. Or to even make a guess.

I need details of the message flow. How the message is being submitted, and the path it takes through your system. And I need details of whatever specific aspects of the trace along that path are not as expected. It would also help to understand what you expected to see but did not.

--
Des
NowSMS Support
No Name
New member
Username: Ncblx

Post Number: 21
Registered: 02-2014
Posted on Friday, December 05, 2014 - 01:20 pm:   

I create VASP
adn MMSC routing http://support.nowsms.com/discus/messages/485/41516.html

Please see attached file.


application/octet-stream
MMSDEBUG.LOG (363.4 k)
application/octet-stream
DUMP.pcap (24.8 k)
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5130
Registered: 08-2008
Posted on Monday, December 08, 2014 - 04:07 pm:   

I am not sure what specific transactions are in question.

I do see an inbound MM7 submission with:

<mm7:DeliveryReport>true</mm7:DeliveryReport>

This seems to get translated to an outbound MM7 submission in Ericsson format, which includes:

<Delivery-Report xsi:type="xsd:boolean">True</Delivery-Report>

So, the delivery report request is being forwarded. (The outbound URL is incorrect, so it is not actually forwarded.)

It is the responsibility of that upstream MMSC connection to generate a delivery report, which would be posted back via MM7/HTTP.

That said, the upstream connection uses the Ericsson proprietary version of MM7, and our implementation does not support delivery reports on that interface. Do your traces so any HTTP POST from the upstream MMSC with delivery reports?

Am I even looking at what you are asking about?

--
Des
NowSMS Support
No Name
New member
Username: Ncblx

Post Number: 22
Registered: 02-2014
Posted on Monday, December 08, 2014 - 05:29 pm:   

At the moment of receiving of Email2SMS, we are not able to check whether the subscriber has Email2SMS service or not.

In order to implement this function, at the moment of AccountingCallBack, type should be Type=SMSEmail. But for the both cases (Email2SMS and Email2MMS), we receive Type=MMSEmail.

For Email2SMS, the type need to be changed to Type=SMSEmail.

Otherwise, please, suggest us another decision.

The service need to be checked from the DB. In the DB, specific values need to be checked for subscriber.

If the mentioned values exist, subscriber receives Email2SMS.

Otherwise, message will not be delivered.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5135
Registered: 08-2008
Posted on Tuesday, December 09, 2014 - 08:58 pm:   


quote:

In order to implement this function, at the moment of AccountingCallBack, type should be Type=SMSEmail. But for the both cases (Email2SMS and Email2MMS), we receive Type=MMSEmail.

For Email2SMS, the type need to be changed to Type=SMSEmail.




I discussed this with our engineering team, and they agreed with this solution.

An update with this change will be posted later this week.

--
Des
NowSMS Support
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 5139
Registered: 08-2008
Posted on Thursday, December 11, 2014 - 04:45 pm:   

Follow-up.

There is an updated version of NowSMS at http://www.nowsms.com/download/nowsms20141209.zip

Relevant change note:

* Accounting callback for SMTP email to SMS now uses Type=SMSEMail to distinguish from SMTP email to MMS which continues to use Type=MMSEMail. The callback is still classified as an MMS accounting callback because it is processed by the MMSC.


--
Des
NowSMS Support
No Name
New member
Username: Ncblx

Post Number: 24
Registered: 02-2014
Posted on Friday, December 12, 2014 - 05:27 am:   

Thanks.

It's worked and solved out problem