Difference between revisions of "MMSC Configuration"

From YateBTS
Jump to: navigation, search
Line 1: Line 1:
;If you need the ability for all connected handsets (smartphones and feature phones) to be able to send/receive MMS messages this is the page you are looking for.
+
If you need the ability for all connected handsets (smartphones and feature phones) to be able to send/receive MMS messages this is the page you are looking for.
  
We did interoperate with the MMSC element of CompanyX <!-- NowSMS --> for a commercial network that does support regular MMS and attachments.  
+
We did interoperate with the MMSC element of [https://www.nowsms.com/productinfo/mmsc NowSMS] for commercial networks that support regular MMS and attachments.  
  
Not sure about Group Messaging, maybe their documentation would help. <!-- [https://www.nowsms.com/now-sms-group-text-messaging] -->
+
For Group Messaging please check their [https://www.nowsms.com/now-sms-group-text-messaging documentation].
  
 
The addition of MMS requires:  
 
The addition of MMS requires:  
*Setting up a separate "mms" AP through which handsets are allowed to reach the MMSC
+
* Setting up a separate "mms" AP through which handsets are allowed to reach the MMSC
*Installing an add-on package '''yate-ucn-icap''' that provides subscriber identification and header enrichment via ICAP.
+
* Installing an add-on package '''yate-ucn-icap''' that provides subscriber identification and header enrichment via ICAP.
*Setting up the MMSC (CompanyX<!-- NowSMS -->) itself, you should get support from them
+
* Setting up the MMSC (NowSMS) itself, you should get support from them
*Setting up a SMPP connection from CompanyX <!-- NowSMS --> to YateSMSC component for new message notifications
+
* Setting up a SMPP connection from NowSMS to the YateSMSC component for new message notifications
 
+
;We can provide samples of the relevant configuration for the CORE Network components.
+
  
  
Line 18: Line 16:
  
 
There is no MMS Access Point configured so you need to add one using the MMI web interface:
 
There is no MMS Access Point configured so you need to add one using the MMI web interface:
*Click on the My Network tab
+
* Click on the My Network tab
*Click on the APNs tab
+
* Click on the APNs tab
*Click on the Add link
+
* Click on the Add link
*Click on Advanced
+
* Click on Advanced
*Fill in the following fields:
+
* Fill in the following fields:
 
<pre>Name: mms
 
<pre>Name: mms
 
IPv: IPv4
 
IPv: IPv4
Line 30: Line 28:
 
Address: 10.0.4.3 (or copy it from another APN if you changed MiniCore configuration
 
Address: 10.0.4.3 (or copy it from another APN if you changed MiniCore configuration
 
</pre>
 
</pre>
*Click on Save
+
* Click on Save
*Click on Finish
+
* Click on Finish
*Click on the Equipment tab
+
* Click on the Equipment tab
*Click Control node on YateUCN
+
* Click Control node on YateUCN
*Click Edit
+
* Click Edit
*Click GGSN/PGW
+
* Click GGSN/PGW
*Click the Add link in Tunnels
+
* Click the Add link in Tunnels
*Click on Advanced
+
* Click on Advanced
*Fill in the following fields:
+
* Fill in the following fields:
 
<pre>Tunnel: tun-mms
 
<pre>Tunnel: tun-mms
 
IPv4 Pool: 10.0.150.2-10.0.150.254
 
IPv4 Pool: 10.0.150.2-10.0.150.254
Line 45: Line 43:
 
Interface MTU: 1400
 
Interface MTU: 1400
 
</pre>
 
</pre>
*Click on Save
+
* Click on Save
*Click on Finish
+
* Click on Finish
*Wait a second or two
+
* Wait a second or two
*Click on the Apply button
+
* Click on the Apply button
*Click on Push changes now
+
* Click on Push changes now
*From the root console:
+
* From the root console:
 
<pre>iptables -t mangle -A FORWARD -i tun-mms -p tcp -m tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
 
<pre>iptables -t mangle -A FORWARD -i tun-mms -p tcp -m tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
 
iptables-save > /etc/sysconfig/iptables
 
iptables-save > /etc/sysconfig/iptables
 
urpmi yate-ucn-icap
 
urpmi yate-ucn-icap
 
</pre>
 
</pre>
;Please configure your IP routing so the 10.0.150.0/24 addresses can have access to NowSMS without any NAT.
+
;Please configure your IP routing so the tun-mms addresses can have access to NowSMS without any NAT.
  
  
Line 62: Line 60:
  
 
The SMPP is not configured so you will need to do the following from the root console:
 
The SMPP is not configured so you will need to do the following from the root console:
*Create a file /etc/yate/smsc/ysmpp.conf
+
* Create a file /etc/yate/smsc/ysmpp.conf
*Edit the file and insert the following:
+
* Edit the file and insert the following:
 
<pre>[general]
 
<pre>[general]
 
server=smpp-server
 
server=smpp-server
Line 76: Line 74:
 
addr=NN.NN.NN.NN (replace with the desired local IP of YateUCN)
 
addr=NN.NN.NN.NN (replace with the desired local IP of YateUCN)
 
port=2775
 
port=2775
 +
</pre>
 
Create a file /etc/yate/smsc/regfile.conf
 
Create a file /etc/yate/smsc/regfile.conf
 
Edit the file and insert the following:
 
Edit the file and insert the following:
[minicore]
+
<pre>[minicore]
password=XXXXX (replace with the password for CompanyX)</pre>
+
password=XXXXX (replace with the password for NowSMS)
 
+
</pre>
  
 
===CompanyX===
 
===CompanyX===
Please give the information below to the CompanyX support team to guide you through the required steps.
+
Please give the information below to the NowSMS support team to guide you through the required steps.
<pre>
+
 
 
Configure a SMPP connection to:
 
Configure a SMPP connection to:
IP address: NN.NN.NN.NN (see above)
+
<pre>IP address: NN.NN.NN.NN (see above)
 
TCP port: 2775
 
TCP port: 2775
 
System ID: yatecore
 
System ID: yatecore
Line 92: Line 91:
 
</pre>
 
</pre>
  
This connection is required so CompanyX can send SMS notifications about incoming MMS.
+
;This connection is required so NowSMS can send SMS notifications about incoming MMS.
  
You may test it with regular SMS from the CompanyX interface or if you chose NowSMS as MMS provider try [https://www.nowsms.com/doc/web-menu-interface/send-mms-notification send MMS notification]
+
You may test it with regular SMS or try [https://www.nowsms.com/doc/web-menu-interface/send-mms-notification send MMS notification]
  
;Configure ICAP header enrichment:
+
Configure ICAP header enrichment:
 
<pre>IP address: NN.NN.NN.NN (see above)
 
<pre>IP address: NN.NN.NN.NN (see above)
 
TCP port: 1344</pre>
 
TCP port: 1344</pre>

Revision as of 23:47, 1 November 2018

If you need the ability for all connected handsets (smartphones and feature phones) to be able to send/receive MMS messages this is the page you are looking for.

We did interoperate with the MMSC element of NowSMS for commercial networks that support regular MMS and attachments.

For Group Messaging please check their documentation.

The addition of MMS requires:

  • Setting up a separate "mms" AP through which handsets are allowed to reach the MMSC
  • Installing an add-on package yate-ucn-icap that provides subscriber identification and header enrichment via ICAP.
  • Setting up the MMSC (NowSMS) itself, you should get support from them
  • Setting up a SMPP connection from NowSMS to the YateSMSC component for new message notifications


YateUCN (GGSN/PGW)

The purpose is to allow the devices to use the MM1 protocol to MMSC and to allow the MMSC to map the IP address to a subscriber MSISDN.

There is no MMS Access Point configured so you need to add one using the MMI web interface:

  • Click on the My Network tab
  • Click on the APNs tab
  • Click on the Add link
  • Click on Advanced
  • Fill in the following fields:
Name: mms
IPv: IPv4
QoS: true
Primary DNS IPv4: 8.8.8.8 (isn't actually used)
MTU IPv4: 1400
Address: 10.0.4.3 (or copy it from another APN if you changed MiniCore configuration
  • Click on Save
  • Click on Finish
  • Click on the Equipment tab
  • Click Control node on YateUCN
  • Click Edit
  • Click GGSN/PGW
  • Click the Add link in Tunnels
  • Click on Advanced
  • Fill in the following fields:
Tunnel: tun-mms
IPv4 Pool: 10.0.150.2-10.0.150.254
Associate to Access Point(APN): mms
IPv4 Interface: 10.0.150.1/24
Interface MTU: 1400
  • Click on Save
  • Click on Finish
  • Wait a second or two
  • Click on the Apply button
  • Click on Push changes now
  • From the root console:
iptables -t mangle -A FORWARD -i tun-mms -p tcp -m tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
iptables-save > /etc/sysconfig/iptables
urpmi yate-ucn-icap
Please configure your IP routing so the tun-mms addresses can have access to NowSMS without any NAT.


YateSMSC

The purpose is to allow the MMSC to send binary SMS for MMS arrival notification.

The SMPP is not configured so you will need to do the following from the root console:

  • Create a file /etc/yate/smsc/ysmpp.conf
  • Edit the file and insert the following:
[general]
server=smpp-server

[smpp-server]
enable=true
default-service-type=sms
transparent_parameters=sms_message_id

[listenerserver companyx]
enable=yes
addr=NN.NN.NN.NN (replace with the desired local IP of YateUCN)
port=2775

Create a file /etc/yate/smsc/regfile.conf Edit the file and insert the following:

[minicore]
password=XXXXX (replace with the password for NowSMS)

CompanyX

Please give the information below to the NowSMS support team to guide you through the required steps.

Configure a SMPP connection to:

IP address: NN.NN.NN.NN (see above)
TCP port: 2775
System ID: yatecore
Secret: XXXXX (see above)
This connection is required so NowSMS can send SMS notifications about incoming MMS.

You may test it with regular SMS or try send MMS notification

Configure ICAP header enrichment:

IP address: NN.NN.NN.NN (see above)
TCP port: 1344

The purpose is to get working the header enrichment, if you chose NowSMS: NowWap and HTTP header enrichment

The package requires the commercial yate-ucn package and can be installed as root with: urpmi.update YateCore && urpmi yate-ucn-icap

When used with MMS for authorization purposes a WAP gateway itself needs some protocol like ICAP so it can map an IP address to a subscriber identity (MSISDN).

Addressing between subscribers uses the phone number (MSISDN) but the phone doesn't even know it, only the IMSI.