Hello,
I want to announce the availability of an ebuild for version 3.2.1 on
Gentoo Portage Overlays.
Here the git link:
http://goo.gl/JXLQ4
The unofficial overlays portage website:
* http://gpo.zugaina.org/net-misc/sip-router
Remember this is not an official ebuild, and neither it's not at official
gentoo portage tree.
Henning, can you add/update it at sip-router git repository
(pkg/ser/gentoo)?
Thank you and best regards,
Claudio
Hi,
I'm new to kamailio, have some questions here hope anyone can help!
Question 1,
I'm trying to use some of the functions in usrloc module, but for some reason if I use those from "Available Functions" part, the kamailio won't start and give an error of "unknown command <ul_get_ucontact>, missing loadmodule?"
The usrloc module is definitely loaded, and it will start as long as I avoid using those "Available Functions". I tried some other modules it will lead to same error.
Question 2,
What is the simplest way to bridge a call based on username and domain?
I was trying to make a simple experiment I used to do in Freeswitch,
==========================
Have 1000,1001,1002 registered,
When 1000 calls 9999, the calls will be bridged to 1001 or 1002 based on different time period.
==========================
While in Freeswitch, it would be as simple as "bridge xxxx(a)domain.com", and then freeswitch will lookup contact information and forward the call.
But in kamailio, I only succeed in forwarding calls by change the $du to the exact contact uri, which is "sip:xxxx@ip-of-the-phone:port", the call r_relay(). In order to do this, I need call a perl script to lookup the location database to find a match…
I'm 99% sure I'm doing wrong here… there must be a way way easier than that, but so far I can't find it….
Please help…
Thanks,
Xi
Hello everyone, I'm new here and I go to test my settings, but I need to
authenticate a remote server, I was reading about the UAC module, one
has configuration examples? I can also customize the user_agent
authentication, because the service only allows specific user_agents?
Thanks in advance!
Regards, Doug
Hi man, I have the same problem like you posted in sip-router.org. The
problem is that :
rc_avpair_new: unknown attribute 5
I see that u have already resolved that problem before. So can u help me to
fix it.
Thank you very much.
Please contact me follow these emails : ducdung0909(a)yahoo.com or
ducdung0909(a)gmail.com .
> On 01/16/2012 09:11 PM, JR Richardson wrote:
>
> > So my question; what is the difference between a drop; and exit;
> > within the on_reply route
>
> Remember that an onreply_route is a callback that allows you to
> intercept a reply, but the reply is forwarded by default afterward (if
> using stateful forwarding). This is different from a request route,
> where it's up to you to marshal everything, and to explicitly forward
> the message.
>
> Thus, exiting an onreply_route has null effect. It doesn't do
> anything to stop the reply from being forwarded, because forwarding is
> the behaviour--the onreply_route is just a hook. In contrast, 'drop'
> explicitly drops the message and prevents further forwarding of the
> reply from taking place.
>
> This is different than in a request route, where exiting precludes any
> forwarding action, because forwarding action must be taken explicitly
> -- e.g. t_relay().
>
> --
> Alex Balashov - Principal
Aaaah, concise explanation, once again, thanks for turning on the light bulb
Alex.
JR
I'm trying to arm the failure route for a message sent via uac_req_send
- similar to:
{
$uac_req(method)="OPTIONS";
$uac_req(ruri)="sip:kamailio.org";
$uac_req(furi)="sip:kamailio.org";
$uac_req(turi)="sip:kamailio.org";
t_on_failure("UAC_FAIL");
uac_req_send();
}
failure_route("UAC_FAIL") {
xlog ......
}
If there is no response from the remote server, kamailio resends until
the timers expire; but the failure route is not run. Similarly, if a
404 is sent back from the remote server, the failure route is not run.
Am I missing something obvious?
Thanks
Hi,
i use the dialog module.
i create the dialog using dlg_manage() right after the invite is recieved.
in a case where the final destination rejects the call (486 busy), i get
the following error:
" WARNING: dialog [dlg_handlers.c:1054]: unable to find dialog for ACK with
route param....."
i guess the dialog module deletes the dialog on the 486 reply and gives me
this erro when an ACK for the 486 is recieved from the caller...
no a bug issue, but, is there a way to overcome it?
thanks,
Uri
Hi,
If I am using IP address, I have no problems. If I use domain name
(pointing to same IP address) then phones do not register.
I have couple of hardware and software SIP phones and when I put name of
domain (stribogkonsult.com) - then no registration, if I put IP - no
problems.
I put IP, and names in domain table.
Effect is - when I use domain name, there are bulk of messages in syslog -
like messages reenter kamailio again and again.
xlog("Auth attemps $au\n"); - I receive many times if I use domain name, if
I use IP - once only.
Problem can be somewhere else of course. But everything else work as I
expect.
route[AUTH] {
#!ifdef WITH_AUTH
if (is_method("REGISTER"))
{
if (!www_authorize("$td", "subscriber"))
{
xlog("RegisterChalange $au $td\n");
www_challenge("$td", "1");
exit;
}
if ($au!=$tU)
{
sl_send_reply("403","Forbidden auth ID");
exit;
}
xlog("Auth attemps $au\n");
} else {
#!ifdef WITH_IPAUTH
if(allow_source_address())
{
# source IP allowed
return;
}
#!endif
# authenticate if from local subscriber
if (from_uri==myself)
{
xlog("Register MySelf\n");
if (!proxy_authorize("$fd", "subscriber")) {
proxy_challenge("$fd", "0");
exit;
}
if (is_method("PUBLISH"))
{
if ($au!=$fU || $au!=$tU) {
sl_send_reply("403","Forbidden auth ID");
exit;
}
if ($au!=$rU) {
sl_send_reply("403","Forbidden R-URI");
exit;
}
} else {
if ($au!=$fU) {
sl_send_reply("403","Forbidden auth ID");
exit;
}
}
consume_credentials();
# caller authenticated
} else {
# caller is not local subscriber, then check if it calls
# a local destination, otherwise deny, not an open relay here
if (!uri==myself)
{
sl_send_reply("403","Not relaying");
exit;
}
}
}
#!endif
return;
}