-
Notifications
You must be signed in to change notification settings - Fork 75
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
Add SIP RPC #514
Conversation
bde1802
to
3286488
Compare
// Username and password used to authenticate inbound and outbound SIP invites | ||
// May be empty to have no Authentication | ||
string username = 5; | ||
string password = 6; |
There was a problem hiding this comment.
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?
There was a problem hiding this 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; |
There was a problem hiding this comment.
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) { |
There was a problem hiding this comment.
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
No description provided.