New doc: How to build Restcomm from source on github

[Ivelin Ivanov]

http://docs.telestax.com/restcomm-mobicents-building-from-source/

[inf...@gmail.com]

Nice tutorial! Worked well for me.

Regards,

Guilherme.

Em segunda-feira, 6 de outubro de 2014 17h44min38s UTC-3, ivelin escreveu:

http://docs.telestax.com/restcomm-mobicents-building-from-source/

[Ivelin Ivanov]

Great. Are you able to run the testsuite without errors?

--
You received this message because you are subscribed to the Google Groups "restcomm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to restcomm+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Scott Barstow]

Small error in doc in that the current version does not have standalone-sip.xml and it's not required.  You can just run standalone.sh to launch the app.

Otherwise this worked perfectly.

On Monday, October 6, 2014 4:44:38 PM UTC-4, ivelin wrote:

http://docs.telestax.com/restcomm-mobicents-building-from-source/

[Arslan Mehboob]

On Tuesday, 7 October 2014 01:44:38 UTC+5, ivelin wrote:
> http://docs.telestax.com/restcomm-mobicents-building-from-source/

Hi Ivelin,

I got this error while building from scratch.

./restcomm-build.sh
https://mobicents.ci.cloudbees.com/job/Mobicents-SipServlet s-Release/558/artifact/mss-3.0.558-apache-tomcat-7.0.50.zip
[exec] Resolving mobicents.ci.cloudbees.com... 54.225.194.96, 54.221.205.199
[exec] Connecting to mobicents.ci.cloudbees.com|54.225.194.96|:443... connected.
[exec] HTTP request sent, awaiting response... 404 Not Found
[exec] 2014-10-16 15:54:21 ERROR 404: Not Found.


I have changed the ant script to point to tomcat at this location

<!-- <property name="mobicents-sipservlets.tomcat.download.url" value="https://mobicents.ci.cloudbees.com/job/Mobicents-SipServlets-Release/${sipservlets-build}/artifact/${mobicents-sipservlets.tomcat.download.distro.file}" /> -->

<property name="mobicents-sipservlets.tomcat.download.url" value="https://mobicents.ci.cloudbees.com/job/Mobicents-SipServlets-Release/lastSuccessfulBuild/artifact/mss-3.0.555-apache-tomcat-7.0.50.zip" />


and the script is downloading, will update the post if everything runs fine

[George Vagenas]

Hi Arslan,

We need to update the script for the updated versions of SipServlets, I will ping you when ready.

George

--
You received this message because you are subscribed to the Google Groups "restcomm" group.
To unsubscribe from this group and stop receiving emails from it, send an email to restcomm+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
George Vagenas

[inf...@gmail.com]

Hi Ivelin!

Sorry for my delay, I was busy at the university.

Even after the successful build, testsuite still running with errors, as described here: https://groups.google.com/forum/#!topic/restcomm/DKiBfZIAIqk

This week I will try to configure the environment again from a clean release of Eclipse Luna. Currently, im running it in JUnit by the Eclipse Kepler release. 

If there is other way to run the testsuite please let me know. I can try it.

Just to complement what Scott said about standalone-sip.xml, JBoss really start without errors but this compromises the administrative login at the restcomm-management. After JBoss init Jersey application, the login screen show the the "Login failed" message. So I believe the parameter "-c standalone-sip.xml" seems to be mandatory.

Also, to build the application using maven 3, the maven-compiler-plugin version need to be explicit declared at the super pom.

Cheers!