ASCI: Use a unique call-id for RTP streams
The MGCP protocol features the 'C' (call-id) to identify which
connections belong to the same call. They may be used by MGW for
accounting or management procedures.
So far we sent the MNCC callref as call-id. Instead, add a separate
unique call_id number space. Assign a unique call_id to each
transaction.
Change-Id: I36c5f159fa0b54fb576ff8bd279928b895554793
Related: OS#4854
diff --git a/include/osmocom/msc/msc_t.h b/include/osmocom/msc/msc_t.h
index 39b3abc..876c11d 100644
--- a/include/osmocom/msc/msc_t.h
+++ b/include/osmocom/msc/msc_t.h
@@ -30,7 +30,7 @@
struct {
struct an_apdu ho_request;
struct gsm0808_cell_id cell_id_target;
- uint32_t callref;
+ uint32_t call_id;
char handover_number[16]; /* No libosmocore definition for MSISDN_MAXLEN? */
struct call_leg *call_leg;
struct mncc_call *mncc_forwarding_to_remote_cn;