osmocom
/
libosmo-sccp
mirror of https://gerrit.osmocom.org/libosmo-sccp
11
0
Fork 0
Code Issues Releases Wiki Activity

HACK: Add hard-coded DPC to SSA in response to SST 

At least some version of an Ericsson MSC is sending us a SST with
point codes only in the M3UA header, but not in the SCCP Called/Calling
address (which only contain SSN).  So if we create a SSA in respone, it
will only have SSN in it, and hence it cannot be routed.

We hard-code the destination point code (7000) here just for testing.

A proper solution would have to either
a) set up some SCCP routing that routes the SSN to a given point code
b) add the M3UA point codes from the MTP/M3UA layer to the SCCP
   Calling/CalledParty when receiving the message at the M3UA->SCCP boundary
This commit is contained in:
Harald Welte 2021-05-09 19:31:15 +00:00
parent bbe87f584c
commit 5489ccc37d
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
src/sccp_scmg.c
View File

@ -243,7 +243,11 @@ static int scmg_rx_sst(struct osmo_sccp_user *scu, const struct osmo_sccp_addr *
if (0 /* !subsys_available(scu) */)
return 0;
return sccp_scmg_tx(scu, called_addr, calling_addr, SCCP_SCMG_MSGT_SSA,
struct osmo_sccp_addr peer_addr = *calling_addr;
peer_addr.pc = 7000;
peer_addr.presence |= OSMO_SCCP_ADDR_T_PC;
return sccp_scmg_tx(scu, called_addr, &peer_addr, SCCP_SCMG_MSGT_SSA,
sst->affected_ssn, sst->affected_pc, 0, NULL);
}