[OpenSIPS-Users] Script to get attr_avp from caller. How to do?

[Rodrigo Pimenta Carvalho]

Hi.


In my script I use to use AVP to store specific additional information for each 
registration.

When I have to get  the attr_avp (Module Registrar) from the callee, during a 
call, I use to codify:


branch_route[per_branch_ops] {

 myVariable = $(avp(attr)[$T_branch_idx]

}


What about the caller? I also need to get the attr_avp from caller, but I can't 
find a similar code in OpenSIPS documentation. How to do?


P.S.: I'm using the configuration:  modparam("usrloc", "db_mode", 0)


Any hint will be very helpful!

Best regards.


RODRIGO PIMENTA CARVALHO
Inatel Competence Center
Software
Ph: +55 35 3471 9200 RAMAL 979
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

[OpenSIPS-Users] codec_delete function issue

[John Nash]

I tried this function to delete "NSE" codec from SDP but it doesnt seem to
be working. Any consideration to make it work?...I am using rtpengine
module but calling it after calling codec_delete but this codec still
passes to other end.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] File name and rtpproxy_start_recording

[Hristo Donev]

You can use Asterisk for RTP proxy.
In this case you have file recording, transcoding and more other .

2016-06-15 15:44 GMT+03:00 Răzvan Crainea :

> Hi, Dragomir!
>
> There is no way to set a filename of the recording. It is auto-generated
> by rtpproxy.
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Solutionswww.opensips-solutions.com
>
> On 06/15/2016 10:38 AM, Dragomir Haralambiev wrote:
>
> Hello ,
> How to setup file name when using rtpproxy_start_recording?
> Best regards,
> Dragomir
>
>
> ___
> Users mailing 
> listUsers@lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] File name and rtpproxy_start_recording

[Răzvan Crainea]

Hi, Dragomir!

There is no way to set a filename of the recording. It is auto-generated 
by rtpproxy.


Best regards,

Răzvan Crainea
OpenSIPS Solutions
www.opensips-solutions.com

On 06/15/2016 10:38 AM, Dragomir Haralambiev wrote:

Hello ,
How to setup file name when using rtpproxy_start_recording?
Best regards,
Dragomir


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Userloc, Bin Interface, and Clusterer combo

[Bogdan-Andrei Iancu]

Hi Sammy,

Yes, you are correct . The current clustering support for usrloc covers 
only simple replication (usually for HA purposes). The next step is to 
achieve distribution and partitioning of registrations across the 
cluster (this is work in progress) and it will be available in the 2.3 
release.


Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 14.06.2016 15:21, SamyGo wrote:


Thanks Bogdan,

Will it be correct to say that usrloc replication is not the way to go 
if a mesh cluster of OpenSIPS, with every node knowing all the online 
subscribers anywhere, is to be created. !


Also, even if I do set ip_nonlocal_bind would each OpenSIPS getting 
this replicated registration start sending keepalives to that 
subscriber too?


Do you think a shared redis cluster for storing AoRs is more suitable 
for the task instead of this approach!


Thanks,
Sammy

On Jun 14, 2016 06:07, "Bogdan-Andrei Iancu" > wrote:


Hi Sammy,

The registration records are usually bound to an interface (the ip
and port the registration was received) - that interface will be
used all the time in the communication with the registered end point.

Now, when if server A receives the Registration on interface X,
and this is replicated to server B, this server B may not have the
X interface, but something else (an Y interface). So the
registration record will loose some information (the interface it
is bound to). This is the nature of the error message you see.
And yes, using the ip_nonlocal_bind options is the way to go.

Once replicated, the registration records are independent and they
do not depend on the what is happening with the original node
(where the registration was pushed from).

Regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 14.06.2016 09:35, SamyGo wrote:

Hi,
I've a cluster setup with userloc replication enabled for 3+
servers. As soon as a user register anywhere the other servers
which receive this replicated contact display these errors:

ERROR:usrloc:receive_ucontact_insert: non-local socket

ERROR:usrloc:receive_ucontact_insert: failed to process
replication event. dom: 'location', aor: '89...@1x.2xx.xx.xx
'
ERROR:usrloc:receive_binary_packet: failed to process a binary
packet!

The solution(kind of) for the same error has been discussed in
this thread:
http://lists.opensips.org/pipermail/users/2015-February/030910.html

The question here is, is setting /ip_nonlocal_bind /for this
userlocation replication a solution ? or should the replication
mechanism be modified to process the replications from other nodes !

Say even if this works, the next question is, what would happen
to the contacts from a server which is no longer active. The
Contacts disappear as soon as the clusterer node becomes inactive ?

Looking for some clarity on this topic.

Regards,
Sammy



___
Users mailing list
Users@lists.opensips.org 
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users