2014-12-18 3 views
1

컨버전스 된 (웹 및 SIP) 애플리케이션을 개발했습니다. 나는 mss-3.0.564-apache-tomcat-7.0.50을 사용하고 있습니다.Sip Servlet 애플리케이션이 시작되지 않았습니다.

sip.xml :

<?xml version="1.0" encoding="UTF-8"?> 

<sip-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
     xmlns="http://www.jcp.org/xml/ns/sipservlet" 
     xsi:schemaLocation="http://www.jcp.org/xml/ns/sipservlet http://www.jcp.org/xml/ns/sipservlet/sip-app_1_1.xsd"> 
    <app-name>com.mydomain.myapp</app-name> 

    <servlet-selection> 
     <main-servlet>MySipServlet</main-servlet> 
    </servlet-selection> 

    <servlet> 
     <servlet-name>MySipServlet</servlet-name> 
     <servlet-class>com.mydomain.myapp.sip.MySipServlet</servlet-class> 
     <load-on-startup>1</load-on-startup> 
    </servlet>  
</sip-app> 

mobicents-dar.properties는 :

ALL: ("com.mydomain.myapp", "DAR:From", "ORIGINATING", "", "NO_ROUTE", "0") 

웹 응용 프로그램이 제대로 시작했지만, SIP 부분은 그렇게하지 않는 것 - MySipServlet.init 메소드가 실행되지 않습니다. 어떤 SIP 요청에

나는 다음과 같은 오류를 얻을

org.mobicents.servlet.sip.core.DispatcherException: the Request-URI does not point to another domain, and there is no Route header,the container should not send the request as it will cause a loop. Instead, the container must reject the request with 404 Not Found final response with no Retry-After header. You may want to check your dar configuration file to see if the request can be handled or make sure you use the correct Application Router jar. 
at org.mobicents.servlet.sip.core.dispatchers.InitialRequestDispatcher.dispatchOutsideContainer(InitialRequestDispatcher.java:488) 

콘솔 로그는 이클립스에서 서버를 실행하는거야

2014-12-18 11:09:03,758 DEBUG [SipApplicationDispatcherImpl] (SIP-TCP-Core-PipelineThreadpool-0) Routing State INITIAL 
2014-12-18 11:09:03,759 DEBUG [InitialRequestDispatcher] (SIP-TCP-Core-PipelineThreadpool-0) Routing of Initial Request REGISTER sip:localhost SIP/2.0 
2014-12-18 11:09:03,759 DEBUG [InitialRequestDispatcher] (SIP-TCP-Core-PipelineThreadpool-0) popped route : null 
2014-12-18 11:09:03,760 DEBUG [DefaultApplicationRouter] (SIP-TCP-Core-PipelineThreadpool-0) [email protected]24 checking for next application for request REGISTER sip:localhost SIP/2.0 
... 
, region=null , directive=NEW, targetedRequestInfo=null, stateinfo=null with following dar {ALL=("com.mydomain.myapp", "DAR:From", "ORIGINATING", "", "NO_ROUTE", "0")} 
2014-12-18 11:09:03,760 DEBUG [DefaultApplicationRouter] (SIP-TCP-Core-PipelineThreadpool-0) Route Modifier : NO_ROUTE 
2014-12-18 11:09:03,760 DEBUG [DefaultApplicationRouter] (SIP-TCP-Core-PipelineThreadpool-0) Previous App Name : com.mydomain.myapp 
2014-12-18 11:09:03,760 DEBUG [DefaultApplicationRouter] (SIP-TCP-Core-PipelineThreadpool-0) Previous App Route Region : ORIGINATING 
2014-12-18 11:09:03,760 DEBUG [DefaultApplicationRouter] (SIP-TCP-Core-PipelineThreadpool-0) Current App Name : com.mydomain.myapp 
2014-12-18 11:09:03,760 DEBUG [DefaultApplicationRouter] (SIP-TCP-Core-PipelineThreadpool-0) Current App Route Region : ORIGINATING 
2014-12-18 11:09:03,760 DEBUG [InitialRequestDispatcher] (SIP-TCP-Core-PipelineThreadpool-0) the AR returned the following sip route modifiernull 
2014-12-18 11:09:03,760 INFO [InitialRequestDispatcher] (SIP-TCP-Core-PipelineThreadpool-0) Dispatching the request event outside the container 

가 포함되어 있습니다. 콘솔에서 실행하면 모든 것이 정상입니다.

가능한 원인은 무엇입니까?

답변

3

server.xml<Context> 태그가 정의되어 있으면 통합 된 응용 프로그램의 SIP 부분이 시작되지 않는 것으로 보입니다. 간단히 제거하면 문제가 해결됩니다. 문제는 Eclipse에서 웹 애플리케이션을 배포 할 때마다 해당 태그가 다시 추가된다는 것입니다.

또한 bug report에 Mobicents를 입력했습니다.

관련 문제