[SR-Users] Kamailio and RTPProxy in-front of freeswitch

[Achintha]

hi all,

i have configured kamailio and RTPProxy on one ubuntu server then
freeswitch on another server.
all servers installed on digital ocean.
i was tried to build following setup,

  SIP_Call--> kamailio+RTPPROXY---> freeswitch

put following configurations on kamailio.

modparam("rtpproxy", "rtpproxy_sock", "udp:localhost:7722")

modparam("rtpproxy", "rtpproxy_retr", 2)

modparam("rtpproxy", "ice_candidate_priority_avp", "$avp(ice_priority)")



mhomed=1


route[FROM_TRUNK]

#force_send_socket("pu.bl.ic.ip ");

rtpproxy_manage("","pu.bl.ic.ip ");

$du="sip:ip.of.free.switch:5080";

route(RELAY);


call was connected  but rtp is not going through the kamailio server like
folows,

SIP FLOOR

SIP_Call--> kamailio---> freeswitch
SIP_Call<-- kamailio<--- freeswitch


RTP FLOOR

SIP_Call --> freeswitch
SIP_Call <-- freeswitch


please help me to configure kamailio and RTPProxy to manage RTP

-- 
thanking you..
Achintha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Kamailio RTP Engine

[Jack Stevens]

Hi Guys,

Looking for some help on configuring RTP Engine with Dispatcher on my Kamailio 
Box

Please see this paste for the kamailio configuration = 
http://pastebin.com/yZzSEJmK

When I run a call the dispatcher does it job perfectly but the rtpengine is not 
been used does anyone know why

-- 





CONFIDENTIAL EMAIL FROM NETCALL TELECOM LIMITED

This email, and any attachments, is intended only for the above addressee. 
It may contain private and/or confidential information. If you have 
received this email in error you are on notice of its status, please 
immediately notify the sender by return email then delete this message and 
any attachments. If you are not the addressee, except to notify the sender, 
you must not use, disclose, copy or distribute this email and/or its 
attachments. Netcall Telecom accepts no responsibility for any changes made 
to this message after it has been sent by the original author. Opinions or 
views expressed in this email may be those of the individual sender and not 
Netcall Telecom. Nothing in this email shall bind Netcall Telecom in any 
contract or obligation

Netcall Telecom Ltd Registered in England 2831215. Registered Office : 3rd 
Floor, Hamilton House, 111 Marlowes, Hemel Hempstead, Herts, HP1 1BB
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Prepaid system using dialog and sqlops

[Infinicalls Infinicalls]

Hi Daniel,
  Thanks. I have added credits in Subscriber. But where exactly should
I insert the SQL statements in kamailio.cfg so that it gets executed
for each and every call. The rate_unit multiplied with time_unit in
billing_rates should be done in realtime, I guess.

Also is it possible to check for credits > 0 in Auth and disconnect
the user if this condition is not met.

regards
Ganesh Kumar

On 8/3/16, Daniel-Constantin Mierla  wrote:
> Hello,
>
>
> On 02/08/16 07:36, Infinicalls Infinicalls wrote:
>> Hi,
>>  I am still struggling to get a prepaid system for my service.
>>
>> After installing SIREMIS, I am able to get the CDRs updated. But even
>> after adding the cron settings, the call duration doesn't get updated.
>>
>> And also in
>>
>> http://lists.sip-router.org/pipermail/sr-users/2012-January/071517.html
>>
>> it has been mentioned that
>>
>> "If it is the case of 1 call per user at a time, then practically can
>> be done from kamailio config only. When call starts, compute the max
>> duration for that call based on caller/destination (e.g., call a
>> stored procedure via sqlops) and set the dialog timeout to that
>> duration. When call ends (BYE in main route or timeout route) update
>> the credit accordingly."
>>
>> Can somebody let me know if my understanding is correct.
>>
>> 1) Add a field called "credits" in the database. And topup that field.
>>
>> 2) First compute max permitted duration for that user by multiplying
>> the cost for number prefix (say +91) and pulse.
>>
>> 3) And finally add this value to timeout of dialog. modparam("dialog",
>> "default_timeout", 10)
>> $dlg_ctx(timeout_bye) = 1;
>>
>> Will this work? Any help would be appreciated.
>>
> That should work, you also need to deduct the used credit when the call
> is ended.
>
> Cheers,
> Daniel
>

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio 4.4 wont start on CentOS 7 using script

[Fabian Borot]

when starting from the "sbin" directory it uses this as default: 
"/var/run/kamailio.pid"...I changed it to 
"PID_FILE=/var/run/kamailio/kamailio.pid" and it works fine as well


the PID_FILE in the " /etc/init.d/kamailio" file is also that one: "

PID_FILE=/var/run/kamailio/kamailio.pid" and that folder has all permissions.


I can still use it w/o the service script but it would be nice to have it be 
working properly


From: Fabian Borot 
Sent: Thursday, August 4, 2016 9:54 AM
To: sr-users@lists.sip-router.org
Subject: Re: Kamailio 4.4 wont start on CentOS 7 using script



thank you, yes, I did have to change these lines according to my install path , 
these are my settings:


KAM=/usr/local/kamailio-4.4/sbin/kamailio
KAMCFG=/usr/local/kamailio-4.4/etc/kamailio/kamailio.cfg
PROG=kamailio
PID_FILE=/var/run/kamailio.pid
LOCK_FILE=/var/lock/subsys/kamailio
RETVAL=0
DEFAULTS=/etc/default/kamailio

the directory is created:
[root@ar-mia-proxy-01 ~]# ls -la /var/run/kamailio/
total 0
drwxr-xr-x.  2 root root  40 Aug  4 15:18 .
drwxr-xr-x. 23 root root 640 Aug  4 15:18 ..
[root@ar-mia-proxy-01 ~]#

I am using the "root" user so it has access to it


From: Fabian Borot 
Sent: Thursday, August 4, 2016 9:30 AM
To: sr-users@lists.sip-router.org
Subject: Kamailio 4.4 wont start on CentOS 7 using script


Hello

I installed/compiled version 4.4 on CentOS 7. When I start the server like 
this: "./kamctl start" it works but when I try to use the script: 
"/etc/init.d/kamailio" it fails




[root@ar-mia-proxy-01 sbin]# /etc/init.d/kamailio start
Starting kamailio (via systemctl):  Job for kamailio.service failed because the 
control process exited with error code. See "systemctl status kamailio.service" 
and "journalctl -xe" for details.
   [FAILED]
[root@ar-mia-proxy-01 sbin]#

when running the "status" I see this:

[root@ar-mia-proxy-01 sbin]# /etc/init.d/kamailio status
â kamailio.service - LSB: Kamailio (OpenSER) - the Open Source SIP Server
   Loaded: loaded (/etc/rc.d/init.d/kamailio)
   Active: failed (Result: exit-code) since Thu 2016-08-04 15:25:59 GMT; 14s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 5556 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Starting LSB: Kamailio 
(OpenSER) - the Open Source SIP Server...
Aug 04 15:25:59 ar-mia-proxy-01.dom.com kamailio[5556]: Starting kamailio:
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Failed to start LSB: 
Kamailio (OpenSER) - the Open Source SIP Server.
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Unit kamailio.service 
entered failed state.
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: kamailio.service failed.
[root@ar-mia-proxy-01 sbin]#

I welcome all ideas, thank you in advance





___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio 4.4 wont start on CentOS 7 using script

[Fabian Borot]

thank you, yes, I did have to change these lines according to my install path , 
these are my settings:


KAM=/usr/local/kamailio-4.4/sbin/kamailio
KAMCFG=/usr/local/kamailio-4.4/etc/kamailio/kamailio.cfg
PROG=kamailio
PID_FILE=/var/run/kamailio.pid
LOCK_FILE=/var/lock/subsys/kamailio
RETVAL=0
DEFAULTS=/etc/default/kamailio

the directory is created:
[root@ar-mia-proxy-01 ~]# ls -la /var/run/kamailio/
total 0
drwxr-xr-x.  2 root root  40 Aug  4 15:18 .
drwxr-xr-x. 23 root root 640 Aug  4 15:18 ..
[root@ar-mia-proxy-01 ~]#

I am using the "root" user so it has access to it


From: Fabian Borot 
Sent: Thursday, August 4, 2016 9:30 AM
To: sr-users@lists.sip-router.org
Subject: Kamailio 4.4 wont start on CentOS 7 using script


Hello

I installed/compiled version 4.4 on CentOS 7. When I start the server like 
this: "./kamctl start" it works but when I try to use the script: 
"/etc/init.d/kamailio" it fails




[root@ar-mia-proxy-01 sbin]# /etc/init.d/kamailio start
Starting kamailio (via systemctl):  Job for kamailio.service failed because the 
control process exited with error code. See "systemctl status kamailio.service" 
and "journalctl -xe" for details.
   [FAILED]
[root@ar-mia-proxy-01 sbin]#

when running the "status" I see this:

[root@ar-mia-proxy-01 sbin]# /etc/init.d/kamailio status
â kamailio.service - LSB: Kamailio (OpenSER) - the Open Source SIP Server
   Loaded: loaded (/etc/rc.d/init.d/kamailio)
   Active: failed (Result: exit-code) since Thu 2016-08-04 15:25:59 GMT; 14s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 5556 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Starting LSB: Kamailio 
(OpenSER) - the Open Source SIP Server...
Aug 04 15:25:59 ar-mia-proxy-01.dom.com kamailio[5556]: Starting kamailio:
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Failed to start LSB: 
Kamailio (OpenSER) - the Open Source SIP Server.
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Unit kamailio.service 
entered failed state.
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: kamailio.service failed.
[root@ar-mia-proxy-01 sbin]#

I welcome all ideas, thank you in advance





___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio 4.4 wont start on CentOS 7 using script

[Nagorny, Dimitry]

Hello Fabian,

I had a similar problem and build my own little kamailio.service file for 
CentOS7. Please find it attached, just drop it under /etc/systemd/system/ and 
give it execution permissions and activate it afterwards with "systemctl enable 
kamailio.service" and "systemctl start kamailio.service". You might have to 
change the path's to match your installation.

Regards
Dimitry Nagorny
Working Student Software Developer

Von: sr-users [mailto:sr-users-boun...@lists.sip-router.org] Im Auftrag von 
Fabian Borot
Gesendet: Donnerstag, 4. August 2016 15:31
An: sr-users@lists.sip-router.org
Betreff: [SR-Users] Kamailio 4.4 wont start on CentOS 7 using script


Hello

I installed/compiled version 4.4 on CentOS 7. When I start the server like 
this: "./kamctl start" it works but when I try to use the script: 
"/etc/init.d/kamailio" it fails




[root@ar-mia-proxy-01 sbin]# /etc/init.d/kamailio start
Starting kamailio (via systemctl):  Job for kamailio.service failed because the 
control process exited with error code. See "systemctl status kamailio.service" 
and "journalctl -xe" for details.
   [FAILED]
[root@ar-mia-proxy-01 sbin]#

when running the "status" I see this:

[root@ar-mia-proxy-01 sbin]# /etc/init.d/kamailio status
â kamailio.service - LSB: Kamailio (OpenSER) - the Open Source SIP Server
   Loaded: loaded (/etc/rc.d/init.d/kamailio)
   Active: failed (Result: exit-code) since Thu 2016-08-04 15:25:59 GMT; 14s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 5556 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Starting LSB: Kamailio 
(OpenSER) - the Open Source SIP Server...
Aug 04 15:25:59 ar-mia-proxy-01.dom.com kamailio[5556]: Starting kamailio:
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Failed to start LSB: 
Kamailio (OpenSER) - the Open Source SIP Server.
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Unit kamailio.service 
entered failed state.
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: kamailio.service failed.
[root@ar-mia-proxy-01 sbin]#

I welcome all ideas, thank you in advance







kamailio.service
Description: kamailio.service
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio 4.4 wont start on CentOS 7 using script

[Jurijs Ivolga]

Hi,

I'm not sure about Centos 7, but on Centos 6, you need to update kamailio
init.d script to make it work. Following lines should be updated:
KAM=/usr/local/sbin/kamailio
KAMCFG=/usr/local/etc/kamailio/kamailio.cfg
PROG=kamailio
PID_FILE=/var/run/kamailio/kamailio.pid

And you need to create directory /var/run/kamailio and add access rights to
kamailio user.

With kind regards,

Jurijs

On Thu, Aug 4, 2016 at 4:30 PM, Fabian Borot  wrote:

> Hello
>
> I installed/compiled version 4.4 on CentOS 7. When I start the server like
> this: "./kamctl start" it works but when I try to use the script:
> "/etc/init.d/kamailio" it fails
>
>
>
> [root@ar-mia-proxy-01 sbin]# /etc/init.d/kamailio start
> Starting kamailio (via systemctl):  Job for kamailio.service failed
> because the control process exited with error code. See "systemctl status
> kamailio.service" and "journalctl -xe" for details.
>[FAILED]
> [root@ar-mia-proxy-01 sbin]#
>
> when running the "status" I see this:
>
> [root@ar-mia-proxy-01 sbin]# /etc/init.d/kamailio status
> â kamailio.service - LSB: Kamailio (OpenSER) - the Open Source SIP Server
>Loaded: loaded (/etc/rc.d/init.d/kamailio)
>Active: failed (Result: exit-code) since Thu 2016-08-04 15:25:59 GMT;
> 14s ago
>  Docs: man:systemd-sysv-generator(8)
>   Process: 5556 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited,
> status=1/FAILURE)
>
> Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Starting LSB:
> Kamailio (OpenSER) - the Open Source SIP Server...
> Aug 04 15:25:59 ar-mia-proxy-01.dom.com kamailio[5556]: Starting kamailio:
> Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: kamailio.service:
> control process exited, code=exited status=1
> Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Failed to start LSB:
> Kamailio (OpenSER) - the Open Source SIP Server.
> Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Unit kamailio.service
> entered failed state.
> Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: kamailio.service
> failed.
> [root@ar-mia-proxy-01 sbin]#
>
> I welcome all ideas, thank you in advance
>
>
>
>
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Kamailio 4.4 wont start on CentOS 7 using script

[Fabian Borot]

Hello

I installed/compiled version 4.4 on CentOS 7. When I start the server like 
this: "./kamctl start" it works but when I try to use the script: 
"/etc/init.d/kamailio" it fails




[root@ar-mia-proxy-01 sbin]# /etc/init.d/kamailio start
Starting kamailio (via systemctl):  Job for kamailio.service failed because the 
control process exited with error code. See "systemctl status kamailio.service" 
and "journalctl -xe" for details.
   [FAILED]
[root@ar-mia-proxy-01 sbin]#

when running the "status" I see this:

[root@ar-mia-proxy-01 sbin]# /etc/init.d/kamailio status
â kamailio.service - LSB: Kamailio (OpenSER) - the Open Source SIP Server
   Loaded: loaded (/etc/rc.d/init.d/kamailio)
   Active: failed (Result: exit-code) since Thu 2016-08-04 15:25:59 GMT; 14s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 5556 ExecStart=/etc/rc.d/init.d/kamailio start (code=exited, 
status=1/FAILURE)

Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Starting LSB: Kamailio 
(OpenSER) - the Open Source SIP Server...
Aug 04 15:25:59 ar-mia-proxy-01.dom.com kamailio[5556]: Starting kamailio:
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: kamailio.service: control 
process exited, code=exited status=1
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Failed to start LSB: 
Kamailio (OpenSER) - the Open Source SIP Server.
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: Unit kamailio.service 
entered failed state.
Aug 04 15:25:59 ar-mia-proxy-01.dom.com systemd[1]: kamailio.service failed.
[root@ar-mia-proxy-01 sbin]#

I welcome all ideas, thank you in advance





___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Path & Loose Route

[Luke Milbourne]

Hi Daniel,

As mentioned previously, I've pasted a copy of the loose.c log lines below.

Aug  4 09:21:43 ip-10-10-2-5 /sbin/kamailio[4711]: DEBUG: rr [loose.c:179]:
find_next_route(): No next Route HF found
Aug  4 09:21:43 ip-10-10-2-5 /sbin/kamailio[4711]: DEBUG: rr [loose.c:846]:
after_loose(): no next URI found
Aug  4 09:21:43 ip-10-10-2-5 /sbin/kamailio[4704]: DEBUG: rr [loose.c:88]:
is_preloaded(): is_preloaded: No
*Aug  4 09:21:43 ip-10-10-2-5 /sbin/kamailio[4704]: DEBUG: rr
[loose.c:783]: after_loose(): Topmost route URI: 'sip:10.10.2.5:5072
' is me*
Aug  4 09:21:43 ip-10-10-2-5 /sbin/kamailio[4704]: DEBUG: rr [loose.c:179]:
find_next_route(): No next Route HF found
Aug  4 09:21:43 ip-10-10-2-5 /sbin/kamailio[4704]: DEBUG: rr [loose.c:807]:
after_loose(): No next URI found
Aug  4 09:21:47 ip-10-10-2-5 /sbin/kamailio[4707]: DEBUG: rr [loose.c:84]:
is_preloaded(): is_preloaded: Yes
Aug  4 09:21:47 ip-10-10-2-5 /sbin/kamailio[4707]: DEBUG: rr [loose.c:783]:
after_loose(): Topmost route URI: 'sip:201@10.10.2.5:5072' is me
Aug  4 09:21:47 ip-10-10-2-5 /sbin/kamailio[4707]: DEBUG: rr [loose.c:179]:
find_next_route(): No next Route HF found
Aug  4 09:21:47 ip-10-10-2-5 /sbin/kamailio[4707]: DEBUG: rr [loose.c:807]:
after_loose(): No next URI found
Aug  4 09:21:48 ip-10-10-2-5 /sbin/kamailio[4706]: DEBUG: rr [loose.c:88]:
is_preloaded(): is_preloaded: No
Aug  4 09:21:48 ip-10-10-2-5 /sbin/kamailio[4706]: DEBUG: rr [loose.c:783]:
after_loose(): Topmost route URI: 'sip:10.10.2.5:5072' is me
Aug  4 09:21:48 ip-10-10-2-5 /sbin/kamailio[4706]: DEBUG: rr [loose.c:179]:
find_next_route(): No next Route HF found
Aug  4 09:21:48 ip-10-10-2-5 /sbin/kamailio[4706]: DEBUG: rr [loose.c:807]:
after_loose(): No next URI found
Aug  4 09:21:51 ip-10-10-2-5 /sbin/kamailio[4711]: DEBUG: rr [loose.c:88]:
is_preloaded(): is_preloaded: No
Aug  4 09:21:51 ip-10-10-2-5 /sbin/kamailio[4711]: DEBUG: rr [loose.c:783]:
after_loose(): Topmost route URI: 'sip:[KAM_PUBLIC_IP]:5062;r2=on;lr=on'

I've since changed the Kamailio script to alter register packets using
the nat_uac_test("19") and fix_nated_contact(), but I'm unsure if this is
good practice or not.

Kind regards,
Luke

On 4 August 2016 at 07:10, Luke Milbourne  wrote:

> Hi Daniel,
>
> Thanks again for your reply again.
>
> I remembered about the debug setting and done it yesterday, not at my pc
> right now but I remember one of the log lines was saying "the topmost route
> header is me".
>
> Still trying to understand it, but will get a copy of the log lines for
> you, if you wouldn't mind taking a look.
>
> Thanks again,
> Luke
>
> On 4 Aug 2016 06:57, "Daniel-Constantin Mierla"  wrote:
>
> Hello,
>
> set debug=3 in kamailio.cfg and look at log messages in syslog.
>
> If you find it too verbose, use dispatcher module and set debug level only
> for core and rr modules to 3.
> Cheers,
> Daniel
>
>
> On 03/08/16 13:22, Luke Milbourne wrote:
>
> Hi Daniel,
>
> I've added some more logging and can see loose_route() is returning -1 -
> route calculation has been unsuccessful.
>
> Is there a way of finding out why this is the case?
>
> Kind regards,
> Luke
>
> On 2 August 2016 at 09:49, Luke Milbourne 
> wrote:
>
>> I added the below xlog lines into my script:
>>
>> xlog("L_NOTICE", "Before loose_route: $si -> $ru - $du\n");
>> xlog("L_NOTICE", "Before record_route: $si -> $ru - $du\n");
>> xlog("L_NOTICE", "After both: $si -> $ru - $du\n");
>>
>> Which generated the below output in syslog:
>>
>> Aug  2 09:46:11 ip-10-10-2-5 /sbin/kamailio[529]: NOTICE: 

Re: [SR-Users] Kamailio segmentation fault rpc request

[Daniel-Constantin Mierla]

Hello,

can you get the output of gdb commands:

bt full

info locals

Cheers,
Daniel


On 04/08/16 08:49, pars3c wrote:
> Hello ,
> i make many request toward jsonrpc server, using dlg.profile_list. Usually on 
> high load, kamailio crash .
> Last time in the dump, ther is :
> 0  0x7f25361cd00a in internal_rpc_profile_print_dlgs (rpc=0x7f25158db9a0, 
> c=0x7f25158db940, profile_name=0x7fffb5b5bb70, value=0x0)
> at dialog.c:1666
> 1666if ((!value || (STR_EQ(*value, 
> ph->value))) && ph->dlg) {
>
>
>
> Can someone helpme?
>
> Thanks
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://www.asipto.com - http://www.kamailio.org
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Kamailio + rtpengine + freeswitch

[Daniel-Constantin Mierla]

It will be helpful if you can provide a pcap with the network capture of
sip packets for such call taken on kamailio server. Then we can see if
rtp relaying was engaged or not.

Cheers,
Daniel


On 04/08/16 04:55, Kotb, Amir wrote:
>
> [03:50]  I have a small query, can anybody assist please?
> [03:51]  I am running kamailio + rtpengine on a google compute
> cloud instance
> [03:51]  have setup them to work with devices behind nat, and
> everything works
> [03:52]  no i have added freeswitch. but I don't know how to
> configure rtpengine to work with both
> [03:52]  when I use #!define with_nat
> and #!define with_freeswitch, I get no voice in the calls. When I
> remove, #!define with_freeswitch, everything works normally
>
> Best regards,
> Amir
>
> --
> *Amir KOTB*, Msc., Bsc.
>
> Postgraduate Researcher
> Department of Electrical Engineering & Electronics,
> *The University of Liverpool*,
> Brownlow Hill,
> Liverpool L69 3GJ,
> UK
>
> Mobile: _+44-(0) 7428844234_
> Email:  _a.k...@liverpool.ac.uk_
> Skype: _A.kotb1_
> Web:   _Http://uk.linkedin.com/in/AOKotb_
>
> Please consider the environment before printing this email
>
>
> ___
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users@lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
http://www.asipto.com - http://www.kamailio.org
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

[SR-Users] Kamailio segmentation fault rpc request

[pars3c]

Hello ,
i make many request toward jsonrpc server, using dlg.profile_list. Usually on 
high load, kamailio crash .
Last time in the dump, ther is :
0  0x7f25361cd00a in internal_rpc_profile_print_dlgs (rpc=0x7f25158db9a0, 
c=0x7f25158db940, profile_name=0x7fffb5b5bb70, value=0x0)
at dialog.c:1666
1666if ((!value || (STR_EQ(*value, 
ph->value))) && ph->dlg) {



Can someone helpme?

Thanks


___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Re: [SR-Users] Path & Loose Route

[Luke Milbourne]

Hi Daniel,

Thanks again for your reply again.

I remembered about the debug setting and done it yesterday, not at my pc
right now but I remember one of the log lines was saying "the topmost route
header is me".

Still trying to understand it, but will get a copy of the log lines for
you, if you wouldn't mind taking a look.

Thanks again,
Luke

On 4 Aug 2016 06:57, "Daniel-Constantin Mierla"  wrote:

Hello,

set debug=3 in kamailio.cfg and look at log messages in syslog.

If you find it too verbose, use dispatcher module and set debug level only
for core and rr modules to 3.
Cheers,
Daniel


On 03/08/16 13:22, Luke Milbourne wrote:

Hi Daniel,

I've added some more logging and can see loose_route() is returning -1 -
route calculation has been unsuccessful.

Is there a way of finding out why this is the case?

Kind regards,
Luke

On 2 August 2016 at 09:49, Luke Milbourne  wrote:

> I added the below xlog lines into my script:
>
> xlog("L_NOTICE", "Before loose_route: $si -> $ru - $du\n");
> xlog("L_NOTICE", "Before record_route: $si -> $ru - $du\n");
> xlog("L_NOTICE", "After both: $si -> $ru - $du\n");
>
> Which generated the below output in syslog:
>
> Aug  2 09:46:11 ip-10-10-2-5 /sbin/kamailio[529]: NOTICE: