MM4 message get split after 79 chars | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
Author | Message | |||
Robert Kristensen New member Username: Linkmobilitymms Post Number: 2 Registered: 11-2015 |
Hi Support We get A recipient unknown or not local, when receiving DR. 220 SMTP Ready HELO smsimm4.sktelink.com 250 Ok MAIL FROM: <+REMOVED/TYPE=PLMN@REMOVED> 250 Ok RCPT TO:<+01012345678/TYPE=PLMN@mms02.coolsmsc.dk> 550 Recipient unknown or not local DATA 503 Invalid sequence, no recipients (RCPT TO) specified X-Mms-3GPP-MMS-Version: 4.3.0 X-Mms-Message-Type: MM4_forward.RES X-Mms-Transaction-ID: "20151109-09-28B8081C--pREMOVED--01012345678" X-Mms-Message-ID: "20151109-09-28B8081C@10.115.0.126" Message-ID: "20151109-09-28B8081C@10.115.0.126" To: +01012345678/TYPE=PLMN Date: Mon, 09 Nov 2015 08:38:53 GMT From: +REMOVED/TYPE=PLMN X-Mms-Request-Status-Code: 1000 . 500 Unknown command QUIT 221 Goodbye We have created a MMSC VASP, with the same as the MMSC Routing, but somehow Nowsms will not accept mail to that recipient? | |||
Robert Kristensen New member Username: Linkmobilitymms Post Number: 3 Registered: 11-2015 |
Sorry wrong subject | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5493 Registered: 08-2008 |
Hi, Make sure all IP addresses used by the partner are defined as VASP account names, so that messages will be accepted from them. For now, set them for standard MMS delivery receive processing. Make sure the MMS domain name defined on the MMSC or Email pages matches the TO domain name you see in SMTP. If you're using accounting callbacks, turn them off for testing as they could be refusing the message. -- Des NowSMS Support | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5494 Registered: 08-2008 |
There also might be helpful info here. http://www.nowsms.com/mmsc-mm4-interconnection-basics | |||
Robert Kristensen New member Username: Linkmobilitymms Post Number: 4 Registered: 11-2015 |
Our provider asks us to send: X-Mms-Delivery-Report:Yes I have added:SMTPExtraHeader=X-Mms-Delivery-Report:Yes to mmsc.ini in the [mmsc] section, but the header does not get included: X-Mms-3GPP-MMS-Version: 4.3.0 X-Mms-Message-Type: MM4_forward.REQ X-Mms-Transaction-ID: "20151110-11-300E972A--pREMOVED--01012345678" X-Mms-Message-ID: "20151110-11-300E972A@10.115.0.126" X-Mms-Ack-Request: Yes X-Mms-Originator-System: system-user@mms02.coolsmsc.dk Message-ID: <20151110-11-300E972A@10.115.0.126> Date: Tue, 10 Nov 2015 11:04:27 +0100 Sender: 01012345678/TYPE=PLMN@mms02.coolsmsc.dk From: 01012345678/TYPE=PLMN To: +REMOVED/TYPE=PLMN Subject: 01012345678 | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5495 Registered: 08-2008 |
Hi, That setting will only affect messages routed via the generic SMTP handler. For example, if a local MMS Subscriber sends a message to an email address. If the message is being routed to a defined MM4 connection, there are settings specific to that connection. Edit VASPOUT\routename\VASP.INI for the route, and under the [VASP] header add: ExtraHeader=X-Mms-Delivery-Report: Yes -- Des NowSMS Support |