Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: Feature server REFER #90

Merged
merged 3 commits into from
Aug 20, 2023
Merged

Conversation

two56
Copy link
Contributor

@two56 two56 commented Jun 2, 2023

This addresses #89

This is mostly correcting (I think) the old code. Adding the destruction of the old dialog of the REFERing feature server and returning a 488 if things go wrong.

I've tested the best I can, I'm getting audio!

I hope re-using the to-tag and from-tag is the right thing to do when setting up the dialog/audio to the target feature server?


const uac = await this.srf.createUAC(referTo.uri, {localSdp: dlg.local.sdp, headers});
this.uas = uac;
uac.type = 'uas';
Copy link
Collaborator

Choose a reason for hiding this comment

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

interesting, 'createUAC' does not do this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Are you referring to setting type?

We start with this scenario:

FS1 -> UAS (SBC) UAC -> End point

When the refer takes place we end up with:

FS2 <- UAC (SBC) UAC -> End point

Quite a few tests in the call-session check (uac|uas).type to handle things like INFO frames correctly, in my case startCallRecording. As the leg to FS2 is now a UAC we need to "correct" it so things are handled in the right way.

Hopefully that shouldn't cause a problem?

@davehorton davehorton merged commit 7f2bce9 into jambonz:main Aug 20, 2023
1 check passed
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.

2 participants