Re: [OpenSIPS-Users] acc extra_fields param

Hi Pasan, This is for OpenSIPS 2.3: https://github.com/OpenSIPS/opensips/commit/42cba2c0de9cb07e31c055bc82514c14735bd2e8 Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam O

Re: [OpenSIPS-Users] acc extra_fields param

Thanks Bogdan, I found it. I'll let you know how it goes. On Wednesday, 14 February 2018, 14:12, Bogdan-Andrei Iancu wrote: Hi Pasan, This is for OpenSIPS 2.3:     https://github.com/OpenSIPS/opensips/commit/42cba2c0de9cb07e31c055bc82514c14735bd2e8 Regards, Bogdan-Andrei Ianc

Re: [OpenSIPS-Users] warning on postgres data type

Hi Pasan, But from the DB point of view, what data type does your procedure return ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com OpenSIPS Summit 2018 http://www.opensips.org/events/Summit-2018Amsterdam On 02/14/2018 08:51 AM, Pasan Meemadu

Re: [OpenSIPS-Users] Port changes

Hi Schneur, I see at initial INVITE you have the same issue - the contact advertises the 34063 port, but the source IP is 1090; and you do fix_nated_contact(). So, based on the initial contact, you learned that the caller device is behind a NAT (or with a bogus ALG). The idea is to remember t

Re: [OpenSIPS-Users] migrating to opensips 2.3 from 2.2

Hi Brian, Are you sure you are using the right opensipdbctl version ? The one provided by the 2.3 installation has the right info text - see: https://github.com/OpenSIPS/opensips/blob/2.3/scripts/opensipsdbctl#L309 Maybe due a version mixing, you use the opensipsdbctl from the 2.2 version (th

Re: [OpenSIPS-Users] warning on postgres data type

Hi Bogdan, It returns the postgres data type uuid. I put that in acc extra field to keep track calls. If I use following, I'm not getting the warning anymore. avp_db_query("SELECT uuid_generate_v1mc()::varchar","$avp(callid)") On Wednesday, 14 February 2018, 14:55, Bogdan-Andrei Iancu

Re: [OpenSIPS-Users] warning on postgres data type

Hi, OK, the uuid is custom data type (specific to postgres ??), so doing the cast at DB level is the proper way to address the warning. But, why not using the call-Id + from_tag as uuid for the calls ? Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutio

Re: [OpenSIPS-Users] Port changes

You're right, I noticed that the port was wrong at the first invite, but I didn't realize that it was fixed, I thought it left it untouched, I just checked again and you're correct it did fix it. Is there any downside (besides for obvious performance reasons) to call fix_nated_contact() on each p

[OpenSIPS-Users] Modules in apt.opensips.org

I was hoping to simplify my installation by only using apt-get to install binaries on a Debian box, but I cannot see an apt package for the module cachedb_couchbase in the apt.opensips.org repository. Does this mean I have to make opensips from source if I want to use this module? John Quick Smar

Re: [OpenSIPS-Users] Modules in apt.opensips.org

Hi John, Yes, it would appear so, currently: root@localhost:~# apt-cache search opensips | grep mongo opensips-mongodb-module - Interface module to interact with a MongoDB server root@localhost:~# apt-cache search opensips | grep cassa root@localhost:~# apt-cache search opensips | grep redis ope

[OpenSIPS-Users] Proto_hep listeners

Hi, I’m trying to upgrade from 1.11 to 2.3.3. We use the siptrace module to replicate messages via HEP, so I had to load in the proto_hep module as well. On startup, I’m getting the following errors: ERROR:proto_hep:mod_init: No HEP listener defined, neither TCP nor UDP! ERROR:core:init_mod: fa

[OpenSIPS-Users] Dialog module requires clusterer

Hi, I’m trying to upgrade from 1.11 to 2.3.3. We use the dialog module but we do not use dialog or profile replication. When I try to run my server it fails with the following error: WARNING:core:solve_module_dependencies: module dialog depends on module clusterer, but it was not loaded! ERROR

[OpenSIPS-Users] Avpops and db_virtual modules

Hi, Sorry for all of the emails! I have found one more issue while trying to upgrade from OpenSIPS 1.11 to 2.x. We use the db_virtual module in front of our redundant Postgres DB instances to facilitate failover between the DBs. We also use the avpops module to perform raw queries against the D

Re: [OpenSIPS-Users] warning on postgres data type

Hi Bogdan, Thanks for the reply. I'll see if I can use call-Id + from_tag for it. But at the moment we are using uuid version 1 for this to make sure we get more accurate uniqueness. On Wednesday, 14 February 2018, 15:54, Bogdan-Andrei Iancu wrote: Hi, OK, the uuid is custom d

Re: [OpenSIPS-Users] acc extra_fields param

Hi Bogdan, your fix worked :). Thanks for that. it converts the int properly now. On Wednesday, 14 February 2018, 14:12, Bogdan-Andrei Iancu wrote: Hi Pasan, This is for OpenSIPS 2.3:     https://github.com/OpenSIPS/opensips/commit/42cba2c0de9cb07e31c055bc82514c14735bd2e8 Regar

Re: [OpenSIPS-Users] Proto_hep listeners

Hi Ben, Even if you do not actually act a HEP traffic receiver (so no need for listening), you *need* to define a HEP listener in the config file. This constrain comes from the generic TCP stack in OpenSIPS (which also re-used to implement the HEP protocol) - this stack work only in a symmet

Re: [OpenSIPS-Users] Dialog module requires clusterer

Hi Ben, Do you have any of the following module parameters set in your cfg : * accept_replicated_dialogs * replicate_dialogs_to * accept_replicated_profiles * replicate_profiles_to Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developer http://www.opensips-solutions.com O

Re: [OpenSIPS-Users] Avpops and db_virtual modules

Ben, emails are welcome, as they provide valuable feedback for us ;) Do you say that avpops + db_virtual combination was working in 1.11 ? I remember there were some fixes couple of months ago in regards to how the capabilities do propagate via the virtual module. Regards, Bogdan-Andrei Ianc

Re: [OpenSIPS-Users] Port changes

Hi Schneur, It is not 100% correct, as a sip message may come from a another SIP server and in this case the Contact (belong to the end point) should not be re-written with the IP OPenSIPS sees as source (which is the other SIP server). Shortly said, you can force the re-write as time as you k