RESTCOMM-1625: Handle Route Header for MultiProvider config#2766
RESTCOMM-1625: Handle Route Header for MultiProvider config#2766jaimecasero merged 1 commit intomasterfrom
Conversation
|
adding @leftyb as well. |
There was a problem hiding this comment.
this is just relocating the addHeaders logic to the B2BUAHelper to be used from anywhere as an util,right?
There was a problem hiding this comment.
Correct. We also added the specific Route handling to push the route
There was a problem hiding this comment.
i take this was duplicated from Call logic, exactly same code?
There was a problem hiding this comment.
The only difference being the two were referring to private sipFactory, which we added as a param in the relocated one
There was a problem hiding this comment.
B2BUAHelper.isB2BUASession(response) == (B2BUAHelper.getLinkedSession(response) != null)
There was a problem hiding this comment.
B2BUAHelper.isB2BUASession(response) basically checks for the existence of a session in the message.
Since the block previously did not need to access any session data, it did not retrieve the SipSession. Now we do need to one access session attribute EXTENSION_HEADERS so we do need the local SipSession
There was a problem hiding this comment.
i take this is actually the only change to fix the issue, is it not the same condition as before?
There was a problem hiding this comment.
Previously we never modified the headers for this B2BUA/challenge request case.
|
for me this PR is ok to be merged, we just need to confirm on testsuite results. would it make sense to add a testcase for the new feature, to check extensionHeaders are added appropiately? |
0c26aee to
c8b1d89
Compare
|
im ok merging this when test results are ready |
…or B2BUA Motivation: - Push routes defined in MultiProvider outbound-voice config. Modification: - Move the duplicated CallManager and Call addHeadersToMessage to B2BUAHelper - Add explicit handling for Route headers - Save outboundHeaders to incoming request SipSession and modify B2BUA invite - Fetch outboundHeaders during challenge response and modify linked B2BU invite - Fix proxyPassword Result: - WebRTC/B2BUA calls will be able to modify headers and add Route headers
c8b1d89 to
074079b
Compare
@gvagenas @deruelle George, VVS, please have a look
Motivation:
Modification:
Result: