18 May
2007
18 May
'07
12:46 p.m.
Hi Taylor,
The ACK generated by the UAC is totally bogus: different From TAG and
different CSEQ than in INVITE. That prevents openser to match the ACK to
the INVITE transaction - in this case, the ACK will be simply fwded
based on RURI (instead of being absorbed).
regards,
bogdan
Taylor Carpenter wrote:
I am getting a ACK loop after receiving a 404 from a
remote GW. I am
starting the call using sipp for testing.
sipp -r 1 -l 1 -d 5000 -s 8989 -p 5061 -sn uac 10.14.18.22
The ngrep trace is showing Via and From set to 127.0.0.1 for the
communication between OpenSER and the sipp system. The ngrep output and
the routes from the openser.cfg are at
http://pastebin.ca/493807
I assume the Via/From being set to 127.0.0.1 may be the issue, which I
assume I could change from sipp, but I would also like OpenSER to catch
the loop.
Taylor
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users