Restcomm-Connect icon indicating copy to clipboard operation
Restcomm-Connect copied to clipboard

It's difficult to do local call testing from devices on the same LAN, but outside RC host

Open atsakiridis opened this issue 8 years ago • 12 comments

Say you want to call a local RC instance number (ie 1235) from an android client using Android SDK connected to the same LAN with RC. When setting up the SDK you cannot use ip address because RC mandates the use of an organization. So to workaround that you need to somehow setup a DNS server for the LAN (if client was on the localhost things would be simple as we are easily covered by tweaking /etc/hosts), which adds complexity and also introduces test dependencies that can go wrong easily.

Since Organizations cannot be toggled on and off, could we think about exposing some sort of debug configuration that would potentially allow us to specify what would go inside the org table where we could use either IP or domain so that when client uses an IP it is accepted? Or any other, more informed solution ;)

atsakiridis avatar Jan 22 '18 15:01 atsakiridis

one of several related issues with Orgs: #2774

gsaslis avatar Jan 25 '18 10:01 gsaslis

we think this is already supported. you may create a new organization with ip address,or even modify the default org to have an ip address.... this allows to match teh dev env ip address as usual...

jaimecasero avatar Feb 23 '18 15:02 jaimecasero

@jaimecasero so you are saying that the organization domain name also allows IP addresses?

Docs (if i am looking at the right place) seems to suggest otherwise: https://www.restcomm.com/docs/connect/api/organization-api.html#create-new-organization

gsaslis avatar Feb 26 '18 14:02 gsaslis

@gsaslis this constraint is at rest API level. At db level you may use an IP address,and logic will work. Anyway, modifying DB internally its tricky, maybe we shoudl allow ip address in org domain name, so we can use REST API...

jaimecasero avatar Feb 26 '18 16:02 jaimecasero

@atsakiridis would you agree that the solution proposed by @jaimecasero would solve your issue?

If so, then maybe we can rename the issue and keep it open for contributions?

gsaslis avatar Feb 26 '18 17:02 gsaslis

this suggestion was commented by VVS team during product backlog refinement, other members may have more hints on this...

jaimecasero avatar Feb 26 '18 18:02 jaimecasero

@gsaslis if what @jaimecasero suggests is to update DB, then it's difficult for non core members, like me or Oggie. In the end VVS will waste time explaining us how to properly do it. Setting up RC is difficult as it is, and adding Docker on top, makes it even more difficult to access DB. Could we add a debug option to allow us for this functionality, if you don't want to expose it via REST API.

atsakiridis avatar Feb 27 '18 13:02 atsakiridis

@atsakiridis i was referring to:

maybe we shoudl allow ip address in org domain name, so we can use REST API...

I agree db access is not really an option, as @jaimecasero also suggested.

gsaslis avatar Feb 27 '18 14:02 gsaslis

i let @gvagenas provide further comments on the options here..

jaimecasero avatar Feb 28 '18 14:02 jaimecasero

@gsaslis @jaimecasero, if that could happen via REST then it 'd be great!

atsakiridis avatar Feb 28 '18 15:02 atsakiridis

@atsakiridis great! in that case, do you think we can rename the issue to sth like "Extend REST API to allow IP address in DomainName" ?

it sounds to me like this could even be a good first issue for someone to contribute? @RestComm/vvs-squad thoughts?

gsaslis avatar Mar 06 '18 16:03 gsaslis

Sure @gsaslis as soon as we get consensus from the @RestComm/vvs-squad will do

atsakiridis avatar Mar 06 '18 16:03 atsakiridis