MMSC VAP requires recipient to be defined locally

MMSC VAP requires recipient to be defined locally SearchSearch
Author Message
Awal Junanto
New member
Username: Junanto

Post Number: 1
Registered: 04-2009
Posted on Wednesday, April 08, 2009 - 04:42 pm:   

Hi,

I am currently trying to configure Now SMS/MMS Gateway v2008.11.05 as MMS receiver-only gateway. My objective is to receive MMS via MM4 and deliver it to the recipient directly (via SMSC which I already have configured and tested successfully).

I have defined one MMSC VASP profile, which I call MM4IN, with the following parameters:

- Accept Connections via: MM4
- MM4 Ack Routing: MM4OUT (an MMSC Routing profile which I created and tested successfully)
- IP Address Restrictions: A.B.C.* (to accept connection from any MMSC in A.B.C.0 subnet)
- MMSC Routing for Received Messages: Force via Defined Route = Direct Routing

When I tested this setup, I can see the following from MMSCDEBUG.LOG:

12:38:46:896 [12] ThreadProcessConnectionSMTP: MAIL FROM:<+33600000000/TYPE=PLMN@mms.foo.grx>
12:38:46:896 [12] SendCommand: 250 Ok
12:38:46:896 [12] ThreadProcessConnectionSMTP: 250 Ok
12:38:46:943 [12] ThreadProcessConnectionSMTP: RCPT TO:<+33611111111/TYPE=PLMN@mms.mnc099.mcc999.gprs>
12:38:46:959 [12] SendCommand: 550 Recipient unknown or not local

Which shows that MM4 Forward REQ was rejected with cause "Recipient unknown or not local". Normally I should have defined +33611111111 as a normal MMS Users.

However, it is impossible for me to define each individual user in the Gateway.

Is there any way to "force" the Gateway to accept incoming MM4 for any user and deliver the MMS directly without checking internal user database?

Many thanks,


.
Awal Junanto
New member
Username: Junanto

Post Number: 2
Registered: 04-2009
Posted on Wednesday, April 08, 2009 - 10:00 pm:   

Hi again,

I read in the manual document that there is a way to do provision MMSC user automatically for the sender using MSISDNHeaderAutoProvision flag.

However, this feature might not be useful for me since the Gateway is a receive-only Gateway.

I need the same feature for the receiver (MMSC VASP receiver).

Or a way to configure the Gateway to bypass user database and deliver MMS directly.

Many thanks,


.
Des - NowSMS Support
Board Administrator
Username: Desosms

Post Number: 674
Registered: 08-2008
Posted on Thursday, April 09, 2009 - 04:35 pm:   

Hi Awal,

Are any SMTP AUTH commands being sent by the other party?

Most real-world MM4 connections don't support SMTP AUTH. In those situations, you need to define the name of the "MMSC VASP" account to be the source IP address of the other party. (And if they connect from multiple IP addresses, multiple "MMSC VASP" connections must be defined.)

Also, make sure that your "Default Route" for the "MMSC Routing" is "Direct Delivery".

I'm assuming that you can send MMS messages ok from the web interface of NowSMS. Correct?

--
Des
NowSMS Support
Awal Junanto
New member
Username: Junanto

Post Number: 3
Registered: 04-2009
Posted on Thursday, April 09, 2009 - 09:08 pm:   

Hi Des,

Thanks for the reply.

There's no SMTP AUTH sent by MMSC sender. I have to use authentication by IP address with wildcard '*' at the end since there are two possible IP addresses from which MM4 Forward REQ may originate.

Now as suggested:

- I have replaced this single MMS4IN MMSC VASP profile with two profiles; each for each MMSC sender's IP address.

- I have changed "Default Route" for the "MMSC Routing" is "Direct Delivery". Previously, it was set to MMS4OUT.

- And restarted the services (SMSC and MMSC) to make sure that all config changes are reloaded.

And I still got this same error:


21:05:09:479 [12] ThreadProcessConnection: Thread started
21:05:09:479 [12] ThreadProcessConnectionSMTP: Processing SMTP connection from xxx.xxx.xxx.xxx...
21:05:09:479 [12] SendCommand: 220 SMTP Ready
21:05:09:479 [12] ThreadProcessConnectionSMTP: 220 SMTP Ready
21:05:09:526 [12] ThreadProcessConnectionSMTP: ehlo mms.foo.grx
21:05:09:526 [12] SendCommand: 250-Ok
250-AUTH LOGIN
250 HELP
21:05:09:526 [12] ThreadProcessConnectionSMTP: 250-Ok
250-AUTH LOGIN
250 HELP
21:05:09:573 [12] ThreadProcessConnectionSMTP: MAIL FROM:<+33600000000/TYPE=PLMN@mms.foo.grx>
21:05:09:573 [12] SendCommand: 250 Ok
21:05:09:573 [12] ThreadProcessConnectionSMTP: 250 Ok
21:05:09:604 [12] ThreadProcessConnectionSMTP: RCPT TO:<+33611111111/TYPE=PLMN@mms.mnc099.mcc999.gprs>
21:05:09:620 [12] SendCommand: 550 Recipient unknown or not local
21:05:09:620 [12] ThreadProcessConnectionSMTP: 550 Recipient unknown or not local
21:05:09:651 [12] WaitForResponsePOP3: ioctlsocket reports no more data
21:05:09:651 [12] ThreadProcessConnectionSMTP: Closing SMTP Connection
21:05:09:651 [12] ThreadProcessConnection: Thread ended


I really don't know what I have done wrong here.


:-(
Awal Junanto
New member
Username: Junanto

Post Number: 4
Registered: 04-2009
Posted on Thursday, April 09, 2009 - 09:18 pm:   

Oh I forgot to do one more thing which turns out to be the missing link; I renamed the profile to the individual IP address.

And it works now.

Many thank Des,

:-)