> On 10 Feb 2021, at 21:01, Juha Heinanen wrote:
>
> When request is sent from Kamailio to MS Teams SIP Proxy, the top R-R
> URI needs to contain FQDN of Kamailio SIP proxy instead of its IP
> address. Document
>
> https://skalatan.de/de/blog/kamailio-sbc-teams
>
> suggest to replace
On 10.02.21 21:01, Juha Heinanen wrote:
> When request is sent from Kamailio to MS Teams SIP Proxy, the top R-R
> URI needs to contain FQDN of Kamailio SIP proxy instead of its IP
> address. Document
>
> https://skalatan.de/de/blog/kamailio-sbc-teams
>
> suggest to replace record_route();
Dear List
Hope this email finds you all well.
I have followed the below tutorial on how to integrate Kamailio with MS
Teams
https://skalatan.de/en/blog/kamailio-sbc-teams
However i have been facing an issue with MS Teams with direct routing where
MS Teams does not send back an ACK after a 200
When request is sent from Kamailio to MS Teams SIP Proxy, the top R-R
URI needs to contain FQDN of Kamailio SIP proxy instead of its IP
address. Document
https://skalatan.de/de/blog/kamailio-sbc-teams
suggest to replace record_route(); call with
Hi
I have setup failover on Kamailio 5.1 using Dispatcher module as below. On a
round robin algorithm, INVITEs are being sent to BOTH healthy and faulty GW.
When an INVITE is being sent to the faulty GW, a re-transmission will be sent
after "t_set_fr" time to the healthy GW and calls are
mmm smart... trying...
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
On Wed, Feb 10, 2021 at 7:50 PM Alex Balashov
wrote:
> Have you tried drop()ping the end-to-end `487 Request Terminated` reply
> from upstream in a failure_route, and then send_reply()
Thanks for the link! Was exactly what I was looking for.
On Wed, Feb 10, 2021 at 4:08 PM Alex Balashov
wrote:
>
> On 2/10/21 8:50 AM, Mihai wrote:
>
> > the $fd has the value: asterisk-wind.voicevw.lan; and i want to take
> > the the first part - asterisk-wind
>
> Sure!
>
> Have a look at
Have you tried drop()ping the end-to-end `487 Request Terminated` reply
from upstream in a failure_route, and then send_reply() in its place?
-- Alex
On 2/10/21 2:43 PM, David Villasmil wrote:
Actually I already implemented that timeout, I haven’t asked about that,
because I didn’t have any
Actually I already implemented that timeout, I haven’t asked about that,
because I didn’t have any problems with that one.
I am being asked for that “if a 180 comes within 0.8 seconds, cancel the
call and send a 480 to the origination.
The cancel I got it working thanks to your help. Sending
Wouldn’t it make more sense to just have an aggressive timeout for the “keeping
it there” aspect?
That is, if, upon receipt of a non-100 1xx message, a final dispositive reply
does not follow within X seconds, route-advance to the next provider? This can
be accomplished with the
Some providers have other providers which many times just answer the call
and try to keep it there. It’s a known strategy some scammers use. Getting
a 180/3 in say; 500ms (to a real-life hard line, is probably one such call.
On Wed, 10 Feb 2021 at 18:52, Raúl Alexis Betancor Santana <
What is the point of refusing a call that answer with a 100/183 "too quickly" ?
... I don't get the point on that.
Saludos
--
Raúl Alexis Betancor Santana
Serlink Telecom S.R.L.U.
De: "David Villasmil"
Para: "Kamailio (SER) - Users Mailing List"
Enviados: Miércoles, 10 de Febrero 2021
Hi,
Here is some more information about my problem.
I think that topos impacts challenge computing.
Do you have the same behaviour I observed? Do you need more information?
My tests were done with kamailio 5.4.3 on Centos7
Without topos activated (note that with topoh activated I have the same
On 2/10/21 8:50 AM, Mihai wrote:
the $fd has the value: asterisk-wind.voicevw.lan; and i want to take
the the first part - asterisk-wind
Sure!
Have a look at Kamailio's equivalent of a .split() method:
https://www.kamailio.org/wiki/cookbooks/5.4.x/transformations#sselect_index_separator
Have a look at
https://www.kamailio.org/wiki/cookbooks/devel/transformations#sselect_index_separator
On Wed, Feb 10, 2021 at 8:51 AM Mihai wrote:
> Hi!
>
> Can I split the variable $fd ?
>
> the $fd has the value: asterisk-wind.voicevw.lan; and i want to take the
> the first part -
Hi!
Can I split the variable $fd ?
the $fd has the value: asterisk-wind.voicevw.lan; and i want to take the
the first part - asterisk-wind
any hints ?
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
Vars are actually per-process, which makes them both useless in a transactional
context beyond the life of any particular message, and dangerous because they
instead persist in a given worker process, so it’s very easy to forget to reset
them from previous values. They bring lots of surprises.
oh damn, that's true.. Alex pointed it out earlierm thanks!
Also,
On sending the CANCEL to the b-leg, I need to immediately send a 480 to the
a-leg, not sure this is at all possible?
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
On Wed, Feb 10, 2021 at
Hi,
var(s) are kind of static variables per process.
You'd rather use an avp (which is bound to the transaction) to be able to
use it in a reply route.
Cheers,
Federico
On Wed, Feb 10, 2021 at 1:55 PM David Villasmil <
david.villasmil.w...@gmail.com> wrote:
> I eneded up adding topos, hiding
I eneded up adding topos, hiding everything behind seems to make them happy.
I do have a small problem storing the current time in a var.
When the a-leg invite comes in, i'm creating a
$var(invite_time) = $TV(Sn);
on the dispatch route, when i try to use it on the reply from the b-leg,
it's 0.
Well, the vendor just can’t have everything it wants. :-) There are limits to
what Kamailio can do.
—
Sent from mobile, with due apologies for brevity and errors.
> On Feb 10, 2021, at 6:35 AM, David Villasmil
> wrote:
>
>
> Ah that's it, thanks!
> But the vendor wants us to set the FROM
Ah that's it, thanks!
But the vendor wants us to set the FROM header domain to our IP, i don't
see this possible with tmx on the CANCEL?
Regards,
David Villasmil
email: david.villasmil.w...@gmail.com
phone: +34669448337
On Wed, Feb 10, 2021 at 11:21 AM Daniel-Constantin Mierla
wrote:
> Hello,
Hello,
replied to the other email on the topic of the last question here, but
for sake of having it in the archive of this thread as well, in case
people end up here by web searching: look at tmx module, it has some
cancel-related functions.
Cheers,
Daniel
On 10.02.21 10:57, David Villasmil
Hello,
look at tmx module, it has some cancel-related functions.
Cheers,
Daniel
On 09.02.21 18:03, David Villasmil wrote:
> Hello,
>
> When receiving a reply, there's a logic which if true, i must cancel
> the outgoing invite (can 480 the origination). I tried using something
> like
>
>
Hello Alex,
Again thanks.
I'm using that calculation to, when receiving a 180/3, if it comes in too
quickly (i.e. 100ms) i cancel that call, and send a 480 the the A leg.
I haven't found way of doing this, is this possible at all? I trired
setting a very low t_set_fr(10,10) (0 means set the
Hello,
the PR was adding a new feature, even more, it adds a new column to the
database table, so definitely doesn't qualify for backporting to a
stable branch. It will be part of the future stable release series 5.5.x.
Cheers,
Daniel
On 10.02.21 03:06, Sergiu Pojoga wrote:
> Well, I'd like to
Hi,
just tested on latest 5.4 (ubuntu 20.04, curl 7.68.0) and http_rr works as
expected, returning the reason phrase.
Can you give some more detail and maybe run a test with increased debug
level?
Regards,
Federico
On Wed, Feb 10, 2021 at 4:14 AM Anthony Joseph Messina <
amess...@messinet.com>
27 matches
Mail list logo
