exception while using 2 ra entities for SIP

42 views
Skip to first unread message

yulian_o

unread,
May 15, 2012, 9:54:32 AM5/15/12
to mobicent...@googlegroups.com
Hello to all
I am trying to use SIP RA with 2 different ip addresses.

I have configured deploy config as follows :

<?xml version="1.0" encoding="UTF-8"?>
<deploy-config>
    <ra-entity
        resource-adaptor-id="ResourceAdaptorID[name=JainSipResourceAdaptor,vendor=net.java.slee.sip,version=1.2]"
        entity-name="OutsideSipRA">
        <properties>
            <property name="javax.sip.PORT" type="java.lang.Integer" value="5060" />
            <property name="javax.sip.IP_ADDRESS" type="java.lang.String" value="X.X.X.X" />
            <property name="javax.sip.TRANSPORT" type="java.lang.String" value="UDP,TCP" />
            <!-- the list of SIP balancers, in the form of "HOST:PORT",
            separated by ";", it is only used if the heart beat service property is defined.
            In case it is Mobicents SIP Load Balancer and it is configured with 2 ports,
            use here the internal one
            <property name="org.mobicents.ha.javax.sip.BALANCERS"
                type="java.lang.String" value="127.0.0.1:5065" />
             -->
        </properties>
        <ra-link name="OutsideSipRA" />
    </ra-entity>
    <ra-entity
        resource-adaptor-id="ResourceAdaptorID[name=JainSipResourceAdaptor,vendor=net.java.slee.sip,version=1.2]"
        entity-name="InsideSipRA">
        <properties>
            <property name="javax.sip.PORT" type="java.lang.Integer" value="5060" />
            <property name="javax.sip.IP_ADDRESS" type="java.lang.String" value="Y.Y.Y.Y" />
            <property name="javax.sip.TRANSPORT" type="java.lang.String" value="UDP" />
            <!-- the list of SIP balancers, in the form of "HOST:PORT",
            separated by ";", it is only used if the heart beat service property is defined.
            In case it is Mobicents SIP Load Balancer and it is configured with 2 ports,
            use here the internal one
            <property name="org.mobicents.ha.javax.sip.BALANCERS"
                type="java.lang.String" value="127.0.0.1:5065" />
             -->
        </properties>
        <ra-link name="InsideSipRA" />
    </ra-entity>
</deploy-config>

and it indeed binds to 2 different ip addresses on transports i have defined.
I have configured the following in sbb :
<resource-adaptor-type-binding>
            <resource-adaptor-type-ref>
                <resource-adaptor-type-name>JAIN SIP</resource-adaptor-type-name>
                <resource-adaptor-type-vendor>javax.sip</resource-adaptor-type-vendor>
                <resource-adaptor-type-version>1.2</resource-adaptor-type-version>
            </resource-adaptor-type-ref>
            <activity-context-interface-factory-name>slee/resources/jainsip/1.2/acifactory</activity-context-interface-factory-name>
            <resource-adaptor-entity-binding>
                <resource-adaptor-object-name>slee/resources/jainsip/1.2/outsideProvider</resource-adaptor-object-name>
                <resource-adaptor-entity-link>OutsideSipRA</resource-adaptor-entity-link>
            </resource-adaptor-entity-binding>       
            <resource-adaptor-entity-binding>
                <resource-adaptor-object-name>slee/resources/jainsip/1.2/insideProvider</resource-adaptor-object-name>
                <resource-adaptor-entity-link>InsideSipRA</resource-adaptor-entity-link>
            </resource-adaptor-entity-binding>
        </resource-adaptor-type-binding>

But When i am trying to use :
ActivityContextInterface localActivityContextInterface = this.sipActivityContextInterfaceFactory.getActivityContextInterface(event.getServerTransaction()); i get an exception :

2012-05-15 16:42:22,342 INFO  [javax.slee.RAEntityNotification[entity=OutsideSipRA].SipResourceAdaptor] Received Request:
REGISTER sip:sipme.mobi;transport=UDP SIP/2.0
Route: <sip:p.sipme.mobi;lr;transport=UDP>
Via: SIP/2.0/UDP 10.0.0.5:5060;branch=z9hG4bKoe5o6kdg31hc6bb99t3gkma;rport=5060;received=81.218.194.171
From: <sip:05558...@sipme.mobi>;tag=rs6o6kbcgdhc72lr9t3g
To: <sip:05558...@sipme.mobi>
Contact: <sip:05558...@10.0.0.5;transport=UDP>;expires=3600
CSeq: 315221 REGISTER
Call-ID: _9C3kghKoIfJ0kZ72zCT5BvKFNgFgG
Supported: sec-agree
User-Agent: E71-1 RM-346 501.21.001
Max-Forwards: 70
Content-Length: 0


2012-05-15 16:42:22,348 INFO  [javax.slee.SbbNotification[service=ServiceID[name=PCSCF Registrar Service,vendor=Web Ukraine,version=1.0.0.0],sbb=SbbID[name=Registrar Proxy,vendor=Web Ukraine,version=1.0.0.0]].RegistrarProxySbb] SETTING INITIAL ACI
2012-05-15 16:42:22,349 ERROR [org.mobicents.slee.runtime.eventrouter.routingtask.EventRoutingTaskImpl] Caught exception while routing EventContext[event type id = EventTypeID[name=javax.sip.message.Request.REGISTER,vendor=net.java.slee,version=1.2] , event = RequestEventWrapper[ EVENT[REGISTER] DIALOG[null] TX[ServerTransaction[z9hG4bKoe5o6kdg31hc6bb99t3gkma]]] , local ac = RA:OutsideSipRA:z9hg4bkoe5o6kdg31hc6bb99t3gkma , address = SIP: <sip:05558...@sipme.mobi> , serviceID = null]
javax.slee.UnrecognizedActivityException
        at org.mobicents.slee.resource.AbstractActivityContextInterfaceFactory.getACI(AbstractActivityContextInterfaceFactory.java:108)
        at net.java.slee.resource.sip.SipActivityContextInterfaceFactoryImpl.getActivityContextInterface(SipActivityContextInterfaceFactoryImpl.java)
        at com.webukraine.ims.core.pcscf.RegistrarProxySbb.onINITIALREGISTER(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:616)
        at org.mobicents.slee.runtime.sbbentity.SbbEntityImpl.invokeEventHandler(SbbEntityImpl.java:478)
        at org.mobicents.slee.runtime.eventrouter.routingtask.EventRoutingTaskImpl.routeQueuedEvent(EventRoutingTaskImpl.java:378)
        at org.mobicents.slee.runtime.eventrouter.routingtask.EventRoutingTaskImpl.run(EventRoutingTaskImpl.java:126)
        at org.mobicents.slee.runtime.eventrouter.EventRouterExecutorImpl$EventRoutingTaskStatsCollector.run(EventRouterExecutorImpl.java:73)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:636)


What i am doing wrong?

Best regards
Yulian Oifa

Alexandre Mendonça

unread,
May 15, 2012, 10:49:35 AM5/15/12
to mobicent...@googlegroups.com
It seems to be the same issue as http://code.google.com/p/mobicents/issues/detail?id=3174 which is fixed in trunk.

Regards,

--
Alexandre Mendonça // JBoss R&D
http://ammendonca.blogspot.com/

Eduardo Martins

unread,
May 15, 2012, 10:50:26 AM5/15/12
to mobicent...@googlegroups.com
I believe this was fixed on SVN trunk recently, see http://code.google.com/p/mobicents/issues/detail?id=3174

-- Eduardo
..............................................
http://emmartins.blogspot.com



On Tue, May 15, 2012 at 2:54 PM, yulian_o <oifa....@gmail.com> wrote:

yulian_o

unread,
May 15, 2012, 11:00:20 AM5/15/12
to mobicent...@googlegroups.com
Hello Eduardo
I have applied patch from trunk but with no luck , still getting same exception.
I am using 2.4.2-Snapshots version.
Is there any other files i should modify?
Also where i can find source of net.java.slee.resource.sip.SipActivityContextInterfaceFactoryImpl?


Best regards
Yulian Oifa

Eduardo Martins

unread,
May 15, 2012, 12:31:15 PM5/15/12
to mobicent...@googlegroups.com
Is there something that prevents you from using latest 2.7.0-SNAPSHOT, this way if there is anything else to fix we do it now...

-- Eduardo
..............................................
http://emmartins.blogspot.com



yulian_o

unread,
May 15, 2012, 1:10:40 PM5/15/12
to mobicent...@googlegroups.com
Hello Eduardo
I have updated to 2.7.0 actually the only change was this issue , so it looks like library jar files resolved the issue.

Best regards
Yulian Oifa
Reply all
Reply to author
Forward
0 new messages