Hello,
I have this scheme: SIP Carrier (external IP 22.203) < > (local ip 1.21)
mikrotik < > (local ip 1.21) Kamailio - (local ip 1.15) Asterisk.
Carrier does not know what is Route header. that is why Carrier send ACK
directly to 1.15 and fail.
I change Contact at Kamailio to 1.21 then ACK i
Hello,
I have this scheme: SIP Carrier (external IP 22.203) < > (local ip 1.21)
mikrotik < > (local ip 1.21) Kamailio - (local ip 1.15) Asterisk.
Carrier does not know what is Route header. that is why Carrier send ACK
directly to 1.15 and fail.
I change Contact at Kamailio to 1.21 then ACK i
El Mon, 22 Aug 2011 22:04:44 +0200
MÉSZÁROS Mihály escribió:
> Hi Daniel
>
> >>
> >> 1.
> >> modul purple is not compiled for me.
> >> hal:/usr/local/src/sip-router/modules_k/purple# make
> >> CC (gcc) [M purple.so] clientpipe.o
> >> In file included from purple.h:23,
> >> from clientpipe.c:28:
Hi Daniel
1.
modul purple is not compiled for me.
hal:/usr/local/src/sip-router/modules_k/purple# make
CC (gcc) [M purple.so] clientpipe.o
In file included from purple.h:23,
from clientpipe.c:28:
/usr/include/libpurple/status.h:93: error: expected
specifier-qualifier-list before ‘gpointer’
ma
Hello,
On 8/18/11 4:12 PM, MÉSZÁROS Mihály wrote:
Hi Daniel!
Thank You very much!
I tested it, and it seems to be working for me!
ok.
Only one typo what i corrected.
You have missed out the beginning " from your example.
if(method==ACK") sip_trace();
Thank you again!
By the way two pro
Hi Daniel!
Thank You very much!
I tested it, and it seems to be working for me!
Only one typo what i corrected.
You have missed out the beginning " from your example.
if(method==ACK") sip_trace();
Thank you again!
By the way two problems with git HEAD.
I checked out the current git HEAD, a
Hello,
I have committed the feature to be able to use sip_trace() from
onsend_route, therefore you can catch forwarded ACKs:
http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=9d8df2527d13878cee23af5b14f142a0cc4cd878
An example of usage would be:
onsend_route {
if(method=
Hi Daniel,
Thank you for looking after the issue.
Am I understand you correctly:
You mean that it couldn't be corrected (or it is not the right
solution) in TM to have a callback to messages what are sent out
stateless way, and correct the issue in this way.
So you mean I will have to
Hello,
ok, seems that there is no actual callback for outgoing ACK -- the same
seems to be in 1.x, based on a quick look there -- the callback for TM
outgoing requests is useless since the ACK is forwarded in stateless mode.
The great thing with 3.x is that we have onsend_route where the outg
Hello Daniel,
I appreciate highly your help!
Cheers,
Misi
2011-08-11 20:41 keltezéssel, Daniel-Constantin Mierla írta:
Hello,
I will look to see what happens with the outgoing ACK, probably
tomorrow or so. Btw, there is no need to apologize, here are open
discussions, reporting issues, thro
Hello,
I will look to see what happens with the outgoing ACK, probably tomorrow
or so. Btw, there is no need to apologize, here are open discussions,
reporting issues, throwing ideas, bad or good, the conclusion comes
after some analysis and help from the others. It's hard to know
everything
Hi Daniel,
I put on setflag before WITHINDLG,
so AFAIK the ACK as a new transaction is executing this step.
The root of my problem is that I can see the incoming E2E ACK, but i
couldn't see the "outgoing"!
route {
#pike flood detection
if (!pike_check_req()) { exit;
Hello,
E2E ACK is getting to configuration file routing block. With the latest
stable version default config file, it is handled in the route[WITHINDLG].
Be sure you call sip trace function there. This will capture the incoming
E2E ACK. For outgoing version, set the flag and it should be captured
Hi,
I want to see all incoming and outgoing sip messages in sip trace table,
but i am missing messages.
I am using TLS so i can't see really trace the conversation only this way.
I am wondering if it is know limitation, or an issue:
I am experiencing that E2E ACK is not logged in siptrace tabl
14 matches
Mail list logo