On Thursday 17 January 2008 18:46:17 Peter P GMX wrote:

the 302 message is as follows

In this case it answers per UPD as I explained before when OpenSER T 10.10.2.13:5060 -> 10.10.2.24:27838 [AP] SIP/2.0 302 Moved Temporarily FROM: "6005"sip:6005@my.openser.de;tag=4b086b07;transport=UDP TO: sip:11111@my.openser.de;transport=UDP;tag=9cca2fa224 CSEQ: 2 INVITE CALL-ID: NjQxNjk3ZDczZDkzN2ZmMzI5MzdiNzhkMzdmZTg0YzM MAX-FORWARDS: 70 VIA: SIP/2.0/TCP 10.10.2.24;branch=z9hG4bK3e88.e9631885.0,SIP/2.0/UDP 10.5.3.22:5060;received=82.135.xx.xxx;branch=z9hG4bK-d8754z-be756d81d31da41 9-1---d8754z-;rport=5060 CONTENT-LENGTH: 0.. SERVER: RTCC/2.0.6017.0..CONTACT: sip:11111@10.10.2.13:5065;transport=UDP

Hi, you say: "In this case it answers per UPD as I explained before when OpenSER" but it's not true, it's TCP, note the "T": T 10.10.2.13:5060 -> 10.10.2.24:27838 [AP]

BTW, could you please capture the trace using ngrep with this syntax?:

~# ngrep -d any -P ' ' -W byline -T -t "" port 5060 or port 5065 or port...