[OpenSIPS-Users] OpenSIPs -> Asterisk

2021-03-24 Thread Social Boh 

Hello,

I'm looking for the best configuration for this setting:

OpenSIPs -> AsteriskPBX on a local server without public IP and with 
remote and local extensions.


Testing different configurations I can call from remote extension and 
access to media services configured on Asterisk.


I can make calls between local extensions but not between a local and a 
remote extension (signalling problem).


Any hint?

Thank you

--
---
I'm SoCIaL, MayBe


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

Re: [OpenSIPS-Users] mid_registrar lookup

2021-03-24 Thread volga629 via Users 

  
  
Hello Liviu,
May I send few screen shot of sip flow for this call ?

volga629.

On 3/24/21 8:57 AM, volga629 via Users
  wrote:


  
  Hello Liviu,
  We use topology hiding edge proxy for end point.
  Here are example 
  of contact header 
  
  Contact: 
  
  that call is inbound from PBX  to opensips and opensips forward to
  end point.
  
  
     
  if(is_method("INVITE|UPDATE|ACK|BYE|CANCEL|NOTIFY|INFO|OPTIONS")
  && $rU=~"%40") {
      xlog("[RELAY] [$rm] testing original
  [$ru]\n");
      route(CONTACT_LOOKUP);
      # We want exclude ACK rewrite toward Bria Push
  Server
      } else if(!isflagset("FLAG_BRIA_PUSH")) {
      xlog("[RELAY] [$rm] didn't match R-URI
  schema [$ru] correcting\n");
      $ru = "sip:" + $tU + "%40" + $td + "@" +
  $td;
      route(CONTACT_LOOKUP);
      }
  
  
  volga629 
  
  On 3/24/21 5:04 AM, Liviu Chircu
wrote:
  
  

On 24.03.2021 05:04, volga629 via
  Users wrote:

But then arrive the ACK and
  that where start the problems lookup  only find first
  contact and not second.
Hi Volga,
So you're doing a lookup() on the ACK
Request-URI?  Typically, the ACK R-URI will contain a
contact header, which is not meant to be searchable.  I'm
surprised you even get 1 result, I would expect such a
lookup() to return -1.
Can you explain what you are trying to
achieve?  Why not just route the ACK using loose_route(),
just like all other mid-dialog requests, and be done with
it?
  
-- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
  
  
  
  
  ___
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] Using sngrep for visualising encrypted SIP traffic

2021-03-24 Thread Ovidiu Sas 
Ciao Giovanni,

Those are great additions! I will integrate them into the blog, to be
more comprehensive.

Thanks,
Ovidiu

On Wed, Mar 24, 2021 at 10:31 AM Giovanni Maruzzelli  wrote:
>
> Ciao Ovidiu!
>
> We're often in parallel :)
>
> I found that if you create the transaction before creating (if any) the 
> dialog, then the ACK is traced even from HEP.
>
> What I would add to the super nice recipe is:
>
> - let's give a portrange to sngrep, so it will not analyze all traffic on all 
> ports, and will not trace the RTP packets too
> - let's give a limit on how many dialogs will keep in memory, default is 2000
> - let's do a rotation of dialogs, FIFO, so will keep the latest and discard 
> the older
> - let's try to understand fragmented udp too
> - let's use aliases for having names for our servers
> - let's not listen for HEP trace when we want (without duplicate display)
>
> - let's send both to a local sngrep and a remote homer
> - let's trace the 100 reply to INVITE too
>
> =
>
> let's put in .bashrc:
>
> alias sngrepa='sngrep -l 5000 -R -Ludp:127.0.0.1:9080 -v "OPTIONS\ sip" 
> "portrange 5050-5090 or (ip[6:2] & 0x1fff) != 0"'
> alias sngrepw='sngrep -l 5000 -R -v "OPTIONS\ sip" "portrange 9069-9071 or 
> (ip[6:2] & 0x1fff) != 0"'
>
> sngrepa will be used for "normal traffic", "sngrepw" for HEP trace
> the negation of OPTIONS would not be useful in sngrepw, but is there so the 
> command line understands when the BPF filter begins
>
> =
>
> opensips.cfg:
>
> modparam("tm", "auto_100trying", 0)
>
> modparam("proto_hep", "hep_id", "[hep_dst] 127.0.0.1:9070; transport=udp; 
> version=3")
> modparam("proto_hep", "hep_id", "[hep_dst2] 168.77.20.250:9060; 
> transport=udp; version=3")
> modparam("proto_hep", "homer5_on", 1)
> modparam("proto_hep", "homer5_delim", "#")
> modparam("proto_hep", "hep_capture_id", 100)
>
> modparam("tracer", "trace_on", 1)
> modparam("tracer", "trace_id", "[sngrep]uri=hep:hep_dst")
> modparam("tracer", "trace_id", "[homer]uri=hep:hep_dst2")
>
> route {
> t_newtran();
>
> if (!has_totag()) {
> if(is_method("INVITE") ) {
> trace("sngrep", "D");
> trace("homer", "D");
> send_reply(100, "Trying Hard");
> }
> } else {
> match_dialog();
> }
>
> if(is_method("MESSAGE|REGISTER|SUBSCRIBE|NOTIFY|PUBLISH") ) {
> trace("sngrep", "T");
> trace("homer", "T");
> }
> }
>
> local_route {
> if(is_method("NOTIFY") ) {
> trace("sngrep", "M");
> trace("homer", "M");
> }
> }
>
> onreply_route[local] {
> if(is_method("NOTIFY") ) {
> trace("sngrep", "M");
> trace("homer", "M");
> }
> }
>
> =
>
> beginning of the commonc .sngreprc:
>
> alias 168.77.20.201 FS1
> alias 168.77.20.202 FS2
> alias 168.77.20.203 FS3
> alias 67.153.242.46 LB
> alias 168.77.20.200 LB
> alias 194.143.78.61 GW1
> alias 94.43.18.61 GW2
> ...
> set background default
> ...
> set eep.listen on
> set eep.listen.version 3
> set eep.listen.address 127.0.0.1
> set eep.listen.port 9070
> set eep.listen.pass
> set eep.listen.uuid off
>
>
> -giovanni
>
>
> On Wed, Mar 24, 2021 at 2:43 AM Ovidiu Sas  wrote:
>>
>> Hello all,
>>
>> Here's a quick recipe to ease the troubleshooting of encrypted SIP traffic:
>> https://voipembedded.wordpress.com/2021/03/23/troubleshooting-opensips-encrypted-sip-traffic/
>>
>> Regards,
>> Ovidiu Sas
>>
>> --
>> VoIP Embedded, Inc.
>> http://www.voipembedded.com
>>
>> ___
>> Users mailing list
>> Users@lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> --
> Sincerely,
>
> Giovanni Maruzzelli
> OpenTelecom.IT
> cell: +39 347 266 56 18
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users



-- 
VoIP Embedded, Inc.
http://www.voipembedded.com

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

Re: [OpenSIPS-Users] Mid_Registrar outgoing_expire issue (Bug?)

2021-03-24 Thread Ricardo Martinez 
Guys.

I finally install all the latest changes….

So far so good… at least the initial problem for the outgoing_expire not
modified is fixed!!.

Thanks again for your help!



Ricardo



*De:* Liviu Chircu 
*Enviado el:* miércoles, 24 de marzo de 2021 11:09
*Para:* Ricardo Martinez ; OpenSIPS users mailling
list 
*Asunto:* Re: [OpenSIPS-Users] Mid_Registrar outgoing_expire issue (Bug?)



On 24.03.2021 16:05, Ricardo Martinez wrote:

So.. in order to make the update… is just fine to make it through git using
this?

git clone https://github.com/OpenSIPS/opensips.git -b 3.1 opensips-3.1

That will pull all the latest changes ??

Correct!  And, in the future, to fetch latest version, just do:

git pull --rebase

Of course, you have to compile & install the new binaries after each
update, using your usual technique.

-- 

Liviu Chircu

www.twitter.com/liviuchircu | www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Using sngrep for visualising encrypted SIP traffic

2021-03-24 Thread Giovanni Maruzzelli 
Ciao Ovidiu!

We're often in parallel :)

I found that if you create the transaction before creating (if any) the
dialog, then the ACK is traced even from HEP.

What I would add to the super nice recipe is:

- let's give a portrange to sngrep, so it will not analyze all traffic on
all ports, and will not trace the RTP packets too
- let's give a limit on how many dialogs will keep in memory, default is
2000
- let's do a rotation of dialogs, FIFO, so will keep the latest and discard
the older
- let's try to understand fragmented udp too
- let's use aliases for having names for our servers
- let's not listen for HEP trace when we want (without duplicate display)

- let's send both to a local sngrep and a remote homer
- let's trace the 100 reply to INVITE too

=

let's put in .bashrc:

alias sngrepa='sngrep -l 5000 -R -Ludp:127.0.0.1:9080 -v "OPTIONS\ sip"
"portrange 5050-5090 or (ip[6:2] & 0x1fff) != 0"'
alias sngrepw='sngrep -l 5000 -R -v "OPTIONS\ sip" "portrange 9069-9071 or
(ip[6:2] & 0x1fff) != 0"'

sngrepa will be used for "normal traffic", "sngrepw" for HEP trace
the negation of OPTIONS would not be useful in sngrepw, but is there so the
command line understands when the BPF filter begins

=

opensips.cfg:

modparam("tm", "auto_100trying", 0)

modparam("proto_hep", "hep_id", "[hep_dst] 127.0.0.1:9070; transport=udp;
version=3")
modparam("proto_hep", "hep_id", "[hep_dst2] 168.77.20.250:9060;
transport=udp; version=3")
modparam("proto_hep", "homer5_on", 1)
modparam("proto_hep", "homer5_delim", "#")
modparam("proto_hep", "hep_capture_id", 100)

modparam("tracer", "trace_on", 1)
modparam("tracer", "trace_id", "[sngrep]uri=hep:hep_dst")
modparam("tracer", "trace_id", "[homer]uri=hep:hep_dst2")

route {
t_newtran();

if (!has_totag()) {
if(is_method("INVITE") ) {
trace("sngrep", "D");
trace("homer", "D");
send_reply(100, "Trying Hard");
}
} else {
match_dialog();
}

if(is_method("MESSAGE|REGISTER|SUBSCRIBE|NOTIFY|PUBLISH") ) {
trace("sngrep", "T");
trace("homer", "T");
}
}

local_route {
if(is_method("NOTIFY") ) {
trace("sngrep", "M");
trace("homer", "M");
}
}

onreply_route[local] {
if(is_method("NOTIFY") ) {
trace("sngrep", "M");
trace("homer", "M");
}
}

=

beginning of the commonc .sngreprc:

alias 168.77.20.201 FS1
alias 168.77.20.202 FS2
alias 168.77.20.203 FS3
alias 67.153.242.46 LB
alias 168.77.20.200 LB
alias 194.143.78.61 GW1
alias 94.43.18.61 GW2
...
set background default
...
set eep.listen on
set eep.listen.version 3
set eep.listen.address 127.0.0.1
set eep.listen.port 9070
set eep.listen.pass
set eep.listen.uuid off


-giovanni


On Wed, Mar 24, 2021 at 2:43 AM Ovidiu Sas  wrote:

> Hello all,
>
> Here's a quick recipe to ease the troubleshooting of encrypted SIP traffic:
>
> https://voipembedded.wordpress.com/2021/03/23/troubleshooting-opensips-encrypted-sip-traffic/
>
> Regards,
> Ovidiu Sas
>
> --
> VoIP Embedded, Inc.
> http://www.voipembedded.com
>
> ___
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>


-- 
Sincerely,

Giovanni Maruzzelli
OpenTelecom.IT
cell: +39 347 266 56 18
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mid_Registrar outgoing_expire issue (Bug?)

2021-03-24 Thread Liviu Chircu 

On 24.03.2021 16:05, Ricardo Martinez wrote:


So.. in order to make the update… is just fine to make it through git 
using this?


git clone https://github.com/OpenSIPS/opensips.git 
-b 3.1 opensips-3.1


That will pull all the latest changes ??


Correct!  And, in the future, to fetch latest version, just do:

git pull --rebase

Of course, you have to compile & install the new binaries after each 
update, using your usual technique.


--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com

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

Re: [OpenSIPS-Users] Mid_Registrar outgoing_expire issue (Bug?)

2021-03-24 Thread Ricardo Martinez 
Liviu.

Thanks for that!… that seems to deal with the problem I’m facing….

I will try the update and let you know!



One more question….

I have installed opensips 3.1.0 from the link
*http://opensips.org/pub/opensips/latest*
, that’s why I have the
version I mention…

So.. in order to make the update… is just fine to make it through git using
this?:

git clone https://github.com/OpenSIPS/opensips.git -b 3.1 opensips-3.1



That will pull all the latest changes ??





Best Regards,

Ricardo





*De:* Liviu Chircu 
*Enviado el:* miércoles, 24 de marzo de 2021 10:26
*Para:* Ricardo Martinez ; OpenSIPS users mailling
list 
*Asunto:* Re: [OpenSIPS-Users] Mid_Registrar outgoing_expire issue (Bug?)



On 24.03.2021 15:18, Ricardo Martinez wrote:

I'm using

version: opensips 3.1.0 (x86_64/linux)

git revision: 58804282f

*git log 58804282fe5..HEAD modules/mid_registrar*

There are at least 8 mid-registrar fixes which you are missing, including:

--
commit a958382016e9825c4d2363157f29ea356b57d67a
Author: Liviu Chircu  
Date:   Fri Jan 15 18:17:42 2021 +0200

mid_registrar: Fix "Expires" edge-case in AoR throttling mode

This fixes a bug where the mid-registrar, in mode == 2, would not
correctly process REGISTER requests containing both:
* an ";expires=" Contact param
* an "Expires" header field

Specifically, the "Expires" header would incorrectly transit "as is",
without being changed.

Related to #2350
--

So my advice would be to pull latest 3.1 code and see if the "Expires"
header processing behavior improves.

Best regards,

-- 

Liviu Chircu

www.twitter.com/liviuchircu | www.opensips-solutions.com
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Re: [OpenSIPS-Users] Mid_Registrar outgoing_expire issue (Bug?)

2021-03-24 Thread Liviu Chircu 

On 24.03.2021 15:51, volga629 wrote:

Is in 3.1.2 all those fixes will be released ?


Yes, most of them have not made it into 3.1.1.

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com

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

Re: [OpenSIPS-Users] Mid_Registrar outgoing_expire issue (Bug?)

2021-03-24 Thread volga629 via Users 

  
  
Hello Liviu,
Is in 3.1.2 all those fixes  will be released ?

volga629 
  
On 3/24/21 10:26 AM, Liviu Chircu
  wrote:


  
  On 24.03.2021 15:18, Ricardo Martinez
wrote:
  
  
I'm using
version: opensips 3.1.0 (x86_64/linux)
git revision: 58804282f
  
  git log 58804282fe5..HEAD
modules/mid_registrar
  There are at least 8 mid-registrar fixes
  which you are missing, including:
  --
  commit a958382016e9825c4d2363157f29ea356b57d67a
  Author: Liviu Chircu 
  Date:   Fri Jan 15 18:17:42 2021 +0200
  
      mid_registrar: Fix "Expires" edge-case in AoR throttling
  mode
      
      This fixes a bug where the mid-registrar, in mode == 2,
  would not
      correctly process REGISTER requests containing both:
      * an ";expires=" Contact param
      * an "Expires" header field
      
      Specifically, the "Expires" header would incorrectly
  transit "as is",
      without being changed.
      
      Related to #2350
  --
  So my advice would be to pull latest 3.1
  code and see if the "Expires" header processing behavior
  improves.

  Best regards,
  
  -- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com
  
  
  ___
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] Mid_Registrar outgoing_expire issue (Bug?)

2021-03-24 Thread Liviu Chircu 

On 24.03.2021 15:18, Ricardo Martinez wrote:

I'm using
version: opensips 3.1.0 (x86_64/linux)
git revision: 58804282f


*git log 58804282fe5..HEAD modules/mid_registrar*

There are at least 8 mid-registrar fixes which you are missing, including:

--
commit a958382016e9825c4d2363157f29ea356b57d67a
Author: Liviu Chircu 
Date:   Fri Jan 15 18:17:42 2021 +0200

    mid_registrar: Fix "Expires" edge-case in AoR throttling mode

    This fixes a bug where the mid-registrar, in mode == 2, would not
    correctly process REGISTER requests containing both:
    * an ";expires=" Contact param
    * an "Expires" header field

    Specifically, the "Expires" header would incorrectly transit "as is",
    without being changed.

    Related to #2350
--

So my advice would be to pull latest 3.1 code and see if the "Expires" 
header processing behavior improves.


Best regards,

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com

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

Re: [OpenSIPS-Users] Mid_Registrar outgoing_expire issue (Bug?)

2021-03-24 Thread Ricardo Martinez 
Hi Volga.

Thanks for your answer.  Let me get this right.

In my case… if I receive a REGISTER to the mid_registrar like this:



REGISTER

Contact: 
;+sip.instance="";reg-id=1;expires=300

Expires: 300.



I apply the work around you mention…



Then I will get the outgoing_register to the PBX with the value modified?



Thanks!

Ricardo



*De:* volga629 
*Enviado el:* martes, 23 de marzo de 2021 23:37
*Para:* OpenSIPS users mailling list ; Ricardo
Martinez 
*Asunto:* Re: [OpenSIPS-Users] Mid_Registrar outgoing_expire issue (Bug?)



Hello Ricardo,
I noticed this issue too. My work around is

Where 7200 is  outgoing_expires in module params.





 if($(hdr("Expires"){s.int})!=7200) {
remove_hf("Expires");
append_hf("Expires: 7200\r\n");
}

volga629

On 3/23/21 12:46 PM, Ricardo Martinez wrote:

Hi.

I’m still unable to understand why the REGISTER is not using the

outgoing_expire.

First.   It's weird because according to the debug seems to change the

outgoing_expire to 3600 but when I check the outgoing REGISTER from the

MID_REGISTRAR still has the Expire Header = 300.

One thing I noticed is for the first REGISTER (the one the

outgoing_expires works) it changes the Expires header ok, this REGISTER

does not have contact expire header, but for the second REGISTER.. which

has Expire header and expire contact header.. seems to apply only the

"expire in the contact header"

(DBG:mid_registrar:replace_expires_ct_param).

These are the debugs...

Is this a bug? Or maybe I'm missing something?



1. Outgoing Expire  OK

INCOMING REGISTER

Contact:

sip:d2.596@192.168.0.34;rinstance=fa92ef51cba5543d;transport=tls>;+sip.ins

tance="

Expires: 300.



DBG:mid_registrar:mid_reg_save: saving to location...

DBG:mid_registrar:prepare_forward: from: '"Ricardo

Martinez"
;tag=ba489a60'

DBG:mid_registrar:prepare_forward: Call-ID:

'187541_mobile-rel120YzljYzJjNjcwOGJlYmYxOTU0MDM1NDBlMDJiZDQyNjg'

DBG:mid_registrar:prepare_forward: Contact:

'
;+sip.i

nstance=""'

DBG:mid_registrar:prepare_forward: registering ptr 0x7f6efc9c6b78 on

TMCB_REQUEST_FWDED ...

DBG:mid_registrar:prepare_forward: registering for TMCB_RESPONSE_FWDED,

mri=0x7f6efc9c6b78 ...

DBG:mid_registrar:prepare_forward: registering for TMCB_RESPONSE_DELETED,

mri=0x7f6efc9c6b78 ...

[187541_mobile-rel120YzljYzJjNjcwOGJlYmYxOTU0MDM1NDBlMDJiZDQyNjg]

[from_vex] [REGISTER sin totag][mid_registrar_save]: Retorna valor 1

[187541_mobile-rel120YzljYzJjNjcwOGJlYmYxOTU0MDM1NDBlMDJiZDQyNjg]

[from_vex] [REGISTER sin totag][mid_registrar_save]:

sip:d2@dom1.company.com:5061 salvado en tabla location

DBG:mid_registrar:mid_reg_req_fwded: msg expires: '300'

DBG:mid_registrar:calc_contact_expires: expires: 300

DBG:mid_registrar:calc_ob_contact_expires: outgoing expires: 1616511318

DBG:mid_registrar:overwrite_contact_expirations: ... contact:

'sip:d2.596@192.168.0.34;rinstance=fa92ef51cba5543d;transport=tls>;+sip.in

stance=""#015' Calculated

TIMEOUT = 1616511318 (3600)

DBG:mid_registrar:replace_expires_hf: ... Exp hdr: '300'

DBG:mid_registrar:mid_reg_req_fwded: trimming all Contact URIs into one...

DBG:mid_registrar:calc_contact_expires: expires: 300

DBG:mid_registrar:trim_to_single_contact: deleting Contact

'
;+sip.i

nstance=""'

DBG:mid_registrar:trim_to_single_contact: inserting new Contact

' '

DBG:mid_registrar:calc_contact_expires: expires: 300

DBG:mid_registrar:mid_reg_req_fwded: REQ FORWARDED TO

'sip:dom1.company.com:5061' (obp: sip:192.141.XXX.94:5060), expires=3600



OUTGOING REGISTER

Contact:  .

Expires: 3600.



2. Outgoing_expire fail

But for the Second REGISTER (from the PUSH SERVER)

INCOMING REGISTER

Contact:


;+sip.instance="";reg-id=1;expires=300

Expires: 300.



DBG:mid_registrar:mid_reg_save: saving to location...

DBG:mid_registrar:prepare_forward: from:

'
;tag=0f1c2a07'

DBG:mid_registrar:prepare_forward: Call-ID:

'y12mg-n8ka5jro_j-bhqn...@216.93.xxx.121'

DBG:mid_registrar:prepare_forward: Contact:

'
;+sip.instance="";reg-id=1;expires=300'

DBG:mid_registrar:prepare_forward: registering ptr 0x7f6efc9b60d0 on

TMCB_REQUEST_FWDED ...

DBG:mid_registrar:prepare_forward: registering for TMCB_RESPONSE_FWDED,

mri=0x7f6efc9b60d0 ...

DBG:mid_registrar:prepare_forward: registering for TMCB_RESPONSE_DELETED,

mri=0x7f6efc9b60d0 ...

[y12mg-n8ka5jro_j-bhqn...@216.93.xxx.121] [from_vex] [REGISTER sin

totag][mid_registrar_save]: Retorna valor 1

[y12mg-n8ka5jro_j-bhqn...@216.93.xxx.121] [from_vex] [REGISTER sin

totag][mid_registrar_save]: sip:d2@dom1.company.com:5061 salvado en

tabla location

DBG:mid_registrar:mid_reg_req_fwded: msg expires: '300'

DBG:mid_registrar:calc_contact_expires: expires: 300

DBG:mid_registrar:calc_ob_contact_expires: outgoing expires: 1616511408

DBG:mid_registrar:overwrite_contact_expirations: ... contact:

Re: [OpenSIPS-Users] Mid_Registrar outgoing_expire issue (Bug?)

2021-03-24 Thread Ricardo Martinez 
Hi Liviu.
I'm using
version: opensips 3.1.0 (x86_64/linux)
git revision: 58804282f

Ricardo

-Mensaje original-
De: Liviu Chircu 
Enviado el: miércoles, 24 de marzo de 2021 4:59
Para: OpenSIPS users mailling list ; Ricardo
Martinez 
Asunto: Re: [OpenSIPS-Users] Mid_Registrar outgoing_expire issue (Bug?)

On 23.03.2021 17:46, Ricardo Martinez wrote:
> Hi.
> I’m still unable to understand why the REGISTER is not using the
> outgoing_expire.

Hi,

What version are you using?  `opensips -V`

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com

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

Re: [OpenSIPS-Users] mid_registrar lookup

2021-03-24 Thread volga629 via Users 

  
  
Hello Liviu,
We use topology hiding edge proxy for end point.
Here are example 
of contact header 

Contact: 

that call is inbound from PBX  to opensips and opensips forward to
end point.


   
if(is_method("INVITE|UPDATE|ACK|BYE|CANCEL|NOTIFY|INFO|OPTIONS")
&& $rU=~"%40") {
    xlog("[RELAY] [$rm] testing original
[$ru]\n");
    route(CONTACT_LOOKUP);
    # We want exclude ACK rewrite toward Bria Push
Server
    } else if(!isflagset("FLAG_BRIA_PUSH")) {
    xlog("[RELAY] [$rm] didn't match R-URI
schema [$ru] correcting\n");
    $ru = "sip:" + $tU + "%40" + $td + "@" +
$td;
    route(CONTACT_LOOKUP);
    }


volga629 

On 3/24/21 5:04 AM, Liviu Chircu wrote:


  
  On 24.03.2021 05:04, volga629 via
Users wrote:
  
  But then arrive the ACK and
that where start the problems lookup  only find first
contact and not second.
  Hi Volga,
  So you're doing a lookup() on the ACK
  Request-URI?  Typically, the ACK R-URI will contain a contact
  header, which is not meant to be searchable.  I'm surprised
  you even get 1 result, I would expect such a lookup() to
  return -1.
  Can you explain what you are trying to
  achieve?  Why not just route the ACK using loose_route(), just
  like all other mid-dialog requests, and be done with it?

  -- 
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


  


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

Re: [OpenSIPS-Users] mid_registrar lookup

2021-03-24 Thread Liviu Chircu 

On 24.03.2021 05:04, volga629 via Users wrote:
But then arrive the ACK and that where start the problems lookup  only 
find first contact and not second.


Hi Volga,

So you're doing a lookup() on the ACK Request-URI?  Typically, the ACK 
R-URI will contain a contact header, which is not meant to be 
searchable.  I'm surprised you even get 1 result, I would expect such a 
lookup() to return -1.


Can you explain what you are trying to achieve?  Why not just route the 
ACK using loose_route(), just like all other mid-dialog requests, and be 
done with it?


--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com

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

Re: [OpenSIPS-Users] Mid_Registrar outgoing_expire issue (Bug?)

2021-03-24 Thread Liviu Chircu 

On 23.03.2021 17:46, Ricardo Martinez wrote:

Hi.
I’m still unable to understand why the REGISTER is not using the
outgoing_expire.


Hi,

What version are you using?  `opensips -V`

--
Liviu Chircu
www.twitter.com/liviuchircu | www.opensips-solutions.com


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