Re: [OpenSIPS-Users] invalid contact wss

2023-02-04 Thread Robert Dyck
I forgot to mention that nat_uac_test should use at least flag 2. This insures 
that usrloc contains "Received".

On Thursday, January 19, 2023 10:27:47 A.M. PST nutxase via Users wrote:
> Hi guys
> 
> So i notice when i register a WSS client to opensips the contact shows
> something like Contact": "sip:62dntqm1@rwtjcrhyne3j.invalid;transport=wss",
> 
> which causes inbound calls to not route and show 476 unresolvable
> destination.
> 
> any tips of where to look here?
> 
> Sent with [Proton Mail](https://proton.me/) secure email.





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


Re: [OpenSIPS-Users] invalid contact wss

2023-02-04 Thread Robert Dyck
Do you have opensips-cli setup? If so, do "mi ul_dump". Look for your 
"invalid" contact.
Your should have a line like "Received": "sip:1.2.3.4:60310;transport=wss",
The IP address should be routable.

On Thursday, January 19, 2023 10:27:47 A.M. PST nutxase via Users wrote:
> Hi guys
> 
> So i notice when i register a WSS client to opensips the contact shows
> something like Contact": "sip:62dntqm1@rwtjcrhyne3j.invalid;transport=wss",
> 
> which causes inbound calls to not route and show 476 unresolvable
> destination.
> 
> any tips of where to look here?
> 
> Sent with [Proton Mail](https://proton.me/) secure email.





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


Re: [OpenSIPS-Users] invalid contact wss

2023-02-04 Thread HS
Nutxcase,

With ref to invalid wss contact - can you confirm Opensips version please?

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


Re: [OpenSIPS-Users] LATE SDP Script on Opensips 3.3

2023-02-04 Thread HS
Hi,

It seems I have fixed issue number 2. But issue 1 is still there (I call a
browser (Firefox or chrome), the call is rejected and I get the error:
"Failed to get local SDP".). Can someone please confirm if NAT/IP detection
works on Opensips 3.3.3? I have tested the exact same config and it works
fine on 3.0.5.

I have df7jal23ls0d.invalid in the SDP on Opensips 3.3.3.

Best wishes.

On Thu, Jan 26, 2023 at 10:44 PM HS  wrote:

> Hi all,
>
> Here's is a link to the log of 2 calls. First part is a call that has
> one-way audio and the second is a call that has great bi-directional audio.
> https://pastebin.com/ggUFUmsp
>
> Appreciate if someone can identify if opensips config is ok pls, or
> suggestions on how to fix pls.
>
> On Sat, Jan 21, 2023 at 3:34 PM HS  wrote:
>
>> Hi all.
>>
>> I am trying to setup an Opensips 3.3 instance on AWS and have rtpengine
>> installed. I am using a modified version of the script here:
>>
>> http://www.opensips.org/pub/docs/tutorials/websockets/opensips-late.cfg
>>
>> Two issues.
>> 1. When I call a browser (Firefox or chrome), the call is rejected and I
>> get the error: "Failed to get local SDP".
>> 2. One-way audio in specific circumstances - log below. Investigating
>> further I found that if I use "t_on_reply("handle_nat");" the calls go
>> through fine. However, if I use "t_on_branch("handle_nat");" I see
>> behaviour below.
>>
>> Thanks in advance.
>>
>> I am using 2 UA - Microsip and Linphone. When I call from Microsip
>> (Laptop) to Linphone (Android) I have great audio and the logs show this:
>>
>> Jan 20 16:11:06 ip-172-31-13-220 rtpengine[42387]: INFO:
>> [f75f1e374747457ca016e3a3a62ff4b3]: [control] Received command 'answer'
>> from 127.0.0.1:33919
>> Jan 20 16:11:06 ip-172-31-13-220 rtpengine[42387]: INFO:
>> [f75f1e374747457ca016e3a3a62ff4b3]: [control] Replying to 'answer' from
>> 127.0.0.1:33919 (elapsed time 0.000268 sec)
>> Jan 20 16:11:06 ip-172-31-13-220 /usr/sbin/opensips[79601]: incoming reply
>> Jan 20 16:11:07 ip-172-31-13-220 dhclient[451]: DHCPREQUEST for
>> 172.31.13.220 on ens5 to 172.31.0.1 port 67
>> Jan 20 16:11:07 ip-172-31-13-220 dhclient[451]: DHCPACK of 172.31.13.220
>> from 172.31.0.1
>> Jan 20 16:11:07 ip-172-31-13-220 dhclient[451]: bound to 172.31.13.220 --
>> renewal in 1607 seconds.
>> Jan 20 16:11:10 ip-172-31-13-220 rtpengine[42387]: INFO:
>> [f75f1e374747457ca016e3a3a62ff4b3 port 13215]: [core] Confirmed peer
>> address as My.Pub.IP.Add:4011
>> Jan 20 16:11:21 ip-172-31-13-220 rtpengine[42387]: INFO:
>> [f75f1e374747457ca016e3a3a62ff4b3]: [control] Received command 'delete'
>> from 127.0.0.1:33919
>> Jan 20 16:11:21 ip-172-31-13-220 rtpengine[42387]: INFO:
>> [f75f1e374747457ca016e3a3a62ff4b3]: [core] Scheduling deletion of call
>> branch 'bGUEC~8' (via-branch '') in 30 seconds
>> Jan 20 16:11:21 ip-172-31-13-220 rtpengine[42387]: INFO:
>> [f75f1e374747457ca016e3a3a62ff4b3]: [core] Scheduling deletion of call
>> branch '33a25bec39c742678ce74836e0ff40d1' (via-branch '') in 30 seconds
>> Jan 20 16:11:21 ip-172-31-13-220 rtpengine[42387]: INFO:
>> [f75f1e374747457ca016e3a3a62ff4b3]: [core] Scheduling deletion of entire
>> call in 30 seconds
>> Jan 20 16:11:21 ip-172-31-13-220 rtpengine[42387]: INFO:
>> [f75f1e374747457ca016e3a3a62ff4b3]: [control] Replying to 'delete' from
>> 127.0.0.1:33919 (elapsed time 0.000179 sec)
>>
>>
>> However, when I call from Linphone to Microsip, there's one-way audio and
>> the following in the logs:
>>
>> Jan 20 16:02:29 ip-172-31-13-220 rtpengine[42387]: INFO: [CjBB-HZqpe]:
>> [control] Received command 'offer' from 127.0.0.1:40022
>> Jan 20 16:02:29 ip-172-31-13-220 rtpengine[42387]: NOTICE: [CjBB-HZqpe]:
>> [core] Creating new call
>> Jan 20 16:02:29 ip-172-31-13-220 rtpengine[42387]: INFO: [CjBB-HZqpe]:
>> [control] Replying to 'offer' from 127.0.0.1:40022 (elapsed time
>> 0.000500 sec)
>> Jan 20 16:02:37 ip-172-31-13-220 rtpengine[42387]: INFO: [CjBB-HZqpe]:
>> [control] Received command 'answer' from 127.0.0.1:40022
>> Jan 20 16:02:37 ip-172-31-13-220 rtpengine[42387]: INFO: [CjBB-HZqpe]:
>> [control] Replying to 'answer' from 127.0.0.1:40022 (elapsed time
>> 0.000209 sec)
>> Jan 20 16:02:37 ip-172-31-13-220 /usr/sbin/opensips[79600]: incoming reply
>> Jan 20 16:02:38 ip-172-31-13-220 rtpengine[42387]: INFO: [CjBB-HZqpe]:
>> [control] Received command 'answer' from 127.0.0.1:40022
>> Jan 20 16:02:38 ip-172-31-13-220 rtpengine[42387]: INFO: [CjBB-HZqpe]:
>> [control] Replying to 'answer' from 127.0.0.1:40022 (elapsed time
>> 0.000178 sec)
>> Jan 20 16:02:38 ip-172-31-13-220 /usr/sbin/opensips[79600]: incoming reply
>> Jan 20 16:02:39 ip-172-31-13-220 rtpengine[42387]: INFO: [CjBB-HZqpe]:
>> [control] Received command 'answer' from 127.0.0.1:40022
>> Jan 20 16:02:39 ip-172-31-13-220 rtpengine[42387]: INFO: [CjBB-HZqpe]:
>> [control] Replying to 'answer' from 127.0.0.1:40022 (elapsed time
>> 0.000139 sec)
>> Jan 20 16:02:39 ip-172-31-13-220 /usr/sbin/opensips[79600]: incoming reply
>> Jan 20