--
You received this message because you are subscribed to the Google Groups "mobicents-public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mobicents-publ...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Jason,
Let me give the tomcat version a try on windows and I'll get back to you.
Thanks for your patience.
Regards
Charles
Telestax_Doc_Team
On Fri, Feb 1, 2013 at 12:51 PM, jason <jason...@blueboxproject.com> wrote:
I tried the Tomcat version instead which was at the same location.
https://mobicents.ci.cloudbees.com/job/RestComm/lastSuccessfulBuild/artifact/restcomm-saas-tomcat-1.0.0.BETA2-SNAPSHOT.zip
It would not start up correctly. I got the following error.
---
Jain Mgcp stack bound to IP /127.0.0.1 and UDP port 2727
Feb 1, 2013 12:04:47 PM org.apache.catalina.core.ApplicationContext log
SEVERE: StandardWrapper.Throwable org.apache.ibatis.exceptions.PersistenceException:
### Error building SqlSession.
### The error may exist in file://C:\apps\apache-tomcat-6-restcomm-1.0.0b2\webapps\restcomm\/WEB-INF/sql/accounts.xml
### Cause: org.apache.ibatis.builder.BuilderException: Error parsing SQL Mapper Configuration. Cause: java.net.UnknownHostException: C
---
I have nothing running on port 2727. Despite this, I tried the curl command anyway and got this.
---
C:\apps\curl>curl -data "PhoneNumber=1234&VoiceUrl=http://127.0.0.1:8080/restcomm/demo/hello-world.xml&VoiceMethod=POST" http://ACae6e420f425248d6a26948c17a9e2acf:77f8c12cc7b8f8423e5c38b03524916...@127.0.0.1:8080/restcomm/2012-04-24/Accounts/ACae6e420f425248d6a26948c17a9e2acf/IncomingPhoneNumbers.json
Hi Thomas,
I downloaded the latest nightly build (Jboss btw, not the tomcat version you suggested because I look forward to use some jboss capabilities). The previous error was fixed and this time I managed to send the curl command correctly, obtaining the expected output on the terminal (In this step I had to deploy the jboss server in my local IP instead of the loopback to be able to send the curl command from my linux virtual machine because I couldn´t manage to send the command from windows. I don´t know if cURL for windows works correctly.)
Until now everything was fine, however, after I did the curl command I saw the following message in the server output log:
0:58:38,123 INFO [AuthorizingRealm] No cache or cacheManager properties have been set. Authorization cache cannot be obtained.
That seems to be indicating that the command didn´t work, but I tried to make the call anyway. The call was successfully received by the server and appropriately delivered to Rescomm, but I didn´t hear any response. I thought that maybe I should change the register address of the linephone account to my local IP instead of the default loopback (since, the server is not on the loopback anymore). I repeated the call and this time I got an error on the server output.
I will attach both logs so that you can inspect them. Both of them start just after I send the curl command.
Kind Regards,
Sebastian
Hi Thomas,
I downloaded the latest nightly build (Jboss btw, not the tomcat version you suggested because I look forward to use some jboss capabilities). The previous error was fixed and this time I managed to send the curl command correctly, obtaining the expected output on the terminal (In this step I had to deploy the jboss server in my local IP instead of the loopback to be able to send the curl command from my linux virtual machine because I couldn´t manage to send the command from windows. I don´t know if cURL for windows works correctly.)
Until now everything was fine, however, after I did the curl command I saw the following message in the server output log:
0:58:38,123 INFO [AuthorizingRealm] No cache or cacheManager properties have been set. Authorization cache cannot be obtained.
That seems to be indicating that the command didn´t work, but I tried to make the call anyway. The call was successfully received by the server and appropriately delivered to Rescomm, but I didn´t hear any response. I thought that maybe I should change the register address of the linephone account to my local IP instead of the default loopback (since, the server is not on the loopback anymore). I repeated the call and this time I got an error on the server output.