Re: [OpenSIPS-Users] Implementation of RFC 8599

2024-02-05 Thread Volkan Oransoy
That is exactly what I was looking for :) Thank you Adrian. Volkan Oransoy On 5 Feb 2024 at 10:34 +, Adrian Georgescu , wrote: > You must register at least once, so that the server can collect the push > token. Then, later you just wait during the Invite for the devices to get the

Re: [OpenSIPS-Users] Implementation of RFC 8599

2024-02-05 Thread Volkan Oransoy
Hi Adrian Thanks for your comment. I got your point. Can you give a hint to handle the the call forking for freshly registered devices? I need to keep calls in a queue until the UA registers. Is msilo right approach? Thanks Volkan Oransoy On 5 Feb 2024 at 10:02 +, Adrian Georgescu , wrote

Re: [OpenSIPS-Users] Implementation of RFC 8599

2024-02-05 Thread Volkan Oransoy
o practically, UA should keeps its registered state active, so needs a registration refresh in regular intervals. That is not the ideal case for a mobile app I believe. So the main idea is to keep power consumption at minimum. Thanks Volkan Oransoy On 4 Feb 2024 at 15:01 +, Adrian Georgescu ,

Re: [OpenSIPS-Users] pn opensips 3.4

2024-02-04 Thread Volkan Oransoy
Hi Ronald For our case, we use exec on development environment too. For the production, we will use rabbitmq and custom events to decouple pn delivery from the script. Volkan Oransoy On 3 Feb 2024 at 20:54 +, r...@rvgeerligs.nl, wrote: > Hi, > > Currently experimenting with the EX

Re: [OpenSIPS-Users] Implementation of RFC 8599

2024-02-03 Thread Volkan Oransoy
. Volkan Oransoy On 2 Feb 2024 at 14:51 +, r...@rvgeerligs.nl, wrote: > Hi Volkan, > > I implemented the scripting from  > sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-ii/ in > opensips 3.4.0. > As the send pn to apple or googlei s not defined I fail to get the pa

[OpenSIPS-Users] Implementation of RFC 8599

2024-02-02 Thread Volkan Oransoy
Hi all, I am working on implementing RFC 8599 and have an architectural question. I followed the blog post https://blog.opensips.org/2020/06/03/sip-push-notification-with-opensips-3-1-lts-rfc-8599-supportpart-ii/ and it works. Based on the rfc and the implementation of Opensips, the UA should

[OpenSIPS-Users] TLS problem

2022-08-26 Thread Volkan Oransoy
27] DBG:core:handle_io: We have received conn 0x7f883464e098 with rw 1 on fd 4 Aug 26 14:06:23 [1927] DBG:core:io_watch_add: [TCP_worker] io_watch_add op (4 on 84) (0x55ef6f9b8080, 4, 19, 0x7f883464e098,1), fd_no=4/1024 Aug 26 14:06:23 [1927] DBG:proto_tls:tls_read_req: Using the global ( per process ) buff Aug 26 14:0

Re: [OpenSIPS-Users] Drouting relay issue

2022-05-17 Thread Volkan Oransoy
Hi Bogdan Yes, TCP stack works as anticipated. Thanks Volkan Oransoy On 17 May 2022 16:02 +0100, Bogdan-Andrei Iancu , wrote: > Thanks on the follow up here. I guess you need to switch to TCP, right ? > > Regards, > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer >

Re: [OpenSIPS-Users] Drouting relay issue

2022-05-17 Thread Volkan Oransoy
” at os network. Cheers Volkan Oransoy On 11 May 2022 11:52 +0100, Volkan Oransoy , wrote: > I think the screenshot has been discarded by the mailman. The sip traffic is > as follows. The proxy tries to retransmit and fails after three more at

Re: [OpenSIPS-Users] Drouting relay issue

2022-05-11 Thread Volkan Oransoy
(SDP) │  +1.953642 │ │ >>> │  10:47:36.051892 │ │ INVITE (SDP) │  +1.603582 │ │ >>> │  10:47:37.655474 │ 408 Request Timeout │ │  +0.001615 │ <── │ │  10:47:37.657089 │ ACK │ │  │ ──────

[OpenSIPS-Users] Drouting relay issue

2022-05-11 Thread Volkan Oransoy
ication/sdp Content-Disposition: session Content-Length: 621 Remote-Party-ID: "+90850885" ;party=calling;screen=yes;privacy=off v=0 o=FreeSWITCH 1651210438 1651210439 IN IP4 1.1.1.1 s=FreeSWITCH c=IN IP4 1.1.1.1 t=0 0 ... -- Volkan Oransoy __

[OpenSIPS-Users] Matching calls with uac_registrant records

2021-12-06 Thread Volkan Oransoy
Hi all, I am using uac_registrant to register a bunch of sip accounts to remote sip registrars. There are multiple remote registrars and a we can register more than one account to a registrar. My Opensips instance can succesfully register and can receive calls as of now. What I am trying to

Re: [OpenSIPS-Users] TLS issue with WSS

2019-03-12 Thread Volkan Oransoy
is a TLS valid one ? > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 02/27/2019 03:21 PM, Volkan Oransoy wrote:

[OpenSIPS-Users] TLS issue with WSS

2019-02-27 Thread Volkan Oransoy
: TLSv1.2 Cipher: ECDHE-RSA-AES256-GCM-SHA384 Session-ID: Session-ID-ctx: Master-Key: EA79ADD7422068E3C79258F309B1D0772B5F11F3DB995DBB869BB68AA154D2827D781A57517CF8841E58F3EB9F18D656 Start Time: 1551272932 Timeout : 7200 (sec) Verify return cod

[OpenSIPS-Users] Uac registrant check

2017-07-21 Thread Volkan Oransoy
Hi all, I use uac_registrant to register to remote SIP systems and registration phase seems ok. What I want to do is to receive calls from these systems and before accepting calls to my box, I want to check destination, if it is a valid record on my system. I found a couple of replies on list

Re: [OpenSIPS-Users] Dispacher and Drouting question

2014-10-13 Thread Volkan Oransoy
() or xxx_domain() ) the GW may be set either in $dd, either in $rd. Regards, Bogdan-Andrei Iancu OpenSIPS Founder and Developerhttp://www.opensips-solutions.com On 10.10.2014 14:33, Volkan Oransoy wrote: Hi, I am working on a special load balancing setup. For specific $rU values, I want

[OpenSIPS-Users] Dispacher and Drouting question

2014-10-10 Thread Volkan Oransoy
Hi, I am working on a special load balancing setup. For specific $rU values, I want to keep choosen gateway and use cached value for next time. So that, for each destination, there will be a specific gateway. But I failed at getting the chosen gw to an avp. I am trying to get it, just before