Thanks for your suggestions! I guess I have been too much involved in B2BUA
that I forgot how a proxy should work. After some digging around in the RFC
I fixed my sipp scripts (for reference herunder) Also the SIP trace.
U 10.57.26.219:5060 -> 10.57.26.220:5060
INVITE sip:service@10.57.26.220:5060
Wim,
Looks like your ACK is missing the Route header, since ACK is a new
transaction kamailio needs to route it based on a preloaded route. When
you receive the 200OK in sipp you should save the record route set and
use it in the ACK with the "[routes]" statement.
Take a look at the SIPP doc
Hi Wim,
Check this:
Dec 15 15:12:02 DNS-enum-8Gb-3 kamailio[6864]: 1(6883) DEBUG: tm
[t_lookup.c:485]: matching_3261(): DEBUG: *RFC3261 transaction matching
failed*
Maybe is related rrs. Add it to your sipp scenarios.
Diego
2016-12-15 11:13 GMT-03:00 Wim Van Cauwenbergh :
> Hi, I
Hi, I have setup kamailio with the dispatcher module and have a problem
with the ACK in response to 200OK not being forwarded by kamailio:
Scenario is very simple:
sipp(.219) --> kamailio (.220) --> sipp(.239)
SIP trace:
root@DNS-enum-8Gb-3:/var/log# ngrep -W byline -d eth0 port 5060
interface:
