[SR-Users] Confusion about various TCP expiry and lifetime parameters

2015-08-25 Thread M S
Hi, We have a bit of confusion regarding tcp_connecton_timeout core parameter. The documentation says, -- Lifetime in seconds for TCP sessions. TCP sessions which are inactive for longer than *tcp_connection_lifetime* will be closed by Kamailio. -- However we observe a strange behaviour. 1. The

Re: [SR-Users] BLF state on register

2015-08-25 Thread Loic Chabert
Thanks Daniel, Yes a subscribe request as been sent by my hardphone, authentication works, but juste after 200OK, a NOTIFY message as been sent with this header: Subscription-State: terminated;reason=timeout But, on my SQL table "active_watcher", i can see my user (103) subscribed to 102 dialog e

[SR-Users] Kamailio dead after INVITE from SIPDROID

2015-08-25 Thread Kowalski Piotr 3 - Hurt
Hello Community. We have openIMS nodes in our lab. We have Kamailio 4.0 based solution. I registered SIPDROID client (iptel) on Android and JITSI on WINDOWS. When I call from SIPDROID to JITSI following happens: SIP DROID - iptel - client - registration ok, but INVITE attempt towards

Re: [SR-Users] OT: some github stuff

2015-08-25 Thread Fred Posner
On 08/25/2015 06:23 AM, Daniel-Constantin Mierla wrote: > > >>> >> There's a special "github" markdown that shouldn't require a file: > > I don't understand what do you mean with the above, can you detail? > > I was looking to get README displayed as markdown file by github.com on > the website

Re: [SR-Users] during registration nonce expired, after backwards time shift

2015-08-25 Thread Vasiliy Ganchev
Daniel-Constantin Mierla-6 wrote > I looked at the code and the system time is used (not the the internal > value). Therefore, after detecting and invalid nonce, if you do > challenge again, a nonce with the right time should be generated and > used for authentication. > > Look at sip trace to see

Re: [SR-Users] Rewrite Invite w/o sdp

2015-08-25 Thread Serge S. Yuriev
Hello, I'm going to send 183 w/o sdp stimulating Cisco to send PRACK. After rebilding INVITE and sending it to callee we are expecting normal call flow: 183/180 (from callee) and 200 (or whatever final). Thanks. On 25/08/15 13:25, Daniel-Constantin Mierla wrote: Hello, saving an invite for

Re: [SR-Users] OT: some github stuff

2015-08-25 Thread Camille Oudot
Le Tue, 25 Aug 2015 12:23:21 +0200, Daniel-Constantin Mierla a écrit : > I was looking to get README displayed as markdown file by github.com > on the website of kamailio project repository, without renaming it to > README.md. Maybe a symlink README.md -> README could do the trick? -- Camille

Re: [SR-Users] Rewrite Invite w/o sdp

2015-08-25 Thread Daniel-Constantin Mierla
Hello, saving an invite for later use can be achieved with t_suspend()/t_continue -- see the tmx module. However, regarding what you need, how do you plan to generate the sdp for early media/183? You need ip, port and media description, are they going to be just some random/invalid values? Cheer

Re: [SR-Users] OT: some github stuff

2015-08-25 Thread Daniel-Constantin Mierla
On 24/08/15 21:40, Fred Posner wrote: > On 08/24/2015 02:34 PM, Daniel-Constantin Mierla wrote: >> 2) is there any specific content/marker to add to README to have it >> interpreted as markdown (without adding .md extensions)? Something like >> a special first or last line, ... It will be display

Re: [SR-Users] BLF state on register

2015-08-25 Thread Daniel-Constantin Mierla
Hello, do you get subscribe requests from users? A NOTIFY is sent only when there is an active subscription. Also, be sure you allow traffic on loopback without authentication -- pua_usrloc may send a publish to same sip server instance. Running with debug=3 and looking at syslog should reveal mo

[SR-Users] BLF state on register

2015-08-25 Thread Loic Chabert
Hello everyone, I'm trying to reproduce BLF's asterisk fonctionnality with kamailio. With asterisk, on register, NOTIFY message has been sent to all suscribed users. So LED became green. How can i reproduce this function ? I have try to execute a "pua_set_publish()" on register route, but it's no