Moving to the smpp-config node and getting SMPP messages working
Recently I've been looking to try to get the SMPP functionality of the Osmocom network working. According to this page about port numbers
the port to send packets to for SMMP is 2775. However, when I tried to do this, the connection was refused. I assumed I had to enable it in the VTY, but when I went into the MSC's VTY, the smpp-config node was not present like the manual states:
https://ftp.osmocom.org/docs/latest/osmomsc-vty-reference.pdf (page 128)
I also want to view/change the SMSC's address because this is needed to create a packet with the correct application header, as far as I know. To do that, I also need to be able to access the smpp-config node (see picture).
Is the manual outdated with the smpp-config node being removed, or am I missing something? I'm going to keep reading up on the manuals but I figured I'd ask here to see if the manual is indeed outdated or if there's another way to access smpp-config.
Thanks for reading.
#2 Updated by laforge over 1 year ago
Which package / version / build are you using? AFAIK all the binary builds we
publish have SMPP enabled. If you build from source, make sure you use
during the build process. This (of course) requires libsmpp34 present in your
#4 Updated by laforge over 1 year ago
On Fri, Jul 19, 2019 at 06:37:29PM +0000, Osmocorn [REDMINE] wrote:
command is the correct one for changing the smsc's address aka operator's phone number?
there is no 'operators phone number'in SMPP. The system-id configures the system ID as
per the SMPP v3.4 specification. It doesn't have any other name.
#5 Updated by fixeria over 1 year ago
[...] command is the correct one for changing the smsc's address aka operator's phone number?
If you meant SMSC's address for the MT messages, it's currently hard-coded to '447785016005' in OsmoMSC:
MO messages also do contain SMSC's address, but it's simply ignored in case of SMPP AFAIR.