Am 06.07.2010 18:47, schrieb David:
Hey,
It's sent when I hit the red button on the phone ( hang up ). It's not
automated.
So I think there is no solution within Kamailio to work around the bug
in the phone. You would need to modify tm module to send delayed CANCEL
not after 100 trying, bu
Am 06.07.2010 20:03, schrieb inge:
I quickly tried this but I cannot used "exec" within the onreply_route.
So the problem stay the same. I don't know how to execute my script only
on established calls...
Upgrade to 3.0 ;-)
regards
klaus
___
SIP E
All,
I have SER sitting in front of Asterisk.
It is useful to me for Call Forking purposes as I do not think Asterisk handle
multiple registered endpoints (against a single username)
However, since both SER and Asterisk are Registrars, and Asterisk need to know
register info to work properly, I
Which version off asterisk do you have Lucas?
Ernest
On 07. 07. 2010 09:37, rupert.or...@bt.com wrote:
All,
I have SER sitting in front of Asterisk.
It is useful to me for Call Forking purposes as I do not think Asterisk handle multiple registered endpoints (against a single username)
How
Hi,
My script is almost done.
I am wondering how weights are calculated in order to choose proper gws list.
For this test I've modified gw table in following way (the same weights).
LCR table points to grp_id=1.
++--+++--+--+
Maciej Bylica writes:
> So it means that weights are calculated different way, not directly
> and only according to weight column.
it is weight column, not priority column. weight gives a probability of
the gw being chosen from among gws of the same group.
-- juha
_
2010/7/6 Lucas Alvarez :
> Iñaki, if you don't know the answer, please don't answer with trash,
You can consider "trash" my response as I can consider "trash" your question.
> my question is all related with kamailio, is an integration of two
> software, since kamailio forward the registrations
Juha,
> it is weight column, not priority column. weight gives a probability of
> the gw being chosen from among gws of the same group.
What other parameters are taken into account while defining probability?
Is that means, that to achieve 100% predictable "routing" (not to
count on probability)
On 07/06/2010 05:44 PM, Lucas Alvarez wrote:
Thank you Michael for you answer, but does kamailio have any method to
resend all the registrations again?
No. Kamailio is just a proxy in the scenario you are describing; all
it can do is act on SIP messages it receives by forwarding them to the
Maciej Bylica writes:
> > it is weight column, not priority column. weight gives a probability of
> > the gw being chosen from among gws of the same group.
>
> What other parameters are taken into account while defining probability?
> Is that means, that to achieve 100% predictable "routing" (no
Juha,
> as you see in above, there is priority column in lcr table. use that
> and arrange so that each gw group has only one gw. then you will be
> sure in which order gws are tried.
Thanks a lot for Your help.
Maciej.
___
SIP Express Router (SER) a
On 07/07/2010 03:37 AM, rupert.or...@bt.com wrote:
I have SER sitting in front of Asterisk.
It is useful to me for Call Forking purposes as I do not think
Asterisk handle multiple registered endpoints (against a single username)
You are correct.
However, since both SER and Asterisk are Regis
Hey,
I have setup two Kamailio servers, my INVITEs will go through server A,
which forwards to server B which forwards it back to server A.
This is intential, the trouble is when the packet comes back through
server B, nothing has changed so TM sees it as a retransmission.
The difference be
Yes, why not, but in a few moment ;)
Does SER 3.0 released ? In the siprouter project ?
Le mercredi 07 juillet 2010 à 09:17 +0200, Klaus Darilion a écrit :
>
> Am 06.07.2010 20:03, schrieb inge:
> > I quickly tried this but I cannot used "exec" within the onreply_route.
> >
> > So the problem s
Hey guys,
I'm using Kamailio 1.5.3-notls and need to apply some re operation to an AVP.
The problem I have is that my re expression is held in an AVP, so the
parser is not recognizing it :(
Would it be very hard to change that behavior? Any ideas/tips to implement?
This code
route[16]
{
Hi,
David wrote:
> I have setup two Kamailio servers, my INVITEs will go through server A,
> which forwards to server B which forwards it back to server A.
>
> This is intential, the trouble is when the packet comes back through
> server B, nothing has changed so TM sees it as a retransmission.
Hey,
I do not do anything IP level forwarding. All my forwarding is done
using Kamailio. It looks like what I am doing is called hairpin routing.
Thanks,
David
On 2010-07-07 18:48, Timo Reimann wrote:
Hi,
David wrote:
I have setup two Kamailio servers, my INVITEs will go through serv
17 matches
Mail list logo
