| Harald Welte | 794d9b2 | 2009-02-17 02:02:14 +0000 | [diff] [blame] | 1 | Call routing in OpenBSC |
| 2 | |
| 3 | Flow of events: |
| 4 | |
| 5 | # MO call initiated by MS, CHANNEL RQD, IMMEDIATE ASSIGN |
| 6 | # MS sends CC SETUP message, we assume already on TCH/H FACCH |
| 7 | # OpenBSC does a subscriber lookup based on the target extension |
| 8 | * If a subscriber is found: |
| 9 | # send CALL PROCEEDING message to MO |
| 10 | # page the MT subscriber and ask itI to ask for TCH/H |
| 11 | # once paging completes, we have the TCH/H for the MT end |
| 12 | # send SETUP to MT |
| 13 | # receive CALL CONFIRMED from MT |
| 14 | # set-up the TRAU mux mapping between the E1 subslots for both TCH/H |
| 15 | # receive ALERTING from MT, route ALERTING to MO |
| 16 | # receive CONNECT from MT, confirm to MT with CONNECT_ACK |
| 17 | # send a CONNECT message to MO, receive CONNECT_ACK from MO |
| 18 | * If subscriber is not found: |
| 19 | # send RELEASE COMPLETE with apropriate cause to MO (1: unalloacated 3: no route) |
| 20 | |
| 21 | |
| 22 | |
| 23 | Thoughts about RR/MM: |
| 24 | |
| 25 | * we allocate RR/MM entities on demand, when we need them |