Skip to content

RESTCOMM-1625: Handle Route Header for MultiProvider config#2766

Merged
jaimecasero merged 1 commit intomasterfrom
MSB-352
Feb 19, 2018
Merged

RESTCOMM-1625: Handle Route Header for MultiProvider config#2766
jaimecasero merged 1 commit intomasterfrom
MSB-352

Conversation

@abdulazizali77
Copy link
Copy Markdown
Contributor

@gvagenas @deruelle George, VVS, please have a look

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

@deruelle
Copy link
Copy Markdown
Member

adding @leftyb as well.

@abdulazizali77 abdulazizali77 changed the title MSB-352 Handle Route Header for MultiProvider config RESTCOMM-1625: Handle Route Header for MultiProvider config Jan 25, 2018
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is just relocating the addHeaders logic to the B2BUAHelper to be used from anywhere as an util,right?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Correct. We also added the specific Route handling to push the route

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i take this was duplicated from Call logic, exactly same code?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The only difference being the two were referring to private sipFactory, which we added as a param in the relocated one

Copy link
Copy Markdown
Contributor

@jaimecasero jaimecasero Feb 2, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

B2BUAHelper.isB2BUASession(response) == (B2BUAHelper.getLinkedSession(response) != null)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i take this is actually the only change to fix the issue, is it not the same condition as before?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Previously we never modified the headers for this B2BUA/challenge request case.

@jaimecasero
Copy link
Copy Markdown
Contributor

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?

@abdulazizali77
Copy link
Copy Markdown
Contributor Author

@jaimecasero
Copy link
Copy Markdown
Contributor

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants