cafesip-sipexchange Mailing List for CafeSip - Look what Java and SIP can do
A suite of open-source tools and frameworks for creating SIP apps
Brought to you by:
amitchatterjee,
beckymc
You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
(11) |
Apr
(6) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
|
Feb
|
Mar
(1) |
Apr
(7) |
May
(2) |
Jun
|
Jul
(1) |
Aug
(3) |
Sep
(4) |
Oct
|
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: mpumelelo a. <lel...@gm...> - 2011-07-19 16:27:27
|
Hi guys I get an error when installing SipExchange. "Buidfile: install.ant does not exist. Build failed." Please help. Kind Regards |
From: Amit C. <ami...@ca...> - 2009-03-22 22:52:23
|
SipExchange 1.0.0b released Introducing SipExchange Portal, web services and more Mar 20, 2009, Raleigh, NC. We are pleased to announce the release of SipExchange r1.0.0b. This is a Beta release to give users a working system to evaluate and test. Feedback from the development community is encouraged for further enhancing the system. In this release, we have introduced major features that will be beneficial to companies and service providers who wants to provide VoIP service to their employees or customers. Highlights of the release include: We have introduced a Web Portal which enables subscribers and administrators to access, manage and fine-tune all aspects of SipExchange. Subscribers can view their calling records, manage their profile & contact list and manage their features like call forwarding and call screening. Administrators can provision and monitor the system from the portal. Based on the Jboss Portal technology, it enables system administrators to completely customize the look and feel and add new applications to the portal. It enables users to customize the look and feel and manage application dashboards. An extensive set of web services have been introduced that enables external management and billing systems to manage user records, billing records and system configurations. This feature allows SipExchange to be integrated into existing infrastructure and enterprise services. In addition, since all the SipExchange user interface applications are portlets, elements of the user interface can be integrated into existing portals. An installer/upgrade tool has been introduced. The installer uses a command-line wizard tool to setup the basic configuration of the system. This reduces the number of steps an installer had to perform to setup SipExchange. The upgrade tool enables SipExchange to be upgraded without losing any data. Extensive set of automated unit tests have been added. In the next release, we want to extend this further and introduce benchmark tests. The call processing engine has been tested extensively and number of bugs found while testing has been fixed. What is SipExchange? SipExchange is an open-source softswitch that provides standard SIP services like location, proxy and presence. Using the SipExchange application, service providers can offer VoIP telephone services to their subscribers as well as other services based on voice, video and instant messaging. SipExchange supports many of the standard subscriber features offered by the traditional telephone exchanges and PBXs. In addition, SipExchange supports external call control capabilities using which service providers and software developers can create new features and services rapidly and plug them into the SipExchange application. SipExchange provides a portal-based user interface using which system administrators can manage subscribers and features as well as perform other routine operations. If you have any questions on SipExchange, please contact sip...@ca.... -- CafeSip Team |
From: 坤 倪 <nk7...@ya...> - 2008-03-18 00:10:58
|
Hi, I'm a student from China. I'm trying to develop a feature that give back to the calling subscriber with a early media when the called subscriber response 180 ringing.I have created a CalledRingTermTrigger(CRN),but I don't know what should I do next.I have no idea about how to send the song configured by the called Subscriber to the calling one.what should i do when the called Subscriber answer the call? waiting for advices,thanks Best regards Ryan Ni --------------------------------- 雅虎邮箱传递新年祝福,个性贺卡送亲朋! |
From: Amit C. <ami...@qu...> - 2007-09-17 11:24:08
|
Hi, I just tried the authentication and it worked fine. I tried logging in with a wrong password and the authentication failed. I would like to understand the reason why this is not working for you. Please provide some details if you can. Also, make sure that you are not running the jiplet reference application that comes with the jiplet project. Regards, Amit The trace message below: Unsuccessful login (wrong password): ------------------------------------------------------ REGISTER sip:cafesip.org SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:37320;received=192.168.2.1 ;branch=z9hG4bK-d87543-9a741745b21c1b5b-1--d87543-;rport=37320 Max-Forwards: 70 Contact: <sip:becky@127.0.0.1:37320;rinstance=d41d62b12871f6dd> To: "Becky McElroy" <sip:be...@ca...> From: "Becky McElroy" <sip:be...@ca...>;tag=4c107153 Call-ID: NWY0NjA1MGU0NmJmOWU4NjE3YmRkMGQ3NzU3MDgyMGI. CSeq: 140 REGISTER Expires: 3600 Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,MESSAGE,SUBSCRIBE,INFO User-Agent: X-Lite release 1011s stamp 41150 Authorization: Digest uri="sip:cafesip.org",realm="cafesip.org ",username="becky",opaque="A+ckExUBAAAOD4kG",nonce="lpEmExUBAAAOD4kG",algorithm=MD5,response="39bea59fe0b1e9bca326d083121569a6" Content-Length: 0 SIP/2.0 401 Please provide your credentials Via: SIP/2.0/UDP 127.0.0.1:37320;received=192.168.2.1 ;branch=z9hG4bK-d87543-9a741745b21c1b5b-1--d87543-;rport=37320 To: "Becky McElroy" <sip:be...@ca...> From: "Becky McElroy" <sip:be...@ca...>;tag=4c107153 Call-ID: NWY0NjA1MGU0NmJmOWU4NjE3YmRkMGQ3NzU3MDgyMGI. CSeq: 140 REGISTER WWW-Authenticate: Digest stale=true,domain="sip:cafesip.org",realm=" cafesip.org ",opaque="A+ckExUBAAAOD4kG",nonce="E5ImExUBAAAOD4kG",algorithm=MD5 Content-Length: 0 Successful Login (right password) ------------------------------------------------ REGISTER sip:cafesip.org SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:46418;received=192.168.2.1 ;branch=z9hG4bK-d87543-681a6f2e03612d6d-1--d87543-;rport=46418 Max-Forwards: 70 Contact: <sip:becky@127.0.0.1:46418;rinstance=47c4175b9a9fb652> To: "Becky McElroy" <sip:be...@ca...> From: "Becky McElroy" <sip:be...@ca...>;tag=0c09770b Call-ID: Y2Q0NTQ5ZjUzYTczMzBkYTQ1ZmMzYTI5ZDJlNTE3ZDc. CSeq: 2 REGISTER Expires: 3600 Allow: INVITE,ACK,CANCEL,OPTIONS,BYE,REFER,NOTIFY,MESSAGE,SUBSCRIBE,INFO User-Agent: X-Lite release 1011s stamp 41150 Authorization: Digest uri="sip:cafesip.org",realm="cafesip.org ",username="becky",opaque="A+ckExUBAAAOD4kG",nonce="S5MmExUBAAAOD4kG",algorithm=MD5,response="db3f856b576e93df390af963bf1b0208" Content-Length: 0 SIP/2.0 200 OK Via: SIP/2.0/UDP 127.0.0.1:46418;received=192.168.2.1 ;branch=z9hG4bK-d87543-681a6f2e03612d6d-1--d87543-;rport=46418 To: "Becky McElroy" <sip:be...@ca...> From: "Becky McElroy" <sip:be...@ca...>;tag=0c09770b Call-ID: Y2Q0NTQ5ZjUzYTczMzBkYTQ1ZmMzYTI5ZDJlNTE3ZDc. CSeq: 2 REGISTER Expires: 3600 Content-Length: 0 > > Message: 1 > Date: Mon, 10 Sep 2007 16:35:47 +0200 (CEST) > From: essafie ennaceure <es...@ya...> > Subject: [Cafesip-sipexchange] Authentication realy don't work in sip > exchange > To: caf...@li... > Message-ID: <917...@we...> > Content-Type: text/plain; charset="iso-8859-1" > > Hi,I would like to thank you very mutch for your aid for my last post it > worked fine , but i would like to pinpoint a bug : when sending a register > request Sipexchange respond with a 401 response than I send a register with > authentication header then I the user was reegistred ,things seems working > fine !! but the problem is that the user was also registred even when I > send a register with false information(Password) in the authentication > Header.It seems that sip exchange don't inquire the data base ??.. > > thank you in advance > > > --------------------------------- > Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! > Mail > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > > |
From: becky m. <bec...@gm...> - 2007-09-11 14:13:23
|
Hi, You'll see some bad event responses from the sipexchange server to the xlite phone because the xlite phone subscribes to other package/events besides presence, like 'winfo' (watcher info) which sipexchange doesn't support (same for the PUBLISH message). But, that doesn't hurt anything, and for the SUBSCRIBE request where the event package is for presence, sipexchange shouldn't be sending bad event but should send OK for that one. You can examine the traces closely and that is what you should be seeing. To turn on traces: Edit the file $JBOSS_HOME/server/$RUN/conf/jiplet/server.xml. Search for a segment that looks like: <jip-property key="gov.nist.javax.sip.TRACE_LEVEL" value="0"/> <jip-property key="gov.nist.javax.sip.DEBUG_LOG" value="proxyserver_log.txt"/> Modify it to look something like: <jip-property key="gov.nist.javax.sip.TRACE_LEVEL" value="16"/> <jip-property key="gov.nist.javax.sip.DEBUG_LOG" value="C:\proxyserver_log.txt"/> and restart JBOSS. At this point, all the SIP messages will be saved in the file C:\proxyserver_log.txt. If you see you're not getting an OK, followed by NOTIFY, for the SUBSCRIBE message with event = presence, please post the trace and I'll look at it. Thanks, Becky On 9/11/07, essafie ennaceure <es...@ya...> wrote: > > Hi , > When making test using Xlite for the presence services ,sip exchange > respond to the subscribe request with a bad event message .IT seems that sip > exchange don't handle presence service ?,I wonder Sir if this is true or I m > confusing things .If this is true, will this limitation of sipexchange will > be fixed in the next release and when the next release will be delivered .It > is urgent sir for my Master project ??? > > Thank you in advance > With Regards. > > ------------------------------ > Ne gardez plus qu'une seule adresse mail ! Copiez vos mails<http://www.trueswitch.com/yahoo-fr/>vers Yahoo! Mail > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Cafesip-sipexchange mailing list > Caf...@li... > https://lists.sourceforge.net/lists/listinfo/cafesip-sipexchange > > |
From: essafie e. <es...@ya...> - 2007-09-11 13:14:01
|
Hi , When making test using Xlite for the presence services ,sip exchange respond to the subscribe request with a bad event message .IT seems that sip exchange don't handle presence service ?,I wonder Sir if this is true or I m confusing things .If this is true, will this limitation of sipexchange will be fixed in the next release and when the next release will be delivered .It is urgent sir for my Master project ??? Thank you in advance With Regards. --------------------------------- Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail |
From: essafie e. <es...@ya...> - 2007-09-10 14:36:04
|
Hi,I would like to thank you very mutch for your aid for my last post it worked fine , but i would like to pinpoint a bug : when sending a register request Sipexchange respond with a 401 response than I send a register with authentication header then I the user was reegistred ,things seems working fine !! but the problem is that the user was also registred even when I send a register with false information(Password) in the authentication Header.It seems that sip exchange don't inquire the data base ??. thank you in advance --------------------------------- Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail |
From: Amit C. <ami...@qu...> - 2007-08-30 12:13:48
|
Hi, it looks like that the EJBs did not deploy and there was no error message. The most likely reason is that the Jboss you are using do not have EJB3 support. Check if you have the directory called - ejb3.deployer under $JBOSS_HOME/server/default/deploy directory. If not, you may have downloaded the Jboss with no EJB3 support. Keep us posted. Regards, Amit essafie ennaceure <es...@ya...> writes: > > when trying to deploy sipexchange version 0.0.4a on jboss 4.0.5GA i > acounter these exceptions : > 10:47:25,593 ERROR [[/sipex]] Servlet /sipex threw load() exception > javax.naming.NameNotFoundException: ejb not bound > at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) > at org.jnp.server.NamingServer.getBinding(NamingServer.java:537) > ......................... > ........................... > > > |
From: essafie e. <es...@ya...> - 2007-08-30 09:00:06
|
when trying to deploy sipexchange version 0.0.4a on jboss 4.0.5GA i acounter these exceptions : 10:47:25,593 ERROR [[/sipex]] Servlet /sipex threw load() exception javax.naming.NameNotFoundException: ejb not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) at org.jnp.server.NamingServer.getBinding(NamingServer.java:537) ......................... ........................... and 10:47:25,625 INFO [JipletService] Received a request to start deployment file:/C:/jboss-4.0.5.GA/server/default/tmp/deploy/tmp3 10:47:25,625 INFO [JipletService] Received a request from J2EE deployer to add a realm with path: /C:/jboss-4.0.5.GA/server/def 10:47:25,796 ERROR [JipletService] Error creating realm: org.cafesip.jiplet.JipletException: javax.naming.NameNotFoundException: org.cafesip.jiplet.JipletException: javax.naming.NameNotFoundException: ejb not bound at org.cafesip.sipexchange.realms.sip.SipExchangeRealm.init(SipExchangeRealm.java:136) ..................... ...................... ...................... and the third : 10:47:25,796 ERROR [JipletService] Error creating J2EE realm: Realm: 01sipex-realm could not be created. Message: javax.naming.Na 10:47:25,796 WARN [NestedThrowable] Duplicate throwable nesting of same base type: class org.jboss.deployment.DeploymentExceptio 10:47:25,796 ERROR [MainDeployer] Could not start deployment: file:/C:/jboss-4.0.5.GA/server/default/tmp/deploy/tmp37439sipexchan org.jboss.deployment.DeploymentException: Realm: 01sipex-realm could not be created. Message: javax.naming.NameNotFoundException: at org.cafesip.jiplet.jboss.SrrDeployer.start(SrrDeployer.java:111) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) ............................ ............................ ............................ I folowed the installatio istraction as given in Installation Howto and i 'm using jdk 1.6 . the jboss screen look like this : 10:47:06,046 INFO [Server] Starting JBoss (MX MicroKernel)... 10:47:06,062 INFO [Server] Release ID: JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) 10:47:06,062 INFO [Server] Home Dir: C:\jboss-4.0.5.GA 10:47:06,062 INFO [Server] Home URL: file:/C:/jboss-4.0.5.GA/ 10:47:06,062 INFO [Server] Patch URL: null 10:47:06,062 INFO [Server] Server Name: default 10:47:06,062 INFO [Server] Server Home Dir: C:\jboss-4.0.5.GA\server\default 10:47:06,062 INFO [Server] Server Home URL: file:/C:/jboss-4.0.5.GA/server/default/ 10:47:06,062 INFO [Server] Server Log Dir: C:\jboss-4.0.5.GA\server\default\log 10:47:06,062 INFO [Server] Server Temp Dir: C:\jboss-4.0.5.GA\server\default\tmp 10:47:06,062 INFO [Server] Root Deployment Filename: jboss-service.xml 10:47:06,421 INFO [ServerInfo] Java version: 1.6.0,Sun Microsystems Inc. 10:47:06,421 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.6.0-b105,Sun Microsystems Inc. 10:47:06,421 INFO [ServerInfo] OS-System: Windows 2003 5.2,x86 10:47:06,843 INFO [Server] Core system initialized 10:47:08,453 INFO [WebService] Using RMI server codebase: http://emw-eing0fvhr10:8083/ 10:47:08,468 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml 10:47:11,984 INFO [ServiceEndpointManager] WebServices: jbossws-1.0.3.SP1 (date=200609291417) 10:47:13,078 INFO [JipletService] Jiplet container started 10:47:13,328 INFO [JipletService] Initializing connector: sip-connector 10:47:13,328 INFO [JipletService] The property javax.sip.IP_ADDRESS has not been specified. Going to use 148.135.109.65 as the I 10:47:13,484 INFO [JipletService] Realm subscribers.cafesip.org started 10:47:13,484 INFO [JipletService] Registering MBEAN JipletContainer 10:47:14,296 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://148.135.109.65:6666/?clientMaxPool 10:47:14,312 INFO [SocketServerInvoker] Invoker started for locator: InvokerLocator [socket://148.135.109.65:6667/?clientMaxPool 10:47:15,031 INFO [Embedded] Catalina naming disabled 10:47:15,062 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set. 10:47:15,062 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in the classpath. Will load the default rule set. 10:47:15,296 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8080 10:47:15,734 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0-8443 10:47:15,734 INFO [Catalina] Initialization processed in 672 ms 10:47:15,734 INFO [StandardService] Starting service jboss.web 10:47:15,734 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.20 10:47:15,765 INFO [StandardHost] XML validation disabled 10:47:15,781 INFO [Catalina] Server startup in 47 ms 10:47:15,953 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/http-invoker.sar/invoker.war/ 10:47:16,250 INFO [WebappLoader] Dual registration of jndi stream handler: factory already defined 10:47:16,578 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbossweb-tomcat55.sar/ROOT.war/ 10:47:16,781 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/deploy/tmp37402jbossws-context-exp.war/ 10:47:16,937 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ 10:47:17,984 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../deploy/management/console-mgr.sar/web-console.war/ 10:47:18,546 INFO [MailService] Mail Service bound to java:/Mail 10:47:18,671 INFO [MailService] Mail Service bound to java:/SipExchangeMail 10:47:18,765 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-local-jdbc.rar 10:47:18,812 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-ha-xa-jdbc.rar 10:47:18,843 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-local-jdbc.rar 10:47:18,875 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jboss-xa-jdbc.rar 10:47:18,937 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/jms/jms-ra.rar 10:47:18,968 INFO [RARDeployment] Required license terms exist, view META-INF/ra.xml in .../deploy/mail-ra.rar 10:47:19,953 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=DefaultDS' to JND 10:47:20,203 INFO [A] Bound to JNDI name: queue/A 10:47:20,203 INFO [B] Bound to JNDI name: queue/B 10:47:20,203 INFO [C] Bound to JNDI name: queue/C 10:47:20,203 INFO [D] Bound to JNDI name: queue/D 10:47:20,203 INFO [ex] Bound to JNDI name: queue/ex 10:47:20,218 INFO [testTopic] Bound to JNDI name: topic/testTopic 10:47:20,218 INFO [securedTopic] Bound to JNDI name: topic/securedTopic 10:47:20,218 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic 10:47:20,218 INFO [testQueue] Bound to JNDI name: queue/testQueue 10:47:20,281 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.0.0:8093 10:47:20,312 INFO [DLQ] Bound to JNDI name: queue/DLQ 10:47:20,437 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jboss.jca:service=ConnectionFactoryBinding,name=Jms 10:47:20,531 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=sipexchangeDs' to 10:47:22,187 INFO [TomcatDeployer] deploy, ctxPath=/jiplet-console, warUrl=.../tmp/deploy/tmp37438jiplet-console-exp.war/ 10:47:22,500 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/ 10:47:22,687 INFO [EsrDeployer] Init J2EE application: file:/C:/jboss-4.0.5.GA/server/default/deploy/sipexchange.esr 10:47:23,953 INFO [JipletService] Received a request to init deployment file:/C:/jboss-4.0.5.GA/server/default/tmp/deploy/tmp37 10:47:24,046 INFO [JipletService] Received a request to create deployment file:/C:/jboss-4.0.5.GA/server/default/tmp/deploy/tmp 10:47:24,046 INFO [JipletService] Received a request to create deployment file:/C:/jboss-4.0.5.GA/server/default/tmp/deploy/tmp 10:47:24,062 INFO [TomcatDeployer] deploy, ctxPath=/sipex, warUrl=.../tmp/deploy/tmp37439sipexchange.esr-contents/sipex-exp.war/ 10:47:24,812 INFO [TilesPlugin] Tiles definition factory loaded for module ''. 10:47:24,812 INFO [ValidatorPlugIn] Loading validation rules file from '/WEB-INF/validator-rules.xml' 10:47:24,812 INFO [ValidatorPlugIn] Loading validation rules file from '/WEB-INF/validation.xml' 10:47:25,593 ERROR [[/sipex]] Servlet /sipex threw load() exception javax.naming.NameNotFoundException: ejb not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) at org.jnp.server.NamingServer.getBinding(NamingServer.java:537) at org.jnp.server.NamingServer.getObject(NamingServer.java:543) at org.jnp.server.NamingServer.lookup(NamingServer.java:267) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.cafesip.sipexchange.web.model.SysParams.<init>(SysParams.java:52) at org.cafesip.sipexchange.web.controller.SipexConsole.init(SipexConsole.java:75) at org.apache.struts.action.ActionServlet.initModulePlugIns(ActionServlet.java:839) at org.apache.struts.action.ActionServlet.init(ActionServlet.java:332) at javax.servlet.GenericServlet.init(GenericServlet.java:211) at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1105) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:932) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3951) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4225) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.apache.catalina.core.StandardContext.init(StandardContext.java:5052) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.modeler.BaseModelMBean.invoke(BaseModelMBean.java:503) at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeployInternal(TomcatDeployer.java:297) at org.jboss.web.tomcat.tc5.TomcatDeployer.performDeploy(TomcatDeployer.java:103) at org.jboss.web.AbstractWebDeployer.start(AbstractWebDeployer.java:371) at org.jboss.web.WebModule.startModule(WebModule.java:83) at org.jboss.web.WebModule.startService(WebModule.java:61) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy40.start(Unknown Source) at org.jboss.web.AbstractWebContainer.start(AbstractWebContainer.java:466) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.interceptor.DynamicInterceptor.invoke(DynamicInterceptor.java:97) at org.jboss.system.InterceptorServiceMBeanSupport.invokeNext(InterceptorServiceMBeanSupport.java:238) at org.jboss.ws.integration.jboss.DeployerInterceptor.start(DeployerInterceptor.java:92) at org.jboss.deployment.SubDeployerInterceptorSupport$XMBeanInterceptor.start(SubDeployerInterceptorSupport.java:188) at org.jboss.deployment.SubDeployerInterceptor.invoke(SubDeployerInterceptor.java:95) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy41.start(Unknown Source) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:490) at java.lang.Thread.run(Thread.java:619) 10:47:25,625 INFO [JipletService] Received a request to start deployment file:/C:/jboss-4.0.5.GA/server/default/tmp/deploy/tmp3 10:47:25,625 INFO [JipletService] Received a request from J2EE deployer to add a realm with path: /C:/jboss-4.0.5.GA/server/def 10:47:25,796 ERROR [JipletService] Error creating realm: org.cafesip.jiplet.JipletException: javax.naming.NameNotFoundException: org.cafesip.jiplet.JipletException: javax.naming.NameNotFoundException: ejb not bound at org.cafesip.sipexchange.realms.sip.SipExchangeRealm.init(SipExchangeRealm.java:136) at org.cafesip.jiplet.JipletContainer.startRealm(JipletContainer.java:1633) at org.cafesip.jiplet.JipletContainer.deployRealm(JipletContainer.java:1578) at org.cafesip.jiplet.JipletContainer.createJ2eeRealm(JipletContainer.java:1681) at org.cafesip.jiplet.jboss.SrrDeployer.start(SrrDeployer.java:103) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:490) at java.lang.Thread.run(Thread.java:619) Caused by: javax.naming.NameNotFoundException: ejb not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) at org.jnp.server.NamingServer.getBinding(NamingServer.java:537) at org.jnp.server.NamingServer.getObject(NamingServer.java:543) at org.jnp.server.NamingServer.lookup(NamingServer.java:267) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305) at sun.rmi.transport.Transport$1.run(Transport.java:159) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:155) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:535) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(TCPTransport.java:790) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:649) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:255) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:233) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:142) at org.jnp.server.NamingServer_Stub.lookup(Unknown Source) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:625) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:587) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.cafesip.sipexchange.realms.sip.SipExchangeRealm.initDomainHome(SipExchangeRealm.java:163) at org.cafesip.sipexchange.realms.sip.SipExchangeRealm.init(SipExchangeRealm.java:131) ... 72 more 10:47:25,796 ERROR [JipletService] Error creating J2EE realm: Realm: 01sipex-realm could not be created. Message: javax.naming.Na 10:47:25,796 WARN [NestedThrowable] Duplicate throwable nesting of same base type: class org.jboss.deployment.DeploymentExceptio 10:47:25,796 ERROR [MainDeployer] Could not start deployment: file:/C:/jboss-4.0.5.GA/server/default/tmp/deploy/tmp37439sipexchan org.jboss.deployment.DeploymentException: Realm: 01sipex-realm could not be created. Message: javax.naming.NameNotFoundException: at org.cafesip.jiplet.jboss.SrrDeployer.start(SrrDeployer.java:111) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1015) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy8.deploy(Unknown Source) at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:421) at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:634) at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:263) at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:336) at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:245) at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:978) at $Proxy0.start(Unknown Source) at org.jboss.system.ServiceController.start(ServiceController.java:417) at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.server.Invocation.invoke(Invocation.java:86) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy4.start(Unknown Source) at org.jboss.deployment.SARDeployer.start(SARDeployer.java:302) at org.jboss.deployment.MainDeployer.start(MainDeployer.java:1025) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:819) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:782) at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:766) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:155) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94) at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:133) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:142) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659) at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210) at $Proxy5.deploy(Unknown Source) at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:482) at org.jboss.system.server.ServerImpl.start(ServerImpl.java:362) at org.jboss.Main.boot(Main.java:200) at org.jboss.Main$1.run(Main.java:490) at java.lang.Thread.run(Thread.java:619) Caused by: org.jboss.deployment.DeploymentException: Realm: 01sipex-realm could not be created. Message: javax.naming.NameNotFoun at org.cafesip.jiplet.jboss.SrrDeployer.start(SrrDeployer.java:106) ... 68 more 10:47:25,828 ERROR [URLDeploymentScanner] Incomplete Deployment listing: --- Incompletely deployed packages --- org.jboss.deployment.DeploymentInfo@82ab64bb { url=file:/C:/jboss-4.0.5.GA/server/default/deploy/sipexchange.esr } deployer: org.cafesip.jiplet.jboss.EsrDeployer@1ff5c98 status: Deployment FAILED reason: Realm: 01sipex-realm could not be created. Message: javax.naming.NameNotFoundException: ejb n state: FAILED watch: file:/C:/jboss-4.0.5.GA/server/default/deploy/sipexchange.esr altDD: null lastDeployed: 1188463644000 lastModified: 1188463642687 mbeans: 10:47:25,921 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080 10:47:26,078 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009 10:47:26,125 INFO [JkMain] Jk running ID=0 time=0/79 config=null 10:47:26,140 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8443 10:47:26,156 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 20s:94ms --------------------------------- Ne gardez plus qu'une seule adresse mail ! Copiez vos mails vers Yahoo! Mail |
From: Becky M. <bec...@qu...> - 2007-08-02 12:24:10
|
Dinesh, When you receive the 401 from the server you'll need to form an 'Authorization' header - it uses some fields from the WWW-Authenticate header - and add that Authorization header to your REGISTER request before you resend it to the server. See RFC3261 for more details on what you have to do at the client side (ie, you also have to increment CSEQ). There are examples out there you can use - for one you can download the SipUnit source code from cafesip.org and follow the code in the SipPhone.register() method. If your second REGISTER message isn't getting to the server, you need to figure out how to see/trace what's going on at the client side. Good luck- Becky Dinesh wrote: >Hi, > > I must admit at the out-set that I'm new to the J2ME world and to top it using SIP for a POC. I came across the sip-exchange server and really liked the product and the potential the software provides to the person with ideas (like me). I have written a small registration module to begin with which doesn't seem to flow the way I expected............ > > I'm sending the REGISTER SIP message to the sip-exchange to register the location + precense , I get back '401 Unauthorised' after the 401 error I set the credentials by copying the WWW-Authenticate header from the response. I was hoping to see another sip message sent to the exchange but unable to see any more messages in the SIP-MONITOR. > > Please find attached the request response > >2007-07-31 10:58:34,680 INFO [STDOUT] <message >from="10.65.18.57:1896" >to="10.65.18.57:5060" >time="1185875914680" >isSender="false" >transactionId="z9hg4bk8d0adf4aaf6b915680f828c023d1ebfb" >callId="84de47c84f386434b5eb8027f23d56a0@10.65.18.57" >firstLine="REGISTER sip:10.65.18.57:5060 SIP/2.0" >debugLine="1684" > > ><![CDATA[REGISTER sip:10.65.18.57:5060 SIP/2.0 >Call-ID: 84de47c84f386434b5eb8027f23d56a0@10.65.18.57 >CSeq: 1 REGISTER >Via: SIP/2.0/UDP 10.65.18.57:1896;branch=z9hG4bK8d0adf4aaf6b915680f828c023d1ebfb >Max-Forwards: 70 >From: <sip:te...@te...>;tag=1205115767 >To: <sip:te...@te...> >Contact: <sip:test@10.65.18.57:1896> >Content-Length: 0 > >]]> ></message> >2007-07-31 10:58:34,680 DEBUG [org.cafesip.jiplet.jboss.JipletService] Received a SIP request with no authentication header >2007-07-31 10:58:34,695 DEBUG [org.jboss.ejb3.entity.ManagedEntityManagerFactory] ************** closing entity managersession ************** >2007-07-31 10:58:34,695 INFO [STDOUT] <message >from="10.65.18.57:5060" >to="10.65.18.57:1896" >time="1185875914695" >isSender="true" >transactionId="z9hg4bk8d0adf4aaf6b915680f828c023d1ebfb" >callId="84de47c84f386434b5eb8027f23d56a0@10.65.18.57" >firstLine="SIP/2.0 401 Please provide your credentials" >debugLine="1738" > > ><![CDATA[SIP/2.0 401 Please provide your credentials >Call-ID: 84de47c84f386434b5eb8027f23d56a0@10.65.18.57 >CSeq: 1 REGISTER >Via: SIP/2.0/UDP 10.65.18.57:1896;branch=z9hG4bK8d0adf4aaf6b915680f828c023d1ebfb >Max-Forwards: 70 >From: <sip:te...@te...>;tag=1205115767 >To: <sip:te...@te...> >WWW-Authenticate: Digest nonce="x2+2GxQBAAAOD4kG",algorithm=MD5,realm="test.com",domain="sip:cafesip.org",opaque="7ZeDGxQBAAAOD4kG",stale=true >Content-Length: 0 > >]]> ></message> > > Please correct me where I'm going wrong. > > Thanks in advance > >Regards, >Dinesh > > > > > ____________________________________________________________________________________ >Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 > > > >------------------------------------------------------------------------- >This SF.net email is sponsored by: Splunk Inc. >Still grepping through log files to find problems? Stop. >Now Search log events and configuration files using AJAX and a browser. >Download your FREE copy of Splunk now >> http://get.splunk.com/ >_______________________________________________ >Cafesip-sipexchange mailing list >Caf...@li... >https://lists.sourceforge.net/lists/listinfo/cafesip-sipexchange > > > |
From: Dinesh <coo...@ya...> - 2007-07-31 12:19:08
|
Hi,=0A=0A I must admit at the out-set that I'm new to the J2ME world an= d to top it using SIP for a POC. I came across the sip-exchange server and = really liked the product and the potential the software provides to the per= son with ideas (like me). I have written a small registration module to beg= in with which doesn't seem to flow the way I expected............=0A=0A = I'm sending the REGISTER SIP message to the sip-exchange to register the l= ocation + precense , I get back '401 Unauthorised' after the 401 error I se= t the credentials by copying the WWW-Authenticate header from the response.= I was hoping to see another sip message sent to the exchange but unable to= see any more messages in the SIP-MONITOR.=0A=0A Please find attached t= he request response=0A=0A2007-07-31 10:58:34,680 INFO [STDOUT] <message=0A= from=3D"10.65.18.57:1896" =0Ato=3D"10.65.18.57:5060" =0Atime=3D"11858759146= 80" =0AisSender=3D"false" =0AtransactionId=3D"z9hg4bk8d0adf4aaf6b915680f828= c023d1ebfb" =0AcallId=3D"84de47c84f386434b5eb8027f23d56a0@10.65.18.57" =0Af= irstLine=3D"REGISTER sip:10.65.18.57:5060 SIP/2.0" =0AdebugLine=3D"1684" = =0A>=0A<![CDATA[REGISTER sip:10.65.18.57:5060 SIP/2.0=0ACall-ID: 84de47c84f= 386434b5eb8027f23d56a0@10.65.18.57=0ACSeq: 1 REGISTER=0AVia: SIP/2.0/UDP 10= .65.18.57:1896;branch=3Dz9hG4bK8d0adf4aaf6b915680f828c023d1ebfb=0AMax-Forwa= rds: 70=0AFrom: <sip:te...@te...>;tag=3D1205115767=0ATo: <sip:test@test.c= om>=0AContact: <sip:test@10.65.18.57:1896>=0AContent-Length: 0=0A=0A]]>=0A<= /message>=0A2007-07-31 10:58:34,680 DEBUG [org.cafesip.jiplet.jboss.JipletS= ervice] Received a SIP request with no authentication header=0A2007-07-31 1= 0:58:34,695 DEBUG [org.jboss.ejb3.entity.ManagedEntityManagerFactory] *****= ********* closing entity managersession **************=0A2007-07-31 10:58:3= 4,695 INFO [STDOUT] <message=0Afrom=3D"10.65.18.57:5060" =0Ato=3D"10.65.18= .57:1896" =0Atime=3D"1185875914695" =0AisSender=3D"true" =0AtransactionId= =3D"z9hg4bk8d0adf4aaf6b915680f828c023d1ebfb" =0AcallId=3D"84de47c84f386434b= 5eb8027f23d56a0@10.65.18.57" =0AfirstLine=3D"SIP/2.0 401 Please provide you= r credentials" =0AdebugLine=3D"1738" =0A>=0A<![CDATA[SIP/2.0 401 Please pro= vide your credentials=0ACall-ID: 84de47c84f386434b5eb8027f23d56a0@10.65.18.= 57=0ACSeq: 1 REGISTER=0AVia: SIP/2.0/UDP 10.65.18.57:1896;branch=3Dz9hG4bK8= d0adf4aaf6b915680f828c023d1ebfb=0AMax-Forwards: 70=0AFrom: <sip:test@test.c= om>;tag=3D1205115767=0ATo: <sip:te...@te...>=0AWWW-Authenticate: Digest n= once=3D"x2+2GxQBAAAOD4kG",algorithm=3DMD5,realm=3D"test.com",domain=3D"sip:= cafesip.org",opaque=3D"7ZeDGxQBAAAOD4kG",stale=3Dtrue=0AContent-Length: 0= =0A=0A]]>=0A</message>=0A=0A Please correct me where I'm going wrong.= =0A=0A Thanks in advance=0A=0ARegards,=0ADinesh=0A=0A=0A=0A=0A = ___________________________________________________________________________= _________=0AShape Yahoo! in your own image. Join our Network Research Pane= l today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=3D7 = =0A=0A |
From: Becky M. <bec...@qu...> - 2007-05-03 14:20:45
|
Hi Ricardo, When user A adds user B to user A's contact list, user B should receive an email. The email says something like 'user A wants to contact you' and it gives a link where user B can go to accept or reject the request to be contacted by A. Until user B accepts, he will appear "offline" to user A. Email has to be used for this because we can't modify the client (Messenger, etc.) to make it happen there. When you created the users (subscribers) in the system from the sipexchange console, did you fill in an email address for them? That is where the email will go. Check this, and also check the sipexchange-mail-service.xml file if you haven't already (instructions below). It has SMTP server info such as server and username - sipexchange will use this to send emails. I set it to my ISP smtp server address and put my mail server username there, in the same way I set up my email client to send/receive emails through my ISP. You can check if this is working by adding another new sipexchange subscriber through the sipex console and put your email address as the subscriber's email address - sipex will try to send a welcome-new-subscriber email to this address. If there's a problem with the email sending you should see an error message when you hit the 'Create' button while creating the new subscriber. If there's no error, check your email and make sure you got the welcome email in your inbox. Here are the instructions from the SipExchange Installation page for setting up the email service so that SipExchange can send emails: 1. Finally, set up a mail service so that SipExchange application can send emails. You will need to know the SMTP server name to which the SipExchange relays all the emails to. If your SMTP server requires an user name and password, you need to obtain these. Please contact your system administrator for this information if you don't have it. Once you have obtained the information, follow the steps below: 1. Open the file $SIPEXCHANGE_HOME/deployment/sipexchange-mail-service.xml using a text editor of your choice. 2. Search for the code segment that looks like <property name="mail.smtp.host" value="SMTP.SERVER.ADDRESS"/> Replace the SMTP.SERVER>ADDRESS text with the real SMTP server address you are using. 3. Search for the code segment that looks like <property name="mail.from" value="MYEMAIL@MYDOMAIN"/> Replace the MYEMAIL@MYDOMAIN text with a real email address of the system administrator (yours?). 4. If your SMTP server requires authentication, search for the code segment that looks like <attribute name="User">nobody</attribute> <attribute name="Password">password</attribute> Replace the nobody with the user name and password with the real password. Regards, Becky Ricardo Bandeira wrote: > Hello Everybody, > > I´m trying to use Windows Messenger 5.1 (5.1.0701) with sipexchange. I > follow all the steps in sipexchange page to configure messenger. > I have to clients in to different PC´s but one of this client is in > the same PC that the sipex. When i sign in the clients, they login in > the sipex without problems. If i try to logout and login another time > they work properly. > But when i add a contact to messenger he always appears offline, and > don´t appears nothing to accept the new contact in the other client. > Anybody knows where probably is the problem? > > Regards, > > Ricardo > >------------------------------------------------------------------------ > >------------------------------------------------------------------------- >This SF.net email is sponsored by DB2 Express >Download DB2 Express C - the FREE version of DB2 express and take >control of your XML. No limits. Just data. Click to get it now. >http://sourceforge.net/powerbar/db2/ > >------------------------------------------------------------------------ > >_______________________________________________ >Cafesip-sipexchange mailing list >Caf...@li... >https://lists.sourceforge.net/lists/listinfo/cafesip-sipexchange > > |
From: Ricardo B. <ric...@cl...> - 2007-05-02 11:53:16
|
Hello Everybody, I=B4m trying to use Windows Messenger 5.1 (5.1.0701) with sipexchange. I = follow all the steps in sipexchange page to configure messenger.=20 I have to clients in to different PC=B4s but one of this client is in = the same PC that the sipex. When i sign in the clients, they login in = the sipex without problems. If i try to logout and login another time = they work properly.=20 But when i add a contact to messenger he always appears offline, and = don=B4t appears nothing to accept the new contact in the other client.=20 Anybody knows where probably is the problem? Regards, Ricardo |
From: Becky M. <bec...@qu...> - 2007-04-24 14:17:36
|
Hi Ricardo, I'm sorry for the late response. Unfortunately there's not a mechanism to 'plug-in' a new trigger type into the management console. Try adding your new trigger to the list of trigger constants in org.cafesip.sipexchange.web.model.Trigger (similar to the lists in org.cafesip.sipexchange.inservice.shared.Trigger and TriggerInfo), build/deploy it. Then your trigger should show up in the Trigger Configuration screen (Trigger dropdown list). In that same screen, for your new feature I think you can just type in the unique name of your feature - it will be sent to the SCP in the trigger message. (I am referring to the screen discussed here: http://www.cafesip.org/projects/sipexchange/external_call_control.html#Trigger_configuration). You may want to study the org.cafesip.sipexchange.web.xyz side of the existing example features if your new feature needs more configuration from the sipex console. Regards, Becky ric...@cl... wrote: > Hello People, > > I want to add a new trigger for the SipExchange, a trigger that i call > "CalledAnswerOkTrigger" and that trigger is to process the response > "OK" from the called subscriber. > I already create the class of the new trigger but i don´t know what i > have to do for the new trigger appears in sipex > console(http://localhost:8080/sipex). > If somebody can help me with that it would be great. I already have > search in the documentation but I don´t find a description how to do > this. > > another thing: I already try to add a new feature but he also don´t > appears in the sipex managemente console. > > Thank You very much and Regards, > > Ricardo Bandeira > ------------------------------------------------------------------------ > >------------------------------------------------------------------------ > >------------------------------------------------------------------------- >This SF.net email is sponsored by DB2 Express >Download DB2 Express C - the FREE version of DB2 express and take >control of your XML. No limits. Just data. Click to get it now. >http://sourceforge.net/powerbar/db2/ > >------------------------------------------------------------------------ > >_______________________________________________ >Cafesip-sipexchange mailing list >Caf...@li... >https://lists.sourceforge.net/lists/listinfo/cafesip-sipexchange > > |
From: <ric...@cl...> - 2007-04-17 15:06:33
|
<HTML> Hello People,<BR> <BR> I want to add a new trigger for the SipExchange, a trigger that i call "CalledAnswerOkTrigger" and that trigger is to process the response "OK" from the called subscriber. <BR> I already create the class of the new trigger but i don=C2=B4t know what i have to do for the new trigger appears in sipex console(http://localhost:8080/sipex).<BR> If somebody can help me with that it would be great. I already have search in the documentation but I don=C2=B4t find a description how t= o do this.<BR> <BR> another thing: I already try to add a new feature but he also don=C2=B4t ap= pears in the sipex managemente console.<BR> <BR> Thank You very much and Regards,<BR> <BR> Ricardo Bandeira </HTML> <BR><hr>= |
From: <ric...@cl...> - 2007-04-17 15:06:11
|
<HTML> Hello People,<BR> <BR> I want to add a new trigger for the SipExchange, a trigger that i call "Cal= ledAnswerOkTrigger" and that trigger is to process the response "OK" from t= he called subscriber. <BR> I already create the class of the new trigger but i don=C2=B4t know what i = have to do for the new trigger appears in sipex console(http://localhost:80= 80/sipex).<BR> If somebody can help me with that it would be great. I already have search = in the documentation but I don=C2=B4t find a description how to do th= is.<BR> <BR> another thing: I already try to add a new feature but he also don=C2=B4t ap= pears in the sipex managemente console.<BR> <BR> Thank You very much and Regards,<BR> <BR> Ricardo Bandeira <BR> </HTML> <BR><hr>= |
From: Becky M. <bec...@qu...> - 2007-04-13 12:58:26
|
Hi, It sounds like the trigger you're most interested in is the ReceivedCall trigger (the MakeCallOrig trigger is an outbound calling trigger and the Call Screening feature is an inbound call feature, the two aren't associated so I was a little confused by the example). Anyway, to see the trigger message contruction/sending take a look at class TriggerProcessor, method: processInviteTriggers() which calls applyCallTerminatedTrigger() and it will eventually call applyRequestTriggers() where the trigger info is actually sent to the SCP. (Also if you haven't already read through it, please see the documentation on triggers (http://www.cafesip.org/projects/sipexchange/external_call_control.html) and the API at http://www.cafesip.org/projects/sipexchange/javadocs/index.html for more info.) Regards Becky Ricardo Bandeira wrote: > Hello Everybody, > > When i have a subscriber trigger for example a "MakeCallOrig trigger" > with the feature "Call Screening", and when i make a call with that > subscriber the sipexchange receive a sip request "Invite" and process > this request in the SipExchangeProxy.java class in the method > "processRequest". > I need to know exactly in the code where the trigger message is > constructed and sent to the SCP of the feature, because i want to add > more information in the message, or in the triggerInfo for example. > > If somebody can help me with that, or describe me all the process when > the trigger is invoke. > > Thanks and Regards, > > Ricardo Bandeira > >------------------------------------------------------------------------ > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share your >opinions on IT & business topics through brief surveys-and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >------------------------------------------------------------------------ > >_______________________________________________ >Cafesip-sipexchange mailing list >Caf...@li... >https://lists.sourceforge.net/lists/listinfo/cafesip-sipexchange > > |
From: Becky M. <bec...@qu...> - 2007-04-13 12:57:09
|
Hi, It sounds like the trigger you're most interested in is the ReceivedCall trigger (the MakeCallOrig trigger is an outbound calling trigger and the Call Screening feature is an inbound call feature, the two aren't associated so I was a little confused by the example). Anyway, to see the trigger message contruction/sending take a look at class TriggerProcessor, method: processInviteTriggers() which calls applyCallTerminatedTrigger() and it will eventually call applyRequestTriggers() where the trigger info is actually sent to the SCP. (Also if you haven't already read through it, please see the documentation on triggers (http://www.cafesip.org/projects/sipexchange/external_call_control.html) and the API at http://www.cafesip.org/projects/sipexchange/javadocs/index.html for more info.) Regards Becky Ricardo Bandeira wrote: > Hello Everybody, > > When i have a subscriber trigger for example a "MakeCallOrig trigger" > with the feature "Call Screening", and when i make a call with that > subscriber the sipexchange receive a sip request "Invite" and process > this request in the SipExchangeProxy.java class in the method > "processRequest". > I need to know exactly in the code where the trigger message is > constructed and sent to the SCP of the feature, because i want to add > more information in the message, or in the triggerInfo for example. > > If somebody can help me with that, or describe me all the process when > the trigger is invoke. > > Thanks and Regards, > > Ricardo Bandeira > >------------------------------------------------------------------------ > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share your >opinions on IT & business topics through brief surveys-and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >------------------------------------------------------------------------ > >_______________________________________________ >Cafesip-sipexchange mailing list >Caf...@li... >https://lists.sourceforge.net/lists/listinfo/cafesip-sipexchange > > |
From: Ricardo B. <ric...@cl...> - 2007-04-12 20:04:05
|
Hello Everybody, When i have a subscriber trigger for example a "MakeCallOrig trigger" = with the feature "Call Screening", and when i make a call with that = subscriber the sipexchange receive a sip request "Invite" and process = this request in the SipExchangeProxy.java class in the method = "processRequest".=20 I need to know exactly in the code where the trigger message is = constructed and sent to the SCP of the feature, because i want to add = more information in the message, or in the triggerInfo for example. If somebody can help me with that, or describe me all the process when = the trigger is invoke. Thanks and Regards, Ricardo Bandeira |
From: Becky M. <bec...@qu...> - 2007-04-03 13:01:32
|
Hi, Given a SIP message, you can get/set the content using the JAIN SIP API javax.sip.message class/methods and then for dealing with the SDP content inside the message body (bandwidth, connection, session description, etc.), there are classes and methods in the javax.sdp package. The NIST (nist.gov) SIP implementation that SipExchange uses has a preliminary implementation of the javax.sdp package (enough to parse SDP content at least it looks like) so you should be able to use the javax.sdp classes/methods to deal with the SDP content from a SIP message body. I haven't done it myself but take a look at the NIST project page (http://snad.ncsl.nist.gov/proj/iptel/) and in there you should find some examples - the JAIN-SIP RI is the implementation available to your SipExchange application code, and the TCK might have some examples of parsing SDP content. SipExchange code itself as far as I know doesn't look inside the message bodies but it gives your application the SIP message so your app can do it. Regards, Becky Ricardo Bandeira wrote: > Hello Everybody, > > I´m using sipexchange but i need to extract the parameters of SDP > packets, like media description and the others. > Somebody knows if sipexchange hava a Class with methods to do this, or > he just copy the integral packet and don´t look for the inside? > > Regards, > > Ricardo Bandeira > >------------------------------------------------------------------------ > >------------------------------------------------------------------------- >Take Surveys. Earn Cash. Influence the Future of IT >Join SourceForge.net's Techsay panel and you'll get the chance to share your >opinions on IT & business topics through brief surveys-and earn cash >http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > >------------------------------------------------------------------------ > >_______________________________________________ >Cafesip-sipexchange mailing list >Caf...@li... >https://lists.sourceforge.net/lists/listinfo/cafesip-sipexchange > > |
From: Ricardo B. <ric...@cl...> - 2007-03-31 11:26:02
|
Hello Everybody, I=B4m using sipexchange but i need to extract the parameters of SDP = packets, like media description and the others. Somebody knows if sipexchange hava a Class with methods to do this, or = he just copy the integral packet and don=B4t look for the inside? Regards, Ricardo Bandeira |
From: Amit C. <ami...@ca...> - 2006-07-17 10:48:03
|
SipExchange 0.0.3a released Many new features added July 16, 2006, Raleigh, NC. We are pleased to announce the release of SipExchange r0.0.3a. This is an Alpha release to give users a preview of the system. SipExchange is an open-source softswitch that provides standard SIP services like registration, proxy and presence. Using the SipExchange application, service providers can offer telephone services to their subscribers as well as other services based on voice, video and instant messaging. SipExchange supports many of the standard subscriber features offered by the traditional telephone exchanges and PBXs. In addition, SipExchange supports external call control capabilities using which service providers and software developers can create new features and services rapidly and plug them into the SipExchange application. Major new features have been added since the previous release. The following are the highlights of the release. 1. The following subscriber features have been added: 1. Call forwarding 2. Call Screening. 2. The following system-level features have been added: 1. Multiple Appearance Address: One number rings many phones 2. SIP Gateway: Allows communication with a SIP carrier or service provider. 3. Code coverage tool added (only of importance to developers). 4. Many bugs have been fixed. If you have any questions about the project, please contact us by sending an email to sip...@ca... <mailto:sip...@ca...>. -- CafeSip Team. |
From: Amit C. <ami...@qu...> - 2006-04-27 11:57:18
|
SipExchange 0.0.2a released Presence functionality implemented April 23, 2006, Raleigh, NC. We are pleased to announce the release of SipExchange r0.0.2a. This is an Alpha release to give users a preview of the system. SipExchange is an open-source softswitch that provides standard SIP services like registration, proxy and presence. Using the SipExchange application, service providers can offer telephone services to their subscribers as well as other services based on voice, video and instant messaging. SipExchange supports many of the standard subscriber features offered by the traditional telephone exchanges and PBXs. In addition, SipExchange supports external call control capabilities using which service providers and software developers can create new features and services rapidly and plug them into the SipExchange application. Major new features have been added since the previous release. The following are the highlights of the release. 1. An early version of the presence service has been implemented. The presence service allows subscribers to add other subscribers to their contact list and monitor their presence. The feature allows subscribers to authorize or block request for subscriptions. There are many limitations that will be fixed in the next release. 2. An early version of the Subscriber Console has been implemented. The subscriber console is a web-based user interface using which subscribers can manage their account, contacts and their features. 3. The proxy code has been re-written to handle proxy-related issues that caused SipExchange to not work with many SIP phones. 4. The administration console has been revamped. Administrator accounts can now be managed from the console and domain parameters can now be configured. There are many other look and feel changes as well. 5. Email templates have been added. This feature will allow emails sent out by SipExchange to be customized on a per-domain basis using the powerful Apache Velocity templates. 6. Many bugs have been fixed. If you have any questions about the project, please contact us by sending an email to sip...@ca.... -- CafeSip Team. |
From: Becky M. <bec...@qu...> - 2006-04-07 02:56:10
|
To turn on the jiplet server trace: If you're using JBOSS, edit the file $JBOSS_HOME/server/$RUN/conf/jiplet/server.xml . If you're using Jiplet Stand-alone container, edit the file $JIPLET_HOME/conf/server.xml. Search for a segment that looks like: <jip-property key="gov.nist.javax.sip.TRACE_LEVEL" value="0"/> <jip-property key="gov.nist.javax.sip.DEBUG_LOG" value="proxyserver_log.txt"/> Modify it to look something like: <jip-property key="gov.nist.javax.sip.TRACE_LEVEL" value="32"/> <!-- or 16 for less --> <jip-property key="gov.nist.javax.sip.DEBUG_LOG" value="C:\proxyserver_log.txt"/> and restart JBOSS, or the Jiplet stand-alone server if you're not using JBOSS. At this point, all the SIP messages will be saved in the file C:\proxyserver_log.txt. Becky McElroy wrote: > Aman, > > Could you please repeat the problem and send to us: > a) the trace from the xlite phone - you can get it by right-clicking > the mouse over the xlite phone (Diagnostic Log) > b) the trace from the jiplet server - for this, see the comments in > the Jiplet Container server.xml (set <jip-property > key="gov.nist.javax.sip.TRACE_LEVEL" value="16"/>) and restart the > container before repeating the problem. > > Regards, > Becky > > > root wrote: > >> Sir, >> thanks for ur replay, sir i found a error in sip exchange is that >> when i use xlite and make a call to mobile number the xlite show trying >> (no ringing tone)and the call is connected but still xlite show trying >> and when we open Cdr in sipconsole the call duration is not given and >> the call status is connected. >> we listen both side voice clearly but the problem is we can see the call >> duration. >> >> but when i used myjiplet application using jiplet the call is connected >> and we listean ringing tone also,but in sipexchnage we can not hear >> ringing. so please send the solution as soon as possible. >> >> Regards >> Aman Sachdeva >> >> >> ------------------------------------------------------- >> This SF.Net email is sponsored by xPML, a groundbreaking scripting >> language >> that extends applications into web and mobile media. Attend the live >> webcast >> and join the prime developer group breaking into this new coding >> territory! >> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >> _______________________________________________ >> Cafesip-sipexchange mailing list >> Caf...@li... >> https://lists.sourceforge.net/lists/listinfo/cafesip-sipexchange >> >> >> > > |
From: Becky M. <bec...@qu...> - 2006-04-07 02:46:19
|
Aman, Could you please repeat the problem and send to us: a) the trace from the xlite phone - you can get it by right-clicking the mouse over the xlite phone (Diagnostic Log) b) the trace from the jiplet server - for this, see the comments in the Jiplet Container server.xml (set <jip-property key="gov.nist.javax.sip.TRACE_LEVEL" value="16"/>) and restart the container before repeating the problem. Regards, Becky root wrote: >Sir, > thanks for ur replay, sir i found a error in sip exchange is that >when i use xlite and make a call to mobile number the xlite show trying >(no ringing tone)and the call is connected but still xlite show trying >and when we open Cdr in sipconsole the call duration is not given and >the call status is connected. >we listen both side voice clearly but the problem is we can see the call >duration. > >but when i used myjiplet application using jiplet the call is connected >and we listean ringing tone also,but in sipexchnage we can not hear >ringing. so please send the solution as soon as possible. > >Regards >Aman Sachdeva > > > >------------------------------------------------------- >This SF.Net email is sponsored by xPML, a groundbreaking scripting language >that extends applications into web and mobile media. Attend the live webcast >and join the prime developer group breaking into this new coding territory! >http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 >_______________________________________________ >Cafesip-sipexchange mailing list >Caf...@li... >https://lists.sourceforge.net/lists/listinfo/cafesip-sipexchange > > > |