Jain-slee with multiple IP

236 views
Skip to first unread message

Laurent Schweizer

unread,
Mar 7, 2012, 5:04:51 AM3/7/12
to mobicent...@googlegroups.com

Hello,

 

I have started jain-slee with the option –b 10.0.0.9  so he must use this IP but the problem is that sometimes he use the default IP (eth0) of the server 10.0.0.5  to send message ( new transaction in TCP ) see NOTIFY.

 

I’m using the last version of Jain-slee 2.6.0 FINAL.

 

Any Idea ?

 

Regards

 

Laurent

 

T 2012/03/07 10:23:32.299412 10.0.0.6:36491 -> 10.0.0.9:5060 [AP]

SUBSCRIBE sip:90796...@10.0.0.9:5060;transport=tcp SIP/2.0.

Record-Route: <sip:10.0.0.6;transport=tcp;lr=on>.

Via: SIP/2.0/TCP 10.0.0.6;branch=z9hG4bK1cef.b826135.0;i=c0e63.

Via: SIP/2.0/TCP 192.168.1.40:2057;received=62.12.250.165;branch=z9hG4bK-atcuu3gvtqrq;rport=15445.

From: <sip:90796...@pbx.peoplefone.com>;tag=bwq6750ftr.

To: <sip:90796...@pbx.peoplefone.com>.

Call-ID: 3c2670c7cf5d-rjaaqq07cw8o.

CSeq: 2 SUBSCRIBE.

Max-Forwards: 69.

Contact: <sip:90796...@62.12.250.165:15445;transport=tcp;line=qedkno8x>;reg-id=1.

Event: message-summary.

Accept: application/simple-message-summary.

User-Agent: snom320/8.4.32.

Expires: 3600.

Content-Length: 0.

.

 

 

T 2012/03/07 10:23:32.305902 10.0.0.9:5060 -> 10.0.0.6:36491 [AP]

SIP/2.0 100 Trying.

To: <sip:90796...@pbx.peoplefone.com>.

Via: SIP/2.0/TCP 10.0.0.6;branch=z9hG4bK1cef.b826135.0;i=c0e63;received=10.0.0.6;rport=36491,SIP/2.0/TCP 192.168.1.40:2057;received=62.12.250.165;branch=z9hG4bK-atcuu3gvtqrq;rport=15445.

CSeq: 2 SUBSCRIBE.

Call-ID: 3c2670c7cf5d-rjaaqq07cw8o.

From: <sip:90796...@pbx.peoplefone.com>;tag=bwq6750ftr.

Content-Length: 0.

.

 

 

T 2012/03/07 10:23:32.315148 10.0.0.9:5060 -> 10.0.0.6:36491 [AP]

SIP/2.0 200 OK.

To: <sip:90796...@pbx.peoplefone.com>;tag=cdc7a0b7.

Via: SIP/2.0/TCP 10.0.0.6;branch=z9hG4bK1cef.b826135.0;i=c0e63;received=10.0.0.6;rport=36491,SIP/2.0/TCP 192.168.1.40:2057;received=62.12.250.165;branch=z9hG4bK-atcuu3gvtqrq;rport=15445.

Record-Route: <sip:10.0.0.6;transport=tcp;lr=on>.

CSeq: 2 SUBSCRIBE.

Call-ID: 3c2670c7cf5d-rjaaqq07cw8o.

From: <sip:90796...@pbx.peoplefone.com>;tag=bwq6750ftr.

Expires: 3600.

Content-Length: 0.

.

 

 

T 2012/03/07 10:23:32.321767 10.0.0.5:49977 -> 10.0.0.6:5060 [AP]

NOTIFY sip:90796...@62.12.250.165:15445;transport=tcp;line=qedkno8x SIP/2.0.

Via: SIP/2.0/TCP 10.0.0.9:5060;branch=z9hG4bK-343838-5a2a7838df3a32e0bb9e776ac8b99c06.

CSeq: 1 NOTIFY.

From: <sip:90796...@pbx.peoplefone.com>;tag=cdc7a0b7.

To: <sip:90796...@pbx.peoplefone.com>;tag=bwq6750ftr.

Call-ID: 3c2670c7cf5d-rjaaqq07cw8o.

Max-Forwards: 70.

Contact: <sip:10.0.0.9:5060;transport=tcp>.

Event: message-summary.

Route: <sip:10.0.0.6;transport=tcp;lr=on>.

Subscription-State: active.

Content-Type: application/simple-message-summary.

Content-Length: 100.

.

Messages-Waiting: yes

Message-Account: sip:90796...@app1.peoplefone.ch

Voice-Message:3/3(0/0)

 

 

LOG  of SIP stack:

 

<message

from="10.0.0.9:5060"

to="10.0.0.6:5060"

time="1331112212321"

isSender="true"

transactionId="z9hg4bk-343838-5a2a7838df3a32e0bb9e776ac8b99c06"

callId="3c2670c7cf5d-rjaaqq07cw8o"

firstLine="NOTIFY sip:90796...@62.12.250.165:15445;transport=tcp;line=qedkno8x SIP/2.0"

> 

<![CDATA[NOTIFY sip:90796...@62.12.250.165:15445;transport=tcp;line=qedkno8x SIP/2.0^M

Via: SIP/2.0/TCP 10.0.0.9:5060;branch=z9hG4bK-343838-5a2a7838df3a32e0bb9e776ac8b99c06^M

CSeq: 1 NOTIFY^M

From: <sip:90796...@pbx.peoplefone.com>;tag=cdc7a0b7^M

To: <sip:90796...@pbx.peoplefone.com>;tag=bwq6750ftr^M

Call-ID: 3c2670c7cf5d-rjaaqq07cw8o^M

Max-Forwards: 70^M

Contact: <sip:10.0.0.9:5060;transport=tcp>^M

Event: message-summary^M

Route: <sip:10.0.0.6;transport=tcp;lr=on>^M

Subscription-State: active^M

Content-Type: application/simple-message-summary^M

Content-Length: 100^M

^M

]]>

</message>

Laurent Schweizer

unread,
Mar 24, 2012, 11:22:22 AM3/24/12
to mobicent...@googlegroups.com

Hello all,

 

Regarding this problem  I see that it’s with TCP only.

 

To do more test  I have created a simple SBB that only send 2 NOTIFY (first one with UDP, second one with TCP) when the SBB is started.

Jain Slee is started with the option “–b 95.128.80.84”  .

As you can see bellow with UDP  the NOTIFY is sent with this IP 95.128.80.84, so all is OK.

For the second one, VIA and CONTACT header are correctly created but the IP used to send the packet is not the correct one, it’s the default eth0 IP.

 

I’m doing test with JAIN-SLEE 2.6.0 FINAL on  linux centos with java :

java version "1.6.0_30"

Java(TM) SE Runtime Environment (build 1.6.0_30-b12)

Java HotSpot(TM) 64-Bit Server VM (build 20.5-b03, mixed mode)

 

Any idea  ?

 

Laurent

 

 

U 95.128.80.84:5060 -> 95.128.80.8:5060

NOTIFY sip:tes...@95.128.80.8 SIP/2.0.

Call-ID: 32f51c5c5e43c048...@95.128.80.84.

CSeq: 1 NOTIFY.

From: <sip:tes...@95.128.80.92>;tag=1332547046116.

To: <sip:tes...@95.128.80.8>.

Via: SIP/2.0/UDP 95.128.80.84:5060;branch=z9hG4bK-343533-1c720fb521ea117a3bdbf80b37f56847.

Max-Forwards: 70.

Contact: <sip:peopl...@95.128.80.84:5060>.

Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,INFO,REFER,NOTIFY.

Event: reboot.

Subscription-State: Subscription-State.

Content-Length: 0.

.

 

 

U 95.128.80.8:5060 -> 95.128.80.84:5060

SIP/2.0 407 Proxy Authentication Required.

Call-ID: 32f51c5c5e43c048...@95.128.80.84.

CSeq: 1 NOTIFY.

From: <sip:tes...@95.128.80.92>;tag=1332547046116.

To: <sip:tes...@95.128.80.8>;tag=a0440f545f39b2694d387b475a5f6bc9.4999.

Via: SIP/2.0/UDP 95.128.80.84:5060;branch=z9hG4bK-343533-1c720fb521ea117a3bdbf80b37f56847;rport=5060.

Proxy-Authenticate: Digest realm="95.128.80.92", nonce="T20PEE9tDeRaQNYcj9v4OWfPEq2uro8B".

Server: kamailio (3.2.1 (x86_64/linux)).

Content-Length: 0.

.

 

 

T 95.128.80.36:50451 -> 95.128.80.8:5060 [AP]

NOTIFY sip:tes...@95.128.80.8 SIP/2.0.

Call-ID: f87fd037e248adb8...@95.128.80.84.

CSeq: 1 NOTIFY.

From: <sip:tes...@95.128.80.92>;tag=1332547046195.

To: <sip:tes...@95.128.80.8>.

Via: SIP/2.0/TCP 95.128.80.84:5060;branch=z9hG4bK-343533-bc62cfde503b0c1f20fd76938d56faf3.

Max-Forwards: 70.

Contact: <sip:peopl...@95.128.80.84:5060;transport=tcp>.

Allow: INVITE,ACK,CANCEL,BYE,OPTIONS,INFO,REFER,NOTIFY.

Event: reboot.

Subscription-State: Subscription-State.

Content-Length: 0.

.

 

 

T 95.128.80.8:5060 -> 95.128.80.36:50451 [AP]

SIP/2.0 404 Not Found.

Call-ID: f87fd037e248adb8...@95.128.80.84.

CSeq: 1 NOTIFY.

From: <sip:tes...@95.128.80.92>;tag=1332547046195.

To: <sip:tes...@95.128.80.8>;tag=0e1310d981aa7d4b122a0b28dd2bdf63-42e1.

Via: SIP/2.0/TCP 95.128.80.84:5060;branch=z9hG4bK-343533-bc62cfde503b0c1f20fd76938d56faf3;rport=5045

Server: kamailio (3.2.1 (x86_64/linux)).

Content-Length: 0.

 

De : Laurent Schweizer [mailto:laurent....@peoplefone.com]
Envoyé : mercredi 7 mars 2012 11:05
À : mobicent...@googlegroups.com
Objet : [mobicents-public] Jain-slee with multiple IP

Tom Uijldert

unread,
Mar 27, 2012, 7:51:29 AM3/27/12
to mobicent...@googlegroups.com

Hi,

 

Maybe off-topic but related?:

What’s the situation on support of multiple addresses for the sip11-ra?

 

I get the impression that jsip can handle it and that both Ivelin and Jean have had a look at it but there’s no sign of it in the  code...

 

Or do I need to start a 2nd RA?

 

TIA,

    Tom.

Laurent Schweizer

unread,
Mar 27, 2012, 10:54:56 AM3/27/12
to mobicent...@googlegroups.com

Hi,

 

no idea if by default the SIP stack support multiple IP but when the SIP stack use the main IP to send the TCP SIP message,

when he get an answer on this socket he process them correctly.

 

Regards

 

Laurent

 

De : Tom Uijldert [mailto:tom.ui...@gmail.com]
Envoyé : mardi 27 mars 2012 13:51
À : mobicent...@googlegroups.com
Objet : RE: [mobicents-public] Jain-slee with multiple IP

Jean Deruelle

unread,
Mar 28, 2012, 5:51:11 AM3/28/12
to mobicent...@googlegroups.com
JAIN SIP can handle multiple IPs. It requires you to configure a listening point per IP Address/port. 
From http://docs.jboss.org/mobicents/jain-slee/2.5.0.FINAL/resources/sip11/user-guide/en-US/html_single/#ra_configuration it appears one SIP RA is tied to one listening point so to have multiple IPs one would need to deploy one SIP RA per couple IP Address, port.

Jean

Tom Uijldert

unread,
Mar 28, 2012, 6:27:56 AM3/28/12
to mobicent...@googlegroups.com

Thanks Jean, I thought as much.

Is there a how-to on how to deploy multiple RA’s of same type?

Vilius Panevėžys

unread,
Mar 28, 2012, 7:21:40 AM3/28/12
to mobicent...@googlegroups.com
Hi,
you need to configure multiple entities of the RA. IMO easiest way is
to use deploy-config:
http://docs.jboss.org/mobicents/jain-slee/2.5.0.FINAL/container/user-guide/en-US/html/management.html#management_persistent_deployer_deploy-config_extension

Also note that since Mobicents JSLEE 2.6.0 deploy-config.xml may be
outside a DU (unfortunately I didn't find an on-line link to the
updated container's user guide).


--
Vilius Panevėžys
Elitnet


On Wed, 28 Mar 2012 12:27:56 +0200
"Tom Uijldert" <tom.ui...@gmail.com> wrote:

> Thanks Jean, I thought as much.
>
> Is there a how-to on how to deploy multiple RA's of same type?
>
>
>
> From: mobicent...@googlegroups.com
> [mailto:mobicent...@googlegroups.com] On Behalf Of Jean Deruelle
> Sent: woensdag 28 maart 2012 11:51
> To: mobicent...@googlegroups.com
> Subject: Re: [mobicents-public] Jain-slee with multiple IP
>
>
>
> JAIN SIP can handle multiple IPs. It requires you to configure a
> listening point per IP Address/port.
>
> From
> http://docs.jboss.org/mobicents/jain-slee/2.5.0.FINAL/resources/sip11/user-g

> uide/en-US/html_single/#ra_configuration it appears one SIP RA is

Laurent Schweizer

unread,
Mar 28, 2012, 9:32:45 AM3/28/12
to mobicent...@googlegroups.com

HI,

I already try to set statically in the config of the RA the IP

javax.sip.IP_ADDRESS:java.lang.String=95.128.80.84

for UDP all is ok , but not for TCP.

Laurent

start LOG:

15:26:28,367 INFO  [DeploymentMBeanImpl] Installed EventTypeID[name=javax.sip.message.Request.NOTIFY,vendor=net.java.slee,version=1.2]

15:26:28,367 INFO  [DeploymentMBeanImpl] Installed EventTypeID[name=javax.sip.Dialog.INVITE,vendor=net.java.slee,version=1.2]

15:26:28,382 INFO  [DeploymentMBeanImpl] Installed ResourceAdaptorTypeID[name=JAIN SIP,vendor=javax.sip,version=1.2]

15:26:28,384 INFO  [DeploymentMBeanImpl] Installed ResourceAdaptorID[name=JainSipResourceAdaptor,vendor=net.java.slee.sip,version=1.2]

15:26:28,384 INFO  [DeploymentMBeanImpl] Installed DeployableUnitID[url=file:/usr/jboss-5.1.0.GA/server/default/deploy/sip11-ra-DU-2.6.0.FINAL.jar/]

15:26:28,718 INFO  [SipResourceAdaptor] RA entity named SipRA bound to port 5060

15:26:28,718 INFO  [ResourceManagement] Created Resource Adaptor Entity SipRA for ResourceAdaptorID[name=JainSipResourceAdaptor,vendor=net.java.slee.sip,version=1.2] Config Properties: [(javax.sip.IP_ADDRESS:java.lang.String=95.128.80.84),(javax.sip.TRANSPORT:java.lang.String=UDP,TCP),(org.mobicents.ha.javax.sip.BALANCERS:java.lang.String=),(org.mobicents.ha.javax.sip.LoadBalancerElector:java.lang.String=org.mobicents.ha.javax.sip.RoundRobinLoadBalancerElector),(javax.sip.PORT:java.lang.Integer=5060),(org.mobicents.ha.javax.sip.LoadBalancerHeartBeatingServiceClassName:java.lang.String=org.mobicents.ha.javax.sip.LoadBalancerHeartBeatingServiceImpl)]

15:26:28,969 INFO  [ResourceManagement] Activated RA Entity SipRA

15:26:29,219 INFO  [ResourceManagement] Bound link between RA Entity SipRA and Name SipRA

LOG, UDP is ok but TCP is  not sent with the configured IP in the STACK

  NOTIFY sip:tes...@95.128.80.8 SIP/2.0..Call-ID: 7c1c16c5c06a600fe016a5f2c9ae

  128.80.8>..Via: SIP/2.0/UDP 95.128.80.84:5060;branch=z9hG4bK-313437-c7945e636

  ANCEL,BYE,OPTIONS,INFO,REFER,NOTIFY..Event: reboot..Subscription-State: Subsc

  SIP/2.0 407 Proxy Authentication Required..Call-ID: 7c1c16c5c06a600fe016a5f2c

  95.128.80.8>;tag=a0440f545f39b2694d387b475a5f6bc9.2b74..Via: SIP/2.0/UDP 95.1

   realm="95.128.80.92", nonce="T3MSs09zEYfTwO0emWBOsXVc3pOgS7x0"..Server: kama

T 95.128.80.36:42082 -> 95.128.80.8:5060 [AP]

  NOTIFY sip:tes...@95.128.80.8 SIP/2.0..Call-ID: 8d206904951a25d55b8b0806c89c

  128.80.8>..Via: SIP/2.0/TCP 95.128.80.84:5060;branch=z9hG4bK-313437-a0c8621be

  : INVITE,ACK,CANCEL,BYE,OPTIONS,INFO,REFER,NOTIFY..Event: reboot..Subscriptio

T 95.128.80.8:5060 -> 95.128.80.36:42082 [AP]

  SIP/2.0 404 Not Found..Call-ID: 8d206904951a25d5...@95.128.80.84

  310d981aa7d4b122a0b28dd2bdf63-d07a..Via: SIP/2.0/TCP 95.128.80.84:5060;branch

   (x86_64/linux))..Content-Length: 0....

-----Message d'origine-----
De :
Vilius Panevėžys [mailto:vil...@elitnet.lt]
Envoyé : mercredi 28 mars 2012 13:22
À : mobicent...@googlegroups.com
Objet : Re: [mobicents-public] Jain-slee with multiple IP

Tom Uijldert

unread,
Mar 28, 2012, 11:01:58 AM3/28/12
to mobicent...@googlegroups.com
Hi,

Thanks for all the tips, got it working now: 2 sip-ra's bound to 2 NIC's. Works like a charm.

Any interest in a "how-to"?

Cheers,
Tom.

Jean Deruelle

unread,
Mar 28, 2012, 11:04:46 AM3/28/12
to mobicent...@googlegroups.com
Yes always :-), feel free to add a wiki page here 

Jean

Tom Uijldert

unread,
Apr 2, 2012, 6:47:13 AM4/2/12
to mobicent...@googlegroups.com

http://code.google.com/p/jain-slee/wiki/Start2SipResourceAdaptors

 

Hope this helps (and is accurate)...

 

Btw., I believe I ranted about this before but online access to any Mobicents info is very fragmented and unstructured.

I’m deeply impressed with any newbie that can make heads or tails out of what’s online...

 

There’s residual(?) stuff on java.net, more after move to google projects, the actual mobicents.org website, JBoss/RedHat entries and now more in google jain-slee, not to mention various blogs that also contain invaluable information...

 

Just saying...

/rant

 

Cheers,

    Tom.

 

From: mobicent...@googlegroups.com [mailto:mobicent...@googlegroups.com] On Behalf Of Jean Deruelle

Yes always :-), feel free to add a wiki page here 


Jean

On Wed, Mar 28, 2012 at 5:01 PM, Tom Uijldert <tom.ui...@gmail.com> wrote:

Hi,

Thanks for all the tips, got it working now: 2 sip-ra's bound to 2 NIC's. Works like a charm.

Any interest in a "how-to"?

Cheers,
   Tom.


> -----Original Message-----
> From: mobicent...@googlegroups.com [mailto:mobicents-
> pub...@googlegroups.com] On Behalf Of Vilius Panevežys
>
> Hi,
> you need to configure multiple entities of the RA. IMO easiest way is
> to use deploy-config:
> http://docs.jboss.org/mobicents/jain-slee/2.5.0.FINAL/container/user-
> guide/en-US/html/management.html#management_persistent_deployer_deploy-
> config_extension

[snip]

Vilius Panevėžys

unread,
Apr 2, 2012, 7:02:47 AM4/2/12
to mobicent...@googlegroups.com
Thanks for the initiative Tom!

I have two suggestions in case you or anyone else would be willing to
improve the post:
1. The How-To could easily be generalised to make it clear the
instructions work for any RA and that SIP RA is only used as an
example. I think that would help newcomers.

2. To configure multiple RA entities, a single RA DU is sufficient.
You can define multiple RA entities in the deploy-config.xml without
even touching resource-adaptor-jar.xml. That would simplify the process.


--
Vilius Panevėžys
Elitnet

Tom Uijldert

unread,
Apr 2, 2012, 8:04:37 AM4/2/12
to mobicent...@googlegroups.com
> 2. To configure multiple RA entities, a single RA DU is sufficient.
> You can define multiple RA entities in the deploy-config.xml without
> even touching resource-adaptor-jar.xml. That would simplify the
> process.

?? If I use the same "resource-adaptor-name" (by not touching the ...jar.xml), the SLEE starts to complain.

Vilius Panevėžys

unread,
Apr 2, 2012, 9:00:26 AM4/2/12
to mobicent...@googlegroups.com
Resource Adaptor name, vendor, version are used to define which of the
deployed RAs is used used to create a RA entity. It is normal to
reference the tuple multiple times.

Maybe I didn't understand the problem. I'm attaching a sample
deploy-config.xml that shows how I would try to do it, to make it
easier to discuss.


--
Vilius Panevėžys
Elitnet

multiple_ra_entity_deploy_config_sample.xml

Tom Uijldert

unread,
Apr 2, 2012, 9:54:40 AM4/2/12
to mobicent...@googlegroups.com
You're right, works fine.
Must've drawn the wrong conclusion in my tests, probably setting the IP-address in resource-adaptor-jar.xml was the problem.

Thanks, modified wiki accordingly.

Cheers,
Tom.

> -----Original Message-----
> From: mobicent...@googlegroups.com [mailto:mobicents-
> pub...@googlegroups.com] On Behalf Of Vilius Panevežys
>

Ivelin Ivanov

unread,
Apr 2, 2012, 10:35:43 AM4/2/12
to mobicent...@googlegroups.com
Thank you, Tom and Vilius. Created gcode ticket to include the example in the JSLEE User's Guide.

Eduardo Martins

unread,
Apr 2, 2012, 12:06:22 PM4/2/12
to mobicent...@googlegroups.com
Tom: the only thing needed to create a second RA entity is to edit the deploy-config.xml (the one in the mobicents-slee directory or the one inside the SIP RA du jar) and add:

<ra-entity resource-adaptor-id="ResourceAdaptorID[name=JainSipResourceAdaptor,vendor=net.java.slee.sip,version=1.2]" entity-name="SipRA2">
<properties>
<property name="javax.sip.PORT" type="java.lang.Integer" value="..." />
<property name="javax.sip.IP_ADDRESS" type="java.lang.String" value="..." />
<property name="javax.sip.TRANSPORT" type="java.lang.String" value="..." />
</properties>
<ra-link name="SipRA2" />
</ra-entity>  

No need for a second DU jar with hacked xml descriptors. If it doesn't work please open an issue.

Ivelin: The JAIN SLEE User Guide describes well the deploy-config.xml function and format, no need to include an example for a concrete deploy case and RA. It's useful as an article/tutorial, as done by Tom (but content in this case points to an not needed and quite complex workaround).

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

Tom Uijldert

unread,
Apr 3, 2012, 8:08:52 AM4/3/12
to mobicent...@googlegroups.com

Seems I was too hasty yesterday on declaring that Villius’ suggestion (and yours below) works.

 

I now consistently get an UnrecognizedActivityException on retrieving an aci  from the dialog in the factory.

 

As in:

dialog = sipprovider.getNewDialog(from, to);

sipAcif.getActivityContextInterface(dialog).attach(localobject);

 

using the recipe in the wiki.

Issue? Or is there still something wrong in the recipe?

 

TIA,

    Tom.

 

Stackdump:

javax.slee.UnrecognizedActivityException

                at org.mobicents.slee.resource.AbstractActivityContextInterfaceFactory.getACI(AbstractActivityContextInterfaceFactory.java:108)

                at net.java.slee.resource.sip.SipActivityContextInterfaceFactoryImpl.getActivityContextInterface(SipActivityContextInterfaceFactoryImpl.java)

                at net.sysmx.msml.MsmlSbb.channelSetUp(MsmlSbb.java:88)

                at net.sysmx.msml.MsmlSbb.msmlCreateConference(MsmlSbb.java:63)

                at net.sysmx.msml.MediaControlSbb.createConferenceAndCallId(MediaControlSbb.java:222)

                at net.sysmx.msml.MediaControlSbb.onCreateConference(MediaControlSbb.java:215)

                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:497)

                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 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)

 

From: mobicent...@googlegroups.com [mailto:mobicent...@googlegroups.com] On Behalf Of Eduardo Martins
Sent: maandag 2 april 2012 18:06
To: mobicent...@googlegroups.com
Subject: Re: [mobicents-public] Jain-slee with multiple IP

 

Tom: the only thing needed to create a second RA entity is to edit the deploy-config.xml (the one in the mobicents-slee directory or the one inside the SIP RA du jar) and add:

Eduardo Martins

unread,
Apr 3, 2012, 9:00:36 AM4/3/12
to mobicent...@googlegroups.com
That's with a single DU?

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



Tom Uijldert

unread,
Apr 3, 2012, 10:13:25 AM4/3/12
to mobicent...@googlegroups.com

Yes.

Eduardo Martins

unread,
Apr 3, 2012, 10:52:56 AM4/3/12
to mobicent...@googlegroups.com
And 2.6?

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



Tom Uijldert

unread,
Apr 4, 2012, 3:00:40 AM4/4/12
to mobicent...@googlegroups.com

Sorry, no, 2.4.0.FINAL.

Uijltje

unread,
Apr 5, 2012, 8:48:06 AM4/5/12
to mobicent...@googlegroups.com
http://code.google.com/p/mobicents/issues/detail?id=3174

Same problem under 2.6.0.FINAL.
And 2.6?

Yes.


Subject: Re: [mobicents-public] Jain-slee with multiple IP

 

Tom: the only thing needed to create a second RA entity is to edit the deploy-config.xml (the one in the mobicents-slee directory or the one inside the SIP RA du jar) and add:

 

<ra-entity resource-adaptor-id="ResourceAdaptorID[name=JainSipResourceAdaptor,vendor=net.java.slee.sip,version=1.2]" entity-name="SipRA2">

                      <properties>

                                  <property name="javax.sip.PORT" type="java.lang.Integer" value="..." />

                                  <property name="javax.sip.IP_ADDRESS" type="java.lang.String" value="..." />

                                  <property name="javax.sip.TRANSPORT" type="java.lang.String" value="..." />

                      </properties>

                      <ra-link name="SipRA2" />

          </ra-entity>  

 

No need for a second DU jar with hacked xml descriptors. If it doesn't work please open an issue.

 

Ivelin: The JAIN SLEE User Guide describes well the deploy-config.xml function and format, no need to include an example for a concrete deploy case and RA. It's useful as an article/tutorial, as done by Tom (but content in this case points to an not needed and quite complex workaround).


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

And 2.6?

Yes.


Subject: Re: [mobicents-public] Jain-slee with multiple IP

 

Tom: the only thing needed to create a second RA entity is to edit the deploy-config.xml (the one in the mobicents-slee directory or the one inside the SIP RA du jar) and add:

 

<ra-entity resource-adaptor-id="ResourceAdaptorID[name=JainSipResourceAdaptor,vendor=net.java.slee.sip,version=1.2]" entity-name="SipRA2">

                      <properties>

                                  <property name="javax.sip.PORT" type="java.lang.Integer" value="..." />

                                  <property name="javax.sip.IP_ADDRESS" type="java.lang.String" value="..." />

                                  <property name="javax.sip.TRANSPORT" type="java.lang.String" value="..." />

                      </properties>

                      <ra-link name="SipRA2" />

          </ra-entity>  

 

No need for a second DU jar with hacked xml descriptors. If it doesn't work please open an issue.

 

Ivelin: The JAIN SLEE User Guide describes well the deploy-config.xml function and format, no need to include an example for a concrete deploy case and RA. It's useful as an article/tutorial, as done by Tom (but content in this case points to an not needed and quite complex workaround).


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

And 2.6?

Yes.


Subject: Re: [mobicents-public] Jain-slee with multiple IP

 

Tom: the only thing needed to create a second RA entity is to edit the deploy-config.xml (the one in the mobicents-slee directory or the one inside the SIP RA du jar) and add:

 

<ra-entity resource-adaptor-id="ResourceAdaptorID[name=JainSipResourceAdaptor,vendor=net.java.slee.sip,version=1.2]" entity-name="SipRA2">

                      <properties>

                                  <property name="javax.sip.PORT" type="java.lang.Integer" value="..." />

                                  <property name="javax.sip.IP_ADDRESS" type="java.lang.String" value="..." />

                                  <property name="javax.sip.TRANSPORT" type="java.lang.String" value="..." />

                      </properties>

                      <ra-link name="SipRA2" />

          </ra-entity>  

 

No need for a second DU jar with hacked xml descriptors. If it doesn't work please open an issue.

 

Ivelin: The JAIN SLEE User Guide describes well the deploy-config.xml function and format, no need to include an example for a concrete deploy case and RA. It's useful as an article/tutorial, as done by Tom (but content in this case points to an not needed and quite complex workaround).


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

Eduardo Martins

unread,
Apr 18, 2012, 5:02:05 AM4/18/12
to mobicent...@googlegroups.com
Fixed on trunk.

-- Eduardo
Reply all
Reply to author
Forward
0 new messages