[OpenSIPS-Users] unicode characters in dlg_list caller_contact field on re-invite

[Denis Lyubimov]

Hi all,

My network scheme is
softphone <-nat-external network-nat-> opensips <-local network-> sip
servers <-local network-> softphone
No b2b or topology_hiding modules are used.
Opensips versions I tried: 3.4.4-1 and 3.4.3-1.

I make a call from a phone behind nat to sip server via opensips, so I use
the fix_contact function from nat_traversal/fix_nated_contact from
nathelper for each request.
On the first invite I get "caller_contact":
"sip:1002@3.3.3.1:49682;transport=TCP;ob"
in "opensips-cli -x mi dlg_list".
If caller side makes re-invite, then i see this "caller_contact": "\u0001"
for nat_traversal,
and this "caller_contact": "sip:1002@3.3.3.1\ufffd" with nathelper in
dlg_list.
In that case dlg_send_sequential mi dialog function cannot be used cause
caller contact cannot be read.

Also if i make a re-invite from the caller side then the caller_contact
field in dlg_list starts looking normal.

Am I doing something wrong with fixing the nated contact field?
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] opensips 3.4 push notification

[Bogdan-Andrei Iancu]

Check with 
https://blog.opensips.org/2020/06/03/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-ii/


If setting $var(do_relay) to "false", be sure you do not hit any 
t_relay() later in your script.


Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
  https://www.siphub.com

On 20.02.2024 17:44, r...@rvgeerligs.nl wrote:

As far as I can see I do not do a relay in case 2:

lookup("location", "method-filtering");
$var(rc) = $retcode;
switch ($var(rc)) {
case 1:
    # we found at least 1 non-PN contact!
    $var(do_relay) = true;
    break;
case 2:
    # success, but all contacts are PN-enabled, so we're
    # sending PNs / awaiting re-registrations from them
*    $var(do_relay) = false;*
#     $var(do_relay) = true;

    break;
default:
    xlog("L_INFO", "DBG: no contacts found ($var(rc))\n");
    t_reply(404, "Not Found");
    exit;
}

Please advise again,

Regards,

Ronald


February 19, 2024 at 6:57 AM, "Bogdan-Andrei Iancu" 
> 
wrote:


Hi Ronald,

Do you check in the cfg the return code of the lookup() [1]
function for retcode (2)? you should not perform any SIP relay in
this case, as it will result into a loop.


[1]
https://opensips.org/html/docs/modules/3.4.x/registrar.html#func_lookup

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 16.02.2024 18:44, r...@rvgeerligs.nl wrote:

here you are.

February 16, 2024 at 1:37 PM, "Bogdan-Andrei Iancu"
mailto:bog...@opensips.org?to=%22Bogdan-Andrei%20Iancu%22%20%3Cbogdan%40opensips.org%3E>>
wrote:

Hi,

Could you share a pcap or trace so we can understand the
routing you have ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
   https://www.siphub.com

On 15.02.2024 22:24, r...@rvgeerligs.nl wrote:

Hi,
I kind of followed the article SIP Push Notification
with OpenSIPS 3.1 LTS [RFC 8599 support][Part II] as I
connot find anything related to opensips 3.4.x.
When I disable (commenting by #) modparam("registrar",
"pn_enable", true), the call actually works.
When I enable modparam("registrar", "pn_enable", true)
the call does not come through.
It gets rerouted internally to external ip address
after the authentication, second INVITE with answer to
nonce, and giving it a try.
Opensips keeps asking for Proxy Authentication
required which was allready accepted.
Anyone an idea?
Regards,
Ronald Geerligs

___
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

[OpenSIPS-Users] [Minor Release] OpenSIPS 3.4.4 and 3.2.17 Minor Releases

[Liviu Chircu]

Hi, everyone!

A new round of stable minor releases is now out: *3.4.4 *and *3.2.17*.  
As an exception, we've also pushed a final *3.3.10* release for *3.3*, 
which takes care of a couple regressions specific to *3.3.9 
*(specifically: in /tracer/ and /rest_client/).


Do make sure to schedule an update as soon as possible.

Full changelogs:

https://opensips.org/pub/opensips/3.4.4/ChangeLog
https://opensips.org/pub/opensips/3.3.10/ChangeLog
https://opensips.org/pub/opensips/3.2.17/ChangeLog 



Please enjoy!

OpenSIPS Team

On 29.01.2024 11:12, Liviu Chircu wrote:



The 3.4.4 and 3.2.17 OpenSIPS minor versions are scheduled for release 
on *Wednesday, Feb 21st*.


In preparation for the releases, starting *Wednesday, Feb 7th*, we 
will impose the usual *freeze* on any significant fixes (as 
complexity) on these stable branches, in order to ensure a /two-week 
safe window/ for testing.
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users