Re: [SR-Users] It does not log any route. Clean installation

2017-10-13 Thread Bruno Henrique Gomes GouvĂȘa
Hello, even with log on console I do not get anything yet. [root@pabxmodelo ~]# /usr/sbin/kamailio -P /var/run/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio loading modules under config path: /usr/lib64/kamailio/modules/ Listening on udp: PUBLIC_IP:5060 Aliases: udp:

[SR-Users] rtcp-mux policy for RTPengine module

2017-10-13 Thread Yuriy Gorlichenko
Hi all! Some time ago Chromium browser sets rtcpMuxPolicy: required by default (soon on Chrome 58) It means that webRTC based clients not accepts a=rtcp:31757 And uses for RTP and RTCP multiplexing at one port Main trouble that i found: calls between original SIP client and webRTC client (SIP

[SR-Users] uac_replace_from and header adulterations

2017-10-13 Thread Alex Balashov
Hello, I've got a bizarre problem caused by bad UA behaviour: UA A ---> Kamailio (P) ---> UA B 1. UA A sends initial INVITE through P to B; 2. Kamailio (P) makes some modifications to the From header using uac_replace_from() and passes along to B. 3. B sends an in-dialog request (e.g. BYE

[SR-Users] Problem removing headers from FAILURE_ROUTE

2017-10-13 Thread Joel Serrano
Hi all, I have the following scenario: Client -> Kamailio (adds X-CallSource hdr) -> Media Server -> Kamailio (removes all "X-" headers) -> Carrier Carrier doesn't get any X- headers. All works. Now for example, if the media server replies with a non-OK status, like: Client -> Kamailio

[SR-Users] Testing for user=phone with siputils uri_param() doesn't work

2017-10-13 Thread George Diamantopoulos
Hello, In my script I've had to test for the user=phone parameter in URIs. I thought uri_param() from siputils would be handy for this operation on the RURI, so I did: if ( !uri_param("user","phone") ) { add_uri_param("user=phone"); } Unfortunately this wouldn't work (uri_param

Re: [SR-Users] unexpected behavior of save from registrar module

2017-10-13 Thread Sebastian Damm
Hi, indeed, when a function returns with 0, Kamailio immediately ends the processing of the packet. So that's why the unlock statement is never executed. I am wondering, why you are using locks at this point. That way, only one REGISTER can be processed at the same time, since they all share the

[SR-Users] unexpected behavior of save from registrar module

2017-10-13 Thread Vasiliy Ganchev
Hi, community! I have in my Kamailio script following block (while REGISTER processing, after auth succeed): . /* Save to usrloc */ lock("LOCATION_LOCK"); if (!save("location")) { unlock("LOCATION_LOCK"); sl_reply_error();