Age | Commit message (Collapse) | Author | Files | Lines |
|
The MNCC application must provide the lchan_type with the lchan_mode,
since FR and HR codec depends on given lchan_type. In case of AMR, the
lchan_type is ignored and an available channel type is selected. In case
of EFR, the given lchan_type (must be full rate) is used.
|
|
When the MNCC application negotiates the codec, it must be sure that the
TCH rates of the neotiation results can be assigned to the MS. Therefore
not only the codecs that are unsupported by BTS are removed, but also the
codecs that require channels that are not available.
|
|
Handover might require change in codec, especially when switching between
AFS (AMR on TCH/F) and AHS (AMR on TCH/H). In this case the handover
decision must know if a different target rate is supported by the MS or
not.
|
|
A CM service request must be acknowledged also, when encryption is already
enabled.
Without encryption enabled, the security status is GSM_SECURITY_NOTAVAIL,
which causes a CM service acknowledge. On initial CM service request, the
security status is GSM_SECURITY_SUCCEED, if encryption is enabled. This
will not lead to an acknowledge, because the cyphering command implies an
acknowlege. An additional CM service request requires an acknowledge, so
I added a new security status: GSM_SECURITY_ALREADY
|
|
|
|
Since codec negotiation is done automatically, there is no need to define
codec for TCH/F and TCH/H via VTY anymore.
|
|
|
|
Traffic cannot sent to BTS, if there is (currently) no logical channel
associated with the transaction.
|
|
Speech codings which are not supported by BTS will be removed from the
bearer capability information element after parsing. This way it is not
required for the MNCC application to consider support of each BTS.
Only GSM full rate is supported by default.
|
|
The codes is not yet tested.
AMR rate is currently fixed to 5.9k.
|
|
Since EFR/AMR/HR codecs use dynamic RTP payload, the payload type can
be set. If it is set, the frame type must be set also, so OpenBSC
knows what frame types are received via RTP.
This modification only affects traffic beween application and MNCC
interface, not the RTP traffic between OpenBSC and BTS.
|
|
Instead of forwarding traffic through MNCC interface, traffic can
now be forwarded to a given RTP destination. A special MNCC message
is used for that. The traffic can still be forwarded through MNCC
interface when this special MNCC message is not used.
It also works with E1 based BTSs.
In conjunction with LCR's "rtp-bridge" feature, the RTP traffic
can be directly exchanged with a remote SIP endpoint, so that the
traffic is not forwarded by LCR itself. This way the performance
of handling traffic only depends on OpenBSC and the remote SIP
endpoint. Also the traffic is exchanged with the SIP endpoint
without transcoding, to have maximum performance.
|
|
Change-Id: I8f6dd67b53c1ecff88e17baa4f7417a68466990f
|