comparison doc/Proto-SMSC-testing @ 19:9ff041d85da5

proto-smsc-daemon: allow HLR GSUP server other than 127.0.0.1
author Mychaela Falconia <falcon@freecalypso.org>
date Sat, 16 Dec 2023 22:23:23 +0000
parents 9c2c1444dca9
children
comparison
equal deleted inserted replaced
18:9c2c1444dca9 19:9ff041d85da5
57 explicitly set ipa-name for the MSC becomes a requirement, just like with 57 explicitly set ipa-name for the MSC becomes a requirement, just like with
58 inter-MSC handover. 58 inter-MSC handover.
59 59
60 3) Run proto-smsc-daemon like this: 60 3) Run proto-smsc-daemon like this:
61 61
62 proto-smsc-daemon Example-SMSC mo-sms-log /tmp/sendmt_socket 62 proto-smsc-daemon 127.0.0.1 Example-SMSC mo-sms-log /tmp/sendmt_socket
63 63
64 The first argument is the IPA name this proto-SMSC should give itself (needs to 64 The first argument is the IP address of your OsmoHLR instance (more precisely,
65 match OsmoHLR config), the second argument is the name of a log file that will 65 the IP address at which OsmoHLR GSUP server can be reached; standard GSUP port
66 be opened for writing, and the third argument is the pathname to which a local 66 is required), the second argument is the IPA name this proto-SMSC should give
67 UNIX domain socket will be bound. 67 itself (needs to match OsmoHLR config), the third argument is the name of a log
68 file that will be opened for writing, and the fourth argument is the pathname
69 to which a local UNIX domain socket will be bound.
68 70
69 Any time an MS sends MO SMS to this proto-SMSC, the message will be written 71 Any time an MS sends MO SMS to this proto-SMSC, the message will be written
70 into the line-oriented log file which you named as the second argument to 72 into the line-oriented log file which you named as the second argument to
71 proto-smsc-daemon. Here is what messages will look like: 73 proto-smsc-daemon. Here is what messages will look like:
72 74