9 Dec
2008
9 Dec
'08
10:29 a.m.
The problem is concurrency:
process process process
3456 3449 3447
| | |
1. receive | |
INVITE | |
| | |
| | |
2. forward | |
INVITE | |
| | |
| 3.receive 180 |
| | |
| | |
| 4.forward 180 |
| | |
| 5. cleaning up |
| | |
| | 6.receive 200
| | |
| | 7.forward 200
| | |
| | 8. cleaning up
| | |
| | |
| | |
9.set | |
retransmit | |
timer | |
| | |
10.cleaning up | |
| | |
I have reported a similiar issue some time ago:
http://lists.kamailio.org/pipermail/devel/2008-September/016018.html
regards
klaus
Aurelien Grimaud schrieb:
As a matter of fact, I already checked this.
There is a reply route set before t_relay, and log outputs in it.
The log line is well seen on 180 and on 200.
This does not avoid retransmission.
Here is a log file with much trace for a call that was answered but
retransmitted.
on an INVITE, a module of mine is collecting all contacts for a serial
forking.
an on_reply_route is set, with a trace of mine in it
My log format is :
T000 [date] [time] bin#ser#<pid>#-1 = <log>
This was on a 1 call only.
I cannot figure out what is happening.
Any comment is welcome.
Thanks !
Aurelien