8 Commits (52247a46e5ea298b4a2e2ade3617145cc1c9e1c0)

Author	SHA1	Message	Date
herlesupreeth	0f06ec0d9c	Add feature to provide custom GTP-U (S1) address to be advertised inside S1AP messages ... This feature is useful in scenarios where eNB is behind a NAT and EPC on public cloud Since eNB's GTP-U can only bind to IP address visible in it's host (usually a private IP beind a NAT), it advertises the same to UE in S1AP message resulting in traffic from EPC to eNB (DL traffic) not able to reach eNB. This commit solves this issue by providing a means to advertise a different IP address than the one GTP-U UDP socket is bound to. This IP is usually advertised in InitialContextSetupResponse and E-RABSetupResponse. In order to make use of this feature, use the following parameter in enb.conf Example: gtp_advertise_addr = 213.61.141.82	4 years ago
Francisco	14d32db92f	implement Handover direct forwarding path availability configuration feature	4 years ago
Francisco	b8fa1d1b61	fix rrc mobility test	4 years ago
Francisco	66988ffd32	s1ap - simplified erab setup procedure. Handle correctly the failure to setup causes	4 years ago
Francisco	c5fc543516	s1ap - handling of ts1 reloc overall timer.	4 years ago
Francisco	c2a99a8112	handover - support for handover cancellation causes, check for E-RAB QoS requirements, cancellation of handover if E-RABs are not supported in the target eNB	4 years ago
Francisco	d2c404b166	handover - setup s1ap cause in case of handover failure at the target enb	4 years ago
Codebot	4523ee6087	rename srsLTE to srsRAN	4 years ago