[SR-Users] Replication problems Registration Using t_replicate ().
Vitaliy Aleksandrov
vitalik.voip at gmail.com
Sat Jul 27 22:32:26 CEST 2013
What protection you are talking about ?
Do you have listen parameter for a virtual_ip at both master and backup
servers ?
Have you set ip_nonlocal_bind option ?
I've used this scheme without any problems and it worked great.
As I understand you need to add "sock_hdr_name" and "sock_flag"
parameters of the registrar module to set a header name where socket
information should be taken from and choose a flag that will be used by
registrar module to get the socket info from some header instead of real
socket.
> Dear Daniel,
>
>
> I'm using this way that you mentioned, but did not succeed. Must
> assign the virtual IP socket server parameter standby. But as this is
> virtual IP at the time of replication on the active server, is not
> allowed, because of a protection from "get_sock_hdr" to ./registrar/save.c
>
> It's possible to somehow assign this virtual IP socket parameter of
> the server standby?
>
> Thanks in advance
> Cheers
> Raphael
>
>
> 2013/7/25 Daniel-Constantin Mierla <miconda at gmail.com
> <mailto:miconda at gmail.com>>
>
> Hello,
>
> for the socket, there is already an embedded header, look at the
> readme for registrar module for sock header, or something like
> that. You just need to set that header to the value you want.
>
> Cheers,
> Daniel
>
>
> On 7/24/13 10:33 PM, Raphael Borges wrote:
>> Hello, anyone have any idea for this my problem? Need to somehow
>> override the value of the server socket standy by entering the
>> virtual IP in this field.
>>
>> Thanks in advance.
>>
>>
>> 2013/7/23 Raphael Borges <raphaelsilvaborges at gmail.com
>> <mailto:raphaelsilvaborges at gmail.com>>
>>
>> Daniel, I had another similar problem. Would you like a
>> procedure similar to the socket parameter. It is possible to
>> add a new header and assign the parameter socket in server
>> standby somehow?
>>
>> Thanks in advance.
>>
>>
>> 2013/7/23 Raphael Borges <raphaelsilvaborges at gmail.com
>> <mailto:raphaelsilvaborges at gmail.com>>
>>
>> Daniel, I had another similar problem. Would you like a
>> procedure similar to the socket parameter. It is possible
>> to add a new header and assign the parameter socket in
>> server standby somehow?
>>
>> Thanks in advance.
>> Raphael
>>
>>
>> 2013/7/22 Raphael Borges <raphaelsilvaborges at gmail.com
>> <mailto:raphaelsilvaborges at gmail.com>>
>>
>> Thanks Daniel, your help was very useful.
>>
>> With this I created a header by append_hf () before
>> calling the function
>> t_replicate and standby server retrieved the value of
>> this header and
>> assigns this value to the parameter avp
>> Example
>> $avp(s:rcv) = $hdr(IP-source);
>>
>> Best regards
>> Raphael
>>
>>
>>
>> Hello,
>>
>> the received is taken from an avp specified by
>> parameter received_avp of registrar module:
>>
>> http://kamailio.org/docs/modules/devel/modules/registrar.html#idp4433296
>>
>> You can carry the original details via a header
>> on the replicated REGISTER (using append_hf()),
>> then take the header on the second server and
>> store its value in the avp.
>>
>> Cheers,
>> Daniel
>>
>>
>> On 7/18/13 9:05 PM, Raphael Borges wrote:
>>> *Hello,*
>>>
>>>
>>> I have two servers in kamailio duality, I am
>>> using the function t_replicate () for
>>> replication log as below:
>>> Server 1 active
>>> t_replicate ("xxx.xxx.xxx.2", "5060");
>>> Server 2 reserves
>>> t_replicate ("xxx.xxx.xxx.1", "5060");
>>>
>>> But when the record is replicated to the standby
>>> server the parameter received is being filled
>>> with the active server IP, where the IP would
>>> Correro UAC, registry problems generating the
>>> backup server.
>>>
>>> Example
>>> Server 1 active xxx.xxx.xxx.1
>>>
>>> $ Kamctl ul show
>>> Domain :: location table = 512 records = 1 = 1
>>> max_slot
>>> AOR :: 4301
>>> Contact :: sip: 4301 at yyy.yyy.yyy.100
>>> <mailto:4301 at yyy.yyy.yyy.100>; transport = udp Q =
>>> Expires :: 4566
>>> Callid :: ccd0431c-6a4c-1231-0a94-7356c4f466e6
>>> CSeq :: 46740150
>>> User-agent :: stepo_LITE
>>> Received :: sip: yyy.yyy.yyy.100: 5060
>>> State :: CS_SYNC
>>> Flags :: 0
>>> CFLAG :: 0
>>> Socket :: udp: xxx.xxx.xxx.1: 5060
>>> Methods :: 8159
>>>
>>> Server 2 Reserve xxx.xxx.xxx.2
>>>
>>> $ Kamctl ul show
>>> Domain :: location table = 512 records = 1 = 1
>>> max_slot
>>> AOR :: 4301
>>> Contact :: sip: 4301 at yyy.yyy.yyy.100
>>> <mailto:4301 at yyy.yyy.yyy.100>; transport = udp Q =
>>> Expires :: 6665
>>> Callid :: ec7cfd42-6a7c-1231-0f94-7356c4f466e6
>>> CSeq :: 46750472
>>> User-agent :: stepo_LITE
>>> Received :: sip: xxx.xxx.xxx.1: 5060
>>> State :: CS_SYNC
>>> Flags :: 0
>>> CFLAG :: 0
>>> Socket :: udp: xxx.xxx.xxx.2: 5060
>>> Methods :: 8159
>>>
>>>
>>>
>>> Tkanks
>>>
>>> Raphael
>>>
>>>
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users at lists.sip-router.org <mailto:sr-users at lists.sip-router.org>
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>> --
>> Daniel-Constantin Mierla -http://www.asipto.com
>> http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda
>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) -
>> sr-users mailing list
>> sr-users at lists.sip-router.org
>> <mailto:sr-users at lists.sip-router.org>
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>>
>>
>>
>>
>>
>
> --
> Daniel-Constantin Mierla -http://www.asipto.com
> http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> -http://www.linkedin.com/in/miconda
>
>
>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20130727/7ad35777/attachment-0001.html>
More information about the sr-users
mailing list