Quick SMSCB HOWTO » History » Version 1
laforge, 01/24/2021 10:15 PM
| 1 | 1 | laforge | h1. Quick SMSCB HOWTO |
|---|---|---|---|
| 2 | |||
| 3 | Assumptions: |
||
| 4 | * [[osmobsc:|osmo-bsc]], [[osmo-cbc:]] and @cbc-apitool.py@ installed on the same host |
||
| 5 | ** cbc-apitool.py is hidden in the @osmo-cbc-utils@ dpkg/rpm package. |
||
| 6 | |||
| 7 | In order to test SMSCB, you will need to: |
||
| 8 | |||
| 9 | # configure your BTS channels to include a CBCH (either on SDCCH/4 or on SDCCH/8) |
||
| 10 | <pre> |
||
| 11 | bts 0 |
||
| 12 | trx 0 |
||
| 13 | timeslot 0 |
||
| 14 | phys_chan_config CCCH+SDCCH4+CBCH |
||
| 15 | </pre> |
||
| 16 | # configure CBSP on the BSC, for example like this: |
||
| 17 | <pre> |
||
| 18 | cbc |
||
| 19 | mode client |
||
| 20 | client |
||
| 21 | remote-ip 127.0.0.1 |
||
| 22 | local-ip 127.0.0.1 |
||
| 23 | local-port 46133 |
||
| 24 | </pre> |
||
| 25 | # configure OsmoCBC from the @osmo-cbc@ RPM package, for example like this: |
||
| 26 | <pre> |
||
| 27 | cbc |
||
| 28 | unknown-peers reject |
||
| 29 | peer local-bsc |
||
| 30 | protocol cbsp |
||
| 31 | remote-port 46133 |
||
| 32 | remote-ip 127.0.0.1 |
||
| 33 | cbsp |
||
| 34 | local-ip 127.0.0.1 |
||
| 35 | local-port 48049 |
||
| 36 | ecbe |
||
| 37 | local-ip 127.0.0.1 |
||
| 38 | local-port 12345 |
||
| 39 | </pre> |
||
| 40 | # use @cbc-apitool.py@ from the @osmo-cbc-utils@ RPM package to add a new SMSCB to the system |
||
| 41 | <pre> |
||
| 42 | $ cbc-apitool.py create-cbs --msg-id 4370 --payload-data-utf8 "Bon giorno!" |
||
| 43 | </pre> |
||
| 44 | |||
| 45 | At that point you should see |
||
| 46 | * *CBSP WRITE-REPLACE* messages on tcp port 48049 between CBC and BSC over the loopback device |
||
| 47 | * *RSL SMS BROADCAST COMMAND* on Abis RSL (tcp port 3003) between BSC and BTS; periodically repeated |
||
| 48 | * *CBCH* downlink transmissions on Um towards the MS |
||
| 49 | |||
| 50 | If your phone doesn't disable them, with a msg-id of 4370 you should get a "Presidential Level Alert' for 4370. |
||
| 51 | |||
| 52 | For more message IDs, see TS 23.041 section 9.4.1.2.2 |
