Make SIP Number and SIP Client tied to an account and Unique per Organization

[maria-farooq]

Use Cases:

• Add new sip number should be possible even if that number exists in a different organization
• Add new sip client should be possible even if that number exists in a different organization
• Dialling a sip number means dialling that number of your(dialling client's) organization.
• Dialling a sip client means dialling that number of your(dialling client's) organization.
• upon sub account creation, tie the sub account to the same org as the parent.
• Register clients with same login under their respective organizations.
• monitoringservice metrics for registered users should distinctly identify users of all organizations #2128
• verify existing test suit
• update db changes in test suit
• add new test in test suit
• add upgrade scripts ( for numbers and client table changes)

@scottbarstow @deruelle do we want to support inter calls between client-to-number and client-to-client of different organizations?
For Example:
maria@org1.restcomm.com dials scott@org2.restcomm.com
or
maria@org1.restcomm.com dials 1234@org2.restcomm.com
do you think that it is part of scope of this ticket or we should create a different issue for that?

[deruelle]

@maria-farooq looks good to me.

maria@org1.restcomm.com dials scott@org2.restcomm.com and maria@org1.restcomm.com dials 1234@org2.restcomm.com only via Dial SIP not via dial client or dial number or dial conference, all of those should stay within an organization

[scottbarstow]

@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.