Add_workflow_for_techpubs |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
JIRAIDAUTH | CHOR-1054 |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ce340b42, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ce340b42, userName='null'} |
---|
|
This Best Practice details the local transfer feature limitation when
or passes through an RTP stream
in Proxy Mode.for the following: Caption |
---|
|
Mode | SBC Edge | SBC SWe Lite |
---|
Proxy Relay | | | Proxy with local SRTP | | |
|
How the RTP stream is transferred in
...
Proxy Relay or Proxy with local SRTP Mode
Local Transfer Feature Limitation
When the Sonus
or completes a local transfer, the transferee party receives the stream with different RTP header parameter(s) (such as SSRC, timestamp, etc.). This is because the original end point (transferor) is replaced by a new endpoint due to the transfer. Since the RTP stream is passed through by the FPP, there is no re-packetization done for any of the RTP header parameters, and the stream is passed end-to-end transparently.
...
To handle the transfer in RTP Proxy mode reliably, the SBC rejects the REFER and raises an event in local register mode.
Refer Pass-through Work Around
REFER pass-through should be enabled by configuring the SBC (see Creating and Modifying SIP Signaling Groups), which forces the transferee to handle the REFER directly.