Re: [SR-Users] RLS question

[Klaus Darilion]

Am 26.01.2011 11:18, schrieb "Andrés S. García Ruiz":
> 
> Hi,
> 
> Rls-services document is working now!
> 
> Thanks a lot. The problem was the URI where the document was stored. It
> must contain the same userID and domain as in the To: header in the Sip
> subscribe message.

That's weird. IMO To should never be used for any comparison. IMO only
RURI of SUBSCRIBE is relevant.

regards
Klaus

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] SIP Recorder

[Iñaki Baz Castillo]

2011/1/26 Danny Dias :
> i mean
> signaling: A>PROXY>B (the normal procedure)
> At the same time, this must be done: (I'm not sure how to do this...the
> proxy could be out of this or not, not sure :()
> A ---INVITE---> SIP_PROXY ---INVITE---> SIP_RECORDER
> B ---INVITE---> SIP_RECORDER --INVITE--> SIP_RECORDER

Hi, is such SIP_PROXY an instance of Kamailio/SER?

-- 
Iñaki Baz Castillo


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Redundancy between 2 Kamailio servers

[Danny Dias]

Hello my friends,

I wonder if someone has done this before? i would like to implement 2
Kamailio servers with redundancy, something like the following:

SERVER_A is working as the primary sip proxy (virtual IP as the sip
signaling), if it fails, the other server (sleeping) should UP the virtual
IP and takes all the traffici guess there is many Linux implementations
thah can do this, but i would like to know if there is someone that has done
this before and hear some recomendations...

I've read some difficulty in the synchronisation of registrations because
Kamailio works best when it stores registrations in memory and registrations
are constantly changing - they expire and are renewed, as well as new ones
joining and old ones leaving. To make the failover solution function
seamlessly, it is necessary to synchronise the in-memory registrations
between the primary and the backup server . This can be done by forking a
copy of the registration request to the backup server, but there are some
practical problems in doing this, has anyone do something with this?


Thanks in advance!
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] SIP Recorder

[Danny Dias]

Hi Iñaki,


2011/1/27 Iñaki Baz Castillo 

> 2011/1/26 Danny Dias :
> > i mean
> > signaling: A>PROXY>B (the normal procedure)
> > At the same time, this must be done: (I'm not sure how to do this...the
> > proxy could be out of this or not, not sure :()
> > A ---INVITE---> SIP_PROXY ---INVITE---> SIP_RECORDER
> > B ---INVITE---> SIP_RECORDER --INVITE--> SIP_RECORDER
>

 B ---INVITE---> SIP_PROXY --INVITE--> SIP_RECORDER

Each peer must send an INVITE to the sip_recorder server, to stablish a
session with it...


> Hi, is such SIP_PROXY an instance of Kamailio/SER?
>

YEs, the proxys are Kamailio.


>
> --
> Iñaki Baz Castillo
> 
>



-- 
Ing. Danny Dias
www.DannTEL.net
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] SIP Recorder

[rabs]

Danny Dias  escribió:


Hi Iñaki,


2011/1/27 Iñaki Baz Castillo 


2011/1/26 Danny Dias :
> i mean
> signaling: A>PROXY>B (the normal procedure)
> At the same time, this must be done: (I'm not sure how to do this...the
> proxy could be out of this or not, not sure :()
> A ---INVITE---> SIP_PROXY ---INVITE---> SIP_RECORDER
> B ---INVITE---> SIP_RECORDER --INVITE--> SIP_RECORDER



 B ---INVITE---> SIP_PROXY --INVITE--> SIP_RECORDER

Each peer must send an INVITE to the sip_recorder server, to stablish a
session with it...


So ... if each UAC send an INVITE to the SIP-RECODER ... where is the  
problem? ... the RTP will be from UAC A to SIP-RECORDER .. that's all.  
Nothing strange should be done


Best regards


This message was sent using IMP, the Internet Messaging Program.


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] NAT Problem in Asterisk Realtime + Kamailio config

[andrzej . ciupek]

Hello

I have started to use configuration like:

http://kb.asipto.com/asterisk:realtime:kamailio-3.0.x-asterisk-1.6.2-astdb

I works fine, but I have problem with dealing with NAT.

kamctl ul show gives me:

 AOR:: andrzej_104
Contact::  
sip:andrzej_104@10.5.0.94:14368;rinstance=9c2b256a13210aa7 Q=

Expires:: 46
Callid:: ZDUwYzIzMDNiZTI3MjkyNmFmOWEyOTI2ODcyNjVmNDg.
Cseq:: 60
User-agent:: eyeBeam release 1102q stamp 51814
State:: CS_DIRTY
Flags:: 0
Cflag:: 0
Socket:: udp:77.xx.yyy.zzz:5060
Methods:: 5087
AOR:: andrzej_103
Contact:: sip:andrzej_103@10.5.0.165:5060 Q=
Expires:: 926
Callid:: 11631436-5060-1@10.5.0.165
Cseq:: 2257
User-agent:: Grandstream HT-502  V1.2A 1.0.3.10
State:: CS_SYNC
Flags:: 0
Cflag:: 0
Socket:: udp:77.xx.yyy.zzz:5060
Methods:: 6879

So when I have incomming call from Asterisk to Kamailio, Kamailio  
start to send call to LAN IP.

I have tried to use help from:
http://nil.uniza.sk/sip/nat-fw/configuring-nat-traversal-using-kamailio-31-and-rtpproxy-server

But I have never get:
Received:: and Cflag:: 192 it is always Cflag:: 0.
field in my kamctl ul show.

In my configuration Asterisk is Callweaver and is on the other server.  
I use rtpproxy-1.2.1 and kamailio-3.0.1 and mofified config from link:


http://kb.asipto.com/asterisk:realtime:kamailio-3.0.x-asterisk-1.6.2-astdb

Please help.



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio CFG file size ??

[marius zbihlei]

On 01/26/2011 10:31 PM, Jijo wrote:

Hi All,
is there any limitation on the size of kamailo.cfg file. When i tried 
to add few avp_subst, then the kamailio starts showing up the error 
out of package memory on receiving SIP message. If i remove those 
lines then everything works fine.. avp_subst is simple one.  Our 
kamailio cfg file is quite big..

Please let me know how to debug this issue?


Hello ,

You can increase the private memory size. The default value (4 MB afaik) 
might be to small. You should try with at least 10 MB. Check 
-DPKG_MEM_SIZE flag and set it to 10 when compiling. (Or alternatively 
edit config.h)


Cheers
Marius

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Klaus Darilion]

Am 27.01.2011 11:21, schrieb Danny Dias:
> Hello my friends,
> 
> I wonder if someone has done this before? i would like to implement 2
> Kamailio servers with redundancy, something like the following:
> 
> SERVER_A is working as the primary sip proxy (virtual IP as the sip
> signaling), if it fails, the other server (sleeping) should UP the virtual
> IP and takes all the traffici guess there is many Linux implementations
> thah can do this, but i would like to know if there is someone that has done
> this before and hear some recomendations...
> 
> I've read some difficulty in the synchronisation of registrations because
> Kamailio works best when it stores registrations in memory and registrations
> are constantly changing - they expire and are renewed, as well as new ones
> joining and old ones leaving. To make the failover solution function
> seamlessly, it is necessary to synchronise the in-memory registrations
> between the primary and the backup server . This can be done by forking a
> copy of the registration request to the backup server, but there are some
> practical problems in doing this, has anyone do something with this?

Yes - the problem with SIP based replication is that both proxies must
be running. This is a problem as Kamailio binds to the virtual IP at
start up - thus adding the virtual IP address to the backup server does
not make Backup-Kamailio listening to the new IP address - you would
have to restart the backup Kamailio.

I think most people either have a database (which is highly-available by
itself) which is used by both proxies, or every proxy has a local
database and the synchronization is on DB level (e.g. master-slave
replication, btw: does somebody know if usrloc DB queries are suitable
for master-master replication?)

regards
klaus

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] NAT Problem in Asterisk Realtime + Kamailio config

[Klaus Darilion]

Am 27.01.2011 12:42, schrieb andrzej.ciu...@asterisk.edu.pl:
> Hello
> 
> I have started to use configuration like:
> 
> http://kb.asipto.com/asterisk:realtime:kamailio-3.0.x-asterisk-1.6.2-astdb
> 
> I works fine, but I have problem with dealing with NAT.

Make sure to add

#!define WITH_NAT

to the config

regards
klaus


> 
> kamctl ul show gives me:
> 
>  AOR:: andrzej_104
> Contact::
> sip:andrzej_104@10.5.0.94:14368;rinstance=9c2b256a13210aa7 Q=
> Expires:: 46
> Callid::
> ZDUwYzIzMDNiZTI3MjkyNmFmOWEyOTI2ODcyNjVmNDg.
> Cseq:: 60
> User-agent:: eyeBeam release 1102q stamp 51814
> State:: CS_DIRTY
> Flags:: 0
> Cflag:: 0
> Socket:: udp:77.xx.yyy.zzz:5060
> Methods:: 5087
> AOR:: andrzej_103
> Contact:: sip:andrzej_103@10.5.0.165:5060 Q=
> Expires:: 926
> Callid:: 11631436-5060-1@10.5.0.165
> Cseq:: 2257
> User-agent:: Grandstream HT-502  V1.2A 1.0.3.10
> State:: CS_SYNC
> Flags:: 0
> Cflag:: 0
> Socket:: udp:77.xx.yyy.zzz:5060
> Methods:: 6879
> 
> So when I have incomming call from Asterisk to Kamailio, Kamailio start
> to send call to LAN IP.
> I have tried to use help from:
> http://nil.uniza.sk/sip/nat-fw/configuring-nat-traversal-using-kamailio-31-and-rtpproxy-server
> 
> 
> But I have never get:
> Received:: and Cflag:: 192 it is always Cflag:: 0.
> field in my kamctl ul show.
> 
> In my configuration Asterisk is Callweaver and is on the other server. I
> use rtpproxy-1.2.1 and kamailio-3.0.1 and mofified config from link:
> 
> http://kb.asipto.com/asterisk:realtime:kamailio-3.0.x-asterisk-1.6.2-astdb
> 
> Please help.
> 
> 
> 
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Alex Hermann]

On Thursday 27 January 2011, Klaus Darilion wrote:
> Am 27.01.2011 11:21, schrieb Danny Dias:
> > I've read some difficulty in the synchronisation of registrations because
> > Kamailio works best when it stores registrations in memory and
> > registrations are constantly changing - they expire and are renewed, as
> > well as new ones joining and old ones leaving. To make the failover
> > solution function seamlessly, it is necessary to synchronise the
> > in-memory registrations between the primary and the backup server . This
> > can be done by forking a copy of the registration request to the backup
> > server, but there are some practical problems in doing this, has anyone
> > do something with this?

What problems are you referring to? I use this for some years now without any 
problems.


> Yes - the problem with SIP based replication is that both proxies must
> be running. This is a problem as Kamailio binds to the virtual IP at
> start up - thus adding the virtual IP address to the backup server does
> not make Backup-Kamailio listening to the new IP address - you would
> have to restart the backup Kamailio.

Just bind kamailio to the HA IP on both servers and do REGISTER replication 
between the two (on SIP level). Then if the IP migrates to the other server, 
it will take over the rgistrar function with no loss of records. No restart 
needed.


> I think most people either have a database (which is highly-available by
> itself) which is used by both proxies, or every proxy has a local
> database and the synchronization is on DB level (e.g. master-slave
> replication, btw: does somebody know if usrloc DB queries are suitable
> for master-master replication?)

Last time i tried, they are not, at least not in writeback mode. One proxy is 
expiring records from the DB which the other proxy is trying to update. Maybe 
DB-only mode will work, but that has some practical (performcance) problems.
-- 
Greetings,

Alex Hermann


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] NAT Problem in Asterisk Realtime + Kamailio config

[andrzej . ciupek]

Hello

You Are Awesome :) it works.

Thank You.

Cytowanie Klaus Darilion :




Am 27.01.2011 12:42, schrieb andrzej.ciu...@asterisk.edu.pl:

Hello

I have started to use configuration like:

http://kb.asipto.com/asterisk:realtime:kamailio-3.0.x-asterisk-1.6.2-astdb

I works fine, but I have problem with dealing with NAT.


Make sure to add

#!define WITH_NAT

to the config

regards
klaus




kamctl ul show gives me:

 AOR:: andrzej_104
Contact::
sip:andrzej_104@10.5.0.94:14368;rinstance=9c2b256a13210aa7 Q=
Expires:: 46
Callid::
ZDUwYzIzMDNiZTI3MjkyNmFmOWEyOTI2ODcyNjVmNDg.
Cseq:: 60
User-agent:: eyeBeam release 1102q stamp 51814
State:: CS_DIRTY
Flags:: 0
Cflag:: 0
Socket:: udp:77.xx.yyy.zzz:5060
Methods:: 5087
AOR:: andrzej_103
Contact:: sip:andrzej_103@10.5.0.165:5060 Q=
Expires:: 926
Callid:: 11631436-5060-1@10.5.0.165
Cseq:: 2257
User-agent:: Grandstream HT-502  V1.2A 1.0.3.10
State:: CS_SYNC
Flags:: 0
Cflag:: 0
Socket:: udp:77.xx.yyy.zzz:5060
Methods:: 6879

So when I have incomming call from Asterisk to Kamailio, Kamailio start
to send call to LAN IP.
I have tried to use help from:
http://nil.uniza.sk/sip/nat-fw/configuring-nat-traversal-using-kamailio-31-and-rtpproxy-server


But I have never get:
Received:: and Cflag:: 192 it is always Cflag:: 0.
field in my kamctl ul show.

In my configuration Asterisk is Callweaver and is on the other server. I
use rtpproxy-1.2.1 and kamailio-3.0.1 and mofified config from link:

http://kb.asipto.com/asterisk:realtime:kamailio-3.0.x-asterisk-1.6.2-astdb

Please help.



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users







___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio CFG file size ??

[Jijo]

Package mem size used is 10MB

Regards,
Jijo

On Jan 27, 2011, at 6:44 AM, marius zbihlei  wrote:

> On 01/26/2011 10:31 PM, Jijo wrote:
>> Hi All,
>> is there any limitation on the size of kamailo.cfg file. When i tried to add 
>> few avp_subst, then the kamailio starts showing up the error out of package 
>> memory on receiving SIP message. If i remove those lines then everything 
>> works fine.. avp_subst is simple one.  Our kamailio cfg file is quite big..
>> Please let me know how to debug this issue?
>> 
> Hello ,
> 
> You can increase the private memory size. The default value (4 MB afaik) 
> might be to small. You should try with at least 10 MB. Check -DPKG_MEM_SIZE 
> flag and set it to 10 when compiling. (Or alternatively edit config.h)
> 
> Cheers
> Marius
> 
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Danny Dias]

Thanks Alex...

2011/1/27 Alex Hermann 

> On Thursday 27 January 2011, Klaus Darilion wrote:
> > Am 27.01.2011 11:21, schrieb Danny Dias:
> > > I've read some difficulty in the synchronisation of registrations
> because
> > > Kamailio works best when it stores registrations in memory and
> > > registrations are constantly changing - they expire and are renewed, as
> > > well as new ones joining and old ones leaving. To make the failover
> > > solution function seamlessly, it is necessary to synchronise the
> > > in-memory registrations between the primary and the backup server .
> This
> > > can be done by forking a copy of the registration request to the backup
> > > server, but there are some practical problems in doing this, has anyone
> > > do something with this?
>
> What problems are you referring to? I use this for some years now without
> any
> problems.
>
>
>
I checked for some problems here:

http://www.smartvox.co.uk/astfaq_ha_failover_ideas.htm



> > Yes - the problem with SIP based replication is that both proxies must
> > be running. This is a problem as Kamailio binds to the virtual IP at
> > start up - thus adding the virtual IP address to the backup server does
> > not make Backup-Kamailio listening to the new IP address - you would
> > have to restart the backup Kamailio.
>
> Just bind kamailio to the HA IP on both servers and do REGISTER replication
> between the two (on SIP level). Then if the IP migrates to the other
> server,
> it will take over the rgistrar function with no loss of records. No restart
> needed.
>

Do you mean that both Kamailio-1 and Kamailio-2 will be as primary server?
and the clients will register in the 2 machines? and also they will bind to
the ip of the HA? sorry my friend but i do not understand very well, i'm
quite new with redundant systems, could you please explain a little?


>
>
> > I think most people either have a database (which is highly-available by
> > itself) which is used by both proxies, or every proxy has a local
> > database and the synchronization is on DB level (e.g. master-slave
> > replication, btw: does somebody know if usrloc DB queries are suitable
> > for master-master replication?)
>
> Last time i tried, they are not, at least not in writeback mode. One proxy
> is
> expiring records from the DB which the other proxy is trying to update.
> Maybe
> DB-only mode will work, but that has some practical (performcance)
> problems.
> --
> Greetings,
>
> Alex Hermann
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>



-- 
Ing. Danny Dias
www.DannTEL.net
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Klaus Darilion]

Am 27.01.2011 13:05, schrieb Alex Hermann:
>> > Yes - the problem with SIP based replication is that both proxies must
>> > be running. This is a problem as Kamailio binds to the virtual IP at
>> > start up - thus adding the virtual IP address to the backup server does
>> > not make Backup-Kamailio listening to the new IP address - you would
>> > have to restart the backup Kamailio.
> Just bind kamailio to the HA IP on both servers and do REGISTER replication 
> between the two (on SIP level). Then if the IP migrates to the other server, 
> it will take over the rgistrar function with no loss of records. No restart 
> needed.

Is it possible to bind Kamailio to an IP address which is not active?
(e.g. start Kamailio on the backup server)

klaus

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Bernhard Suttner]

Try to set this option to bind to an non existing ip:

net.ipv4.ip_nonlocal_bind = 1

does work for SSH and thefore should also work with kamailio


-Ursprüngliche Nachricht-
Von: sr-users-boun...@lists.sip-router.org 
[mailto:sr-users-boun...@lists.sip-router.org] Im Auftrag von Klaus Darilion
Gesendet: Donnerstag, 27. Januar 2011 15:18
An: Alex Hermann
Cc: sr-users@lists.sip-router.org
Betreff: Re: [SR-Users] Redundancy between 2 Kamailio servers



Am 27.01.2011 13:05, schrieb Alex Hermann:
>> > Yes - the problem with SIP based replication is that both proxies must
>> > be running. This is a problem as Kamailio binds to the virtual IP at
>> > start up - thus adding the virtual IP address to the backup server does
>> > not make Backup-Kamailio listening to the new IP address - you would
>> > have to restart the backup Kamailio.
> Just bind kamailio to the HA IP on both servers and do REGISTER replication 
> between the two (on SIP level). Then if the IP migrates to the other server, 
> it will take over the rgistrar function with no loss of records. No restart 
> needed.

Is it possible to bind Kamailio to an IP address which is not active?
(e.g. start Kamailio on the backup server)

klaus

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[marius zbihlei]

On 01/27/2011 04:15 PM, Danny Dias wrote:

Thanks Alex...

2011/1/27 Alex Hermann mailto:a...@speakup.nl>>

On Thursday 27 January 2011, Klaus Darilion wrote:
> Am 27.01.2011 11:21, schrieb Danny Dias:
> > I've read some difficulty in the synchronisation of
registrations because
> > Kamailio works best when it stores registrations in memory and
> > registrations are constantly changing - they expire and are
renewed, as
> > well as new ones joining and old ones leaving. To make the
failover
> > solution function seamlessly, it is necessary to synchronise the
> > in-memory registrations between the primary and the backup
server . This
> > can be done by forking a copy of the registration request to
the backup
> > server, but there are some practical problems in doing this,
has anyone
> > do something with this?

What problems are you referring to? I use this for some years now
without any
problems.



I checked for some problems here:

http://www.smartvox.co.uk/astfaq_ha_failover_ideas.htm

> Yes - the problem with SIP based replication is that both
proxies must
> be running. This is a problem as Kamailio binds to the virtual IP at
> start up - thus adding the virtual IP address to the backup
server does
> not make Backup-Kamailio listening to the new IP address - you would
> have to restart the backup Kamailio.

Just bind kamailio to the HA IP on both servers and do REGISTER
replication
between the two (on SIP level). Then if the IP migrates to the
other server,
it will take over the rgistrar function with no loss of records.
No restart
needed.


Do you mean that both Kamailio-1 and Kamailio-2 will be as primary 
server? and the clients will register in the 2 machines? and also they 
will bind to the ip of the HA? sorry my friend but i do not understand 
very well, i'm quite new with redundant systems, could you please 
explain a little?


Hello

This week, I have added the p_usrloc module to K master branch, that 
allows partitioned user location service for Kamailio. This has the 
benefits of redundancy, failover and load balancing to user location 
service for K. Along with Henning Westerholt, we will also present some 
strategies for partioned user location to the upcoming FOSDEM meeting in 
Brussels.(more info here 
http://www.fosdem.org/2011/schedule/event/kamailiolocationservices)


You can check the README of the module (master branch 
modules_k/p_usrloc) for  some strategies for partitioned user location.


Marius







> I think most people either have a database (which is
highly-available by
> itself) which is used by both proxies, or every proxy has a local
> database and the synchronization is on DB level (e.g. master-slave
> replication, btw: does somebody know if usrloc DB queries are
suitable
> for master-master replication?)

Last time i tried, they are not, at least not in writeback mode.
One proxy is
expiring records from the DB which the other proxy is trying to
update. Maybe
DB-only mode will work, but that has some practical (performcance)
problems.
--
Greetings,

Alex Hermann


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing
list
sr-users@lists.sip-router.org 
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users




--
Ing. Danny Dias
www.DannTEL.net 


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Klaus Darilion]

Am 27.01.2011 13:05, schrieb Alex Hermann:
> On Thursday 27 January 2011, Klaus Darilion wrote:
>> > Am 27.01.2011 11:21, schrieb Danny Dias:
>>> > > I've read some difficulty in the synchronisation of registrations 
>>> > > because
>>> > > Kamailio works best when it stores registrations in memory and
>>> > > registrations are constantly changing - they expire and are renewed, as
>>> > > well as new ones joining and old ones leaving. To make the failover
>>> > > solution function seamlessly, it is necessary to synchronise the
>>> > > in-memory registrations between the primary and the backup server . This
>>> > > can be done by forking a copy of the registration request to the backup
>>> > > server, but there are some practical problems in doing this, has anyone
>>> > > do something with this?
> What problems are you referring to? I use this for some years now without any 
> problems.

Alex, do you also do NAT keep-alive from the proxies? If yes, are you
sending them from both servers at the same time?

regards
klaus

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] SIP Recorder

[Stefan Sayer]

o r...@dimension-virtual.com on 01/27/2011 01:13 PM:

Danny Dias  escribió:


Hi Iñaki,


2011/1/27 Iñaki Baz Castillo 


2011/1/26 Danny Dias :
> i mean
> signaling: A>PROXY>B (the normal procedure)
> At the same time, this must be done: (I'm not sure how to do 
this...the

> proxy could be out of this or not, not sure :()
> A ---INVITE---> SIP_PROXY ---INVITE---> SIP_RECORDER
> B ---INVITE---> SIP_RECORDER --INVITE--> SIP_RECORDER



 B ---INVITE---> SIP_PROXY --INVITE--> SIP_RECORDER

Each peer must send an INVITE to the sip_recorder server, to stablish a
session with it...


So ... if each UAC send an INVITE to the SIP-RECODER ... where is the 
problem? ... the RTP will be from UAC A to SIP-RECORDER .. that's all. 
no, I think what he wants is in the proxy to intercept the call which 
is from UAC A to UAC B, and place two additional calls to his 
SIP-RECORDER, which should transmit both signaling and RTP to the 
SIP-RECORDER.


To the OP: this is IMO not possible to do properly in a SIP proxy, 
even if its as flexible as s-r; while you can replicate the initial 
INVITE to the SIP-RECORDER, and even change the RTP media address in 
the SDP in order to make RTP go through rtpproxy, which might be 
modified to send a copy of the traffic to your SIP recorder, I really 
doubt that you can change the 200 to establish another INVITE to the 
SIP-RECORDER, let alone that you need to process the responses to the 
INVITEs to SIp-RECORDER, generate ACKs, handle in-dialog requests 
(e.g. session timer, hold etc etc).


For this stuff you need a SIP app server/B2BUA/media server, which has 
two dialogs on each side, and another two dialogs to the SIP-RECORDER. 
You might possibly be interested in SEMS' sbc module (shameless ad ;), 
latest development features RTP relay, you might be able to change it 
to create two more dialogs to SIP-RECORDER, using the original 
signaling, and relay the RTP also there. If that doesn't suit you, 
possibly you could have a look at implementing this using pjsip, 
freeswitch, asterisk (maybe in that order, depending on how 
transparent the thing in the middle should be). An alternative is to 
use s-r proxy and rtpproxy, and add some custom app server (again 
built possibly with sems/pjsip/freeswitch etc), which somehow gets 
signaling and RTP traffic from s-r/rtpproxy and sends them into two 
separate calls which are established to SIP-RECORDER. This type of 
stuff is usually implemented for LI (which hopefully we all don't 
like) and has further requirements regarding being transparent etc.


hth
Stefan


--
Stefan Sayer
VoIP Services Consulting and Development

Warschauer Str. 24
10243 Berlin

tel:+491621366449
sip:sa...@iptel.org
email/xmpp:stefan.sa...@gmail.com



___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Alex Hermann]

On Thursday 27 January 2011, Klaus Darilion wrote:
> Alex, do you also do NAT keep-alive from the proxies? If yes, are you
> sending them from both servers at the same time?

No, we require clients to sent nat-keepalives. It is much more efficient. In 
addition, the registrars are not directly accessible by clients, they go via 
load-balancers. Clients keep the NAT binding with the balancer, not the 
registrar.

-- 
Greetings,

Alex Hermann


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] ACC error | failed to insert into database

[alex pappas]

Hi all,

Hve anyone seen before the following error?

*Kamailio acc [acc.c:398]: failed to insert into database*

After a Kamailio restart it is ok but it start again afetr x time.



Thank you Alex
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Danny Dias]

Do you mean that both Kamailio-1 and Kamailio-2 will be as primary server?
and the clients will register in the 2 machines? and also they will bind to
the ip of the HA? sorry my friend but i do not understand very well, i'm
quite new with redundant systems, could you please explain a little please?


2011/1/27 Alex Hermann 

> On Thursday 27 January 2011, Klaus Darilion wrote:
> > Alex, do you also do NAT keep-alive from the proxies? If yes, are you
> > sending them from both servers at the same time?
>
> No, we require clients to sent nat-keepalives. It is much more efficient.
> In
> addition, the registrars are not directly accessible by clients, they go
> via
> load-balancers. Clients keep the NAT binding with the balancer, not the
> registrar.
>
> --
> Greetings,
>
> Alex Hermann
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Alex Hermann]

On Thursday 27 January 2011 17:18:22 Danny Dias wrote:
> Do you mean that both Kamailio-1 and Kamailio-2 will be as primary server?
> and the clients will register in the 2 machines? and also they will bind to
> the ip of the HA? sorry my friend but i do not understand very well, i'm
> quite new with redundant systems, could you please explain a little please?

Clients will register to the HA ip. The registrars are bound to the HA ip and 
to another IP on which the REGISTERs will be replicated between the 
registrars. Outbound request are forced through the right socket to the HA ip 
so they follow the  NAT binding of the client.

-- 
Alex Hermann

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Load_gw failed

[Thiago Maluf]

Hi Kamailio Users,

I'm trying to use LCR module in Kamailio 3.1.1 and I', having some
problems with this function (load_gws).

I'm my kamailio.cfg , I have this route:

# SEARCH DEST
route[NUMBER] {
xlog("L_ALERT", "NUMBER IS $rU \n");
if ($rU=~"^55211020[0-9]{4}$") { # IS MY USERS
route(LDAP_NUM2USER);
} else { # NOT IS MY USER
if (!load_gws(1,$rU)) {
xlog("L_ALERT", "LOAD LOCAL GW FAILED $rU  \n");
route(DSER);
return;
} else {
xlog("L_ALERT", "LOAD GW DEBUG $avp(i:709)\n");
} ;

if (!next_gw()) {
xlog("L_ALERT", "NEXT LOCAL GW FAILED\n");
sl_send_reply("503", "Service not available -
No gateways");
return;
};

setflag(29);
route(RELAY);
return;
};
};

When my call arrive to load_gws, I have this problem:

(2198) ERROR:  [action.c:1158]: runtime fixup failed for load_gws param 2
(2198) ERROR:  [action.c:1511]: run action error at:
/etc/kamailio/kamailio.cfg:472

I already saw the Kamailio Code and this error doesn't make sense.

Would somebody Help me with it?

Very thanks,
Thiago Maluf.



-- 

Thiago Maluf Resende
Tel: +55 21 9700-9113
e-mail: malu...@gmail.com

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Load_gw failed

[Alex Balashov]

On 01/27/2011 01:04 PM, Thiago Maluf wrote:


 if (!load_gws(1,$rU)) {


Pseudovariables like $rU have to be encapsulated in double-quotes, if 
they are supported as parameters to the function at all.


--
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web: http://www.evaristesys.com/

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Iñaki Baz Castillo]

2011/1/27 Klaus Darilion :
> Is it possible to bind Kamailio to an IP address which is not active?
> (e.g. start Kamailio on the backup server)

Yes, it depends on a sysctl option of the kernel (I don't remember the
name, sorry). With such option set you can make a server to listen in
a IP which doesn't exist in the server.

-- 
Iñaki Baz Castillo


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Iñaki Baz Castillo]

2011/1/27 Danny Dias :
> Do you mean that both Kamailio-1 and Kamailio-2 will be as primary server?
> and the clients will register in the 2 machines? and also they will bind to
> the ip of the HA? sorry my friend but i do not understand very well, i'm
> quite new with redundant systems, could you please explain a little please?

Two Kamailios in a HeartBeat cluster which manages the kamailio
service along with a virtual IP in which kamailios are supposed to
listen. Just one kamailio is running (HA manages them).

Regsitration can be done in a shared database with db_mode=3 (or 2) so
no locations are lost when HA stops the running instance of kamailio
(or the server is down) and starts kamailio in the other cluster node.

Another option without using realtime DB storage is replicating the
REGISTER from one Kamailio to the other (t_replicate method) but it
requires both kamailios being running at the same time (so
net.ipv4.ip_nonlocal_bind must be 1) and kamailios must NOT be managed
by HA. Also it requires some other considerations.

-- 
Iñaki Baz Castillo


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Danny Dias]

Thanks Iñaki,

2011/1/27 Iñaki Baz Castillo 

> 2011/1/27 Danny Dias :
> > Do you mean that both Kamailio-1 and Kamailio-2 will be as primary
> server?
> > and the clients will register in the 2 machines? and also they will bind
> to
> > the ip of the HA? sorry my friend but i do not understand very well, i'm
> > quite new with redundant systems, could you please explain a little
> please?
>
> Two Kamailios in a HeartBeat cluster which manages the kamailio
> service along with a virtual IP in which kamailios are supposed to
> listen. Just one kamailio is running (HA manages them).
>
>
So, the heartbeat cluster shall manage that both are ok and also check that
the virtual ip and the kamailio service in the primary server is OKif
something fails it will activate the virtual IP address and the kamailio
process in the other server? so this heartbeat cluster is installed in both
kamailio servers?

which HA software do you recommend?


> Regsitration can be done in a shared database with db_mode=3 (or 2) so
> no locations are lost when HA stops the running instance of kamailio
> (or the server is down) and starts kamailio in the other cluster node.
>
>
So, the database of the kamailios should be dedicated and externalised
server?


> Another option without using realtime DB storage is replicating the
> REGISTER from one Kamailio to the other (t_replicate method) but it
> requires both kamailios being running at the same time (so
> net.ipv4.ip_nonlocal_bind must be 1) and kamailios must NOT be managed
> by HA. Also it requires some other considerations.
>
> --
> Iñaki Baz Castillo
> 
>



-- 
Ing. Danny Dias
www.DannTEL.net
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Redundancy between 2 Kamailio servers

[Iñaki Baz Castillo]

2011/1/27 Danny Dias :
>> Two Kamailios in a HeartBeat cluster which manages the kamailio
>> service along with a virtual IP in which kamailios are supposed to
>> listen. Just one kamailio is running (HA manages them).
>>
>
> So, the heartbeat cluster shall manage that both are ok and also check that
> the virtual ip and the kamailio service in the primary server is OKif
> something fails it will activate the virtual IP address and the kamailio
> process in the other server? so this heartbeat cluster is installed in both
> kamailio servers?
> which HA software do you recommend?

As I said at the top of my previous mail: HeartBeat (as it is the only
I'm used to).


>> Regsitration can be done in a shared database with db_mode=3 (or 2) so
>> no locations are lost when HA stops the running instance of kamailio
>> (or the server is down) and starts kamailio in the other cluster node.
>>
>
> So, the database of the kamailios should be dedicated and externalised
> server?

Could be, or not. It doesn't matter too much.


-- 
Iñaki Baz Castillo


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users