MMSC Configuration

From YateBTS
Revision as of 16:47, 1 November 2018 by Paulb (Talk | contribs)

Jump to: navigation, search
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 for a commercial network that does support regular MMS and attachments.

Not sure about Group Messaging, maybe their documentation would help.

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 (CompanyX) itself, you should get support from them
  • Setting up a SMPP connection from CompanyX to YateSMSC component for new message notifications
We can provide samples of the relevant configuration for the CORE Network components.


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: (isn't actually used)
MTU IPv4: 1400
Address: (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:
Associate to Access Point(APN): mms
IPv4 Interface:
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 addresses can have access to NowSMS without any NAT.


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:


[listenerserver companyx]
addr=NN.NN.NN.NN (replace with the desired local IP of YateUCN)
Create a file /etc/yate/smsc/regfile.conf
Edit the file and insert the following:
password=XXXXX (replace with the password for CompanyX)


Please give the information below to the CompanyX 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 CompanyX 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 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.