Re: [SR-Users] presentce handly_subscribe() protocol/port mismatch to WS endpoint

Found that at the tm:local-request $ru modifies but anyway - request sent to old RURI. INFO: NOTIFY to WS, update RURI -- here is making $ru = $ru+";transport=ws"; --- INFO: NOTIFY to WS, new RURI: sip:94e51c30bdf28de52519@93.81.99.68:54733

Re: [SR-Users] presentce handly_subscribe() protocol/port mismatch to WS endpoint

Can not find any entry of this device at the active watchers. Suppose after module found sockets mistmatch and didnt got NOTIFY response it removes entry from active watchers... I added handling at the event route as you sugested and tried to do next Firs i tried fix $ru here but it does not

Re: [SR-Users] Multi crashes in the same day

Hello, likely you got hit by the issue fixed by:   - https://github.com/kamailio/kamailio/commit/25f2180999dafb807068313c4a329a163dd99f92 4.2 series is old and I expect this commit was not backported there. Cheers, Daniel On 03.10.17 18:49, igor.potjevle...@gmail.com wrote: > > Hello ! > >  

[SR-Users] Multi crashes in the same day

Hello ! I have multi crashes on a Kamailio 4.2.8 instance. Already 6 coredump today, same time with the same scenario. Below the output of the last coredump: (gdb) where #0 0x003d6f6328a5 in raise () from /lib64/libc.so.6 #1 0x003d6f634085 in abort () from /lib64/libc.so.6 #2

Re: [SR-Users] 200 OK - need to include Expires

Attached is the pcap sent by Kamailio. My SIP client / Presence client requires 200 OK to be mandatory so its discarding the message. Can you help me Kamailio send Expires header for 200 OK messge? Regards, MGSK On Tue, Oct 3, 2017 at 9:59 PM, Subba Krishna MG wrote: >

Re: [SR-Users] 200 OK - need to include Expires

Hello Daniel, I am refering to Expires : 50 header. of 200 OK message. Example: UDP message sent (372 bytes): SIP/2.0 200 OK Via: SIP/2.0/UDP 0.0.0.0:5060 ;transport=udp:5060;branch=z9hG4bK*002e-009f-0dc8 From: ;tag=b72e12bnbsN2759d33bc8-34dfbc00 To:

Re: [SR-Users] presentce handly_subscribe() protocol/port mismatch to WS endpoint

Hello, you should use set_contact_alias() for subscribe instead of fixed_nated_contact(), is a better option. Back to the reported topic, can you paste here the db record from active_watchers table? Then, you should be able to update some parts of the local generated requests by having an

Re: [SR-Users] 200 OK - need to include Expires

Hello, what exactly you refer to by EXPIRES IE? Expires header? Cheers, Daniel On 03.10.17 04:18, Subba Krishna MG wrote: > Hello, > > This might be very simple question for you folks,  > > I am using Kamailio as SIP - Presence server, and For every user > Kamailio is sending 200 OK, but the

[SR-Users] how to use SIP header Route

HI, How to use SIP header Route in [SIPOUT] route instead of uri -- Regards, K.Anil Kumar ___ Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] presentce handly_subscribe() protocol/port mismatch to WS endpoint

Also found at the lists some solutions like "accept fix_nated_register() and fix_nated_contact() for REGISTER and SUBSCRIBE" Done it. But still protos mistmatch... kamailio founds tls:myip:myport and forces t to udp... 2017-10-03 10:49 GMT+03:00 Yuriy Gorlichenko : > Hi. I

[SR-Users] presentce handly_subscribe() protocol/port mismatch to WS endpoint

Hi. I have presence server and it works fine for UDP/TCP/TLS endpoints. For now i have new one type of endpoints that runs via WebSockets It sends SUBSCRIBE request to the and then after handle_subscribe() NOTIFY not comes to the subscriber because of [core/forward.c:231]: get_send_socket2():

[SR-Users] "python_exec" not work

Iwant to work with "app_python" module,i set “script_name”,“mode_init_function”, “child_init_function” and “python_exec”in kamailio.cfg ,but I have a problem in “python_exec”section. This section not work in correctly, please guide me.thanks___