-
Notifications
You must be signed in to change notification settings - Fork 215
Make SIP Number and SIP Client tied to an account and Unique per Organization #2106
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
Comments
@maria-farooq looks good to me.
|
@maria-farooq this looks right to me as well. Jean can speak better to the inter-org, but what I'm not sure about is if we'd want to treat inter-org calls in your example as off-net, but I think this is a billing decision not a technical one. @deruelle comment on Dial SIP sounds right, tho I'm not deep in the weeds on that yet. Either way I think we should treat that as separate ticket so that we can include test cases separately. |
…, updated getClientByLogin to include organization sid #2106
added organizationSid in registrations dao and xml mapper files #2106
test suit packages verification
|
Add New test for the feature:
|
* master: Minor patch for Restcomm testsuite failing tests Patch for CallManager to properly handle numbers that start with + This close #2158 Patch to fix Outbound call never reach the completed state when inbound call sends BYE This close #2157 Patch that fixes various Restcomm testsuite failing tests Conflicts resolved: restcomm/restcomm.telephony/src/main/java/org/restcomm/connect/telephony/CallManager.java #2106
Use Cases:
@scottbarstow @deruelle do we want to support inter calls between
client-to-number
andclient-to-client
of different organizations?For Example:
[email protected]
dials[email protected]
or
[email protected]
dials[email protected]
do you think that it is part of scope of this ticket or we should create a different issue for that?
The text was updated successfully, but these errors were encountered: