hi
The cause :
the Asterisk in KVM - had no voice during internal calls, so no RTP from
Asterisk - and no Kernalizing ( no RTP packets were seen from Asterisk so the
RTPENGINE daemon did not send a command to kernalize.
On Monday, June 6, 2016 2:42 PM, Dmitry
Hi!
Instead of function from utils module, it is better to use newer from here:
http://kamailio.org/docs/modules/4.4.x/modules/http_client.html
ore here:
http://kamailio.org/docs/modules/4.4.x/modules/http_async_client.html
hope this is helpful!
cheers
--
View this message in context:
Hi guys
i am bridging call on a private ip asterisk behind kamailio/rtpproxy
i am calling rtpproxy with the route [FROMASTERISK]
route[FROMASTERISK] {
if(ds_is_from_list()){
xlog("L_INFO","$dd Call from Media-Server Cluster\n");
rtpproxy_manage("cawei");
SIP INVITE with sdp always
exactly the same error!
just disabling "#!define WITH_TLS" and start immediately with "kamailio -m 64"
or "kamctl start"
may help re-compile openssl from scratch (i installed from .rpm)? any specific
version? openssl-1.0? openssl-0.98?
Regards,
On 14 June 2016 16:03:30 CEST,
Hi Daniel,
But when Kamailio receives a CANCEL prints the following error messages:
2016-06-15 14:39:10.354 ERROR: tm [t_msgbuilder.c:287]:
build_local_reparse(): ERROR: build_local_reparse: INVITE is missing
2016-06-15 14:39:10.354 ERROR: tm [t_msgbuilder.c:494]:
build_local_reparse(): ERROR:
Hello,
On 14/06/16 16:33, José Seabra wrote:
> Hi Olle and Daniel,
> Thank you for your replies, After receive your msg I looked again to
> my script and i found the problem.
>
> I didn't configure the correct failure_route block and the failure
> route configured didn't print any msg on the
Hi!
While REGISTER processing, lookup(location) is not what you need to call
lookup - have to be used, e.g. while INVITE processing, when you need to
find location of registered user, to send him INVITE.
about name in RURI, if you are talking about REGISTER - it is specific
message, and RURI in
That depends on when you want to trigger the notification. The easiest thing to
do would be to trigger it when one party sends a BYE. The best place to do this
would probably be after you have relayed the BYE to the UA (in the RELAY route
after the t_relay() call). This seems most logical as
This was asked on the mailing list earlier in the day yesterday. I’m presuming
you only just subscribed. See this topic on the archive for info -
http://lists.sip-router.org/pipermail/sr-users/2016-June/093348.html
Phil
From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of