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

Add SIP RPC #514

Merged
merged 1 commit into from
Nov 14, 2023
Merged

Add SIP RPC #514

merged 1 commit into from
Nov 14, 2023

Conversation

Sean-Der
Copy link
Contributor

@Sean-Der Sean-Der commented Nov 8, 2023

No description provided.

livekit_sip.proto Outdated Show resolved Hide resolved
livekit_sip.proto Outdated Show resolved Hide resolved
rpc/io.proto Show resolved Hide resolved
rpc/io.proto Show resolved Hide resolved
// Username and password used to authenticate inbound and outbound SIP invites
// May be empty to have no Authentication
string username = 5;
string password = 6;
Copy link
Contributor

Choose a reason for hiding this comment

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

Not exactly a protocol issue, but are there requirements about encrypting user credentials we need to store?

Copy link
Member

@davidzhao davidzhao left a comment

Choose a reason for hiding this comment

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

lg!

// Username and password used to authenticate inbound and outbound SIP invites
// May be empty to have no Authentication
string username = 6;
string password = 7;
Copy link
Member

Choose a reason for hiding this comment

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

we should mask or return blank username/password when listing/getting trunks.

import "options.proto";

service SIPInternal {
rpc UpdateSIPParticipant(InternalUpdateSIPParticipantRequest) returns (InternalUpdateSIPParticipantResponse) {
Copy link
Member

Choose a reason for hiding this comment

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

looks like this is just a placeholder? I think we'll want topic based routing to the node hosting the participant instead of affinity based selection

@Sean-Der Sean-Der merged commit e65cc3e into main Nov 14, 2023
3 checks passed
@Sean-Der Sean-Der deleted the sip branch November 14, 2023 01:25
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.

4 participants