[Partysip-dev] X-Ten Client bypasses partysip

[Walter Schober]

Hi!

When partysip sends a INVITE to the X-Ten Client, this client answers
with TRYING and/or OK, but to the first proxy in the chain. 

2 things:

X-Ten Client = 192.168.3.232:5061
PartySIP = 192.168.3.2
Other Proxy = 192.168.3.34

1) PartySIP is configured with record-route on, but I miss the
Record-Route Field in the outgoing message. Shouldn't be there a 
Record-Route: <sip:192.168.3.2:5060;lr>
behind the other?

INVITE sip:address@hidden:5061 SIP/2.0
Via: SIP/2.0/UDP
192.168.3.2:5060;branch=z9hG4bKf2731eabe5f901b4e7fd99f175013c7dc.0
Via: SIP/2.0/UDP 192.168.3.34:5060;branch=z9hG4bK~w8s7VLP0xz-gOv
Via: SIP/2.0/UDP 192.168.3.232:5060;branch=z9hG4bKJW5uN3KePuCGLLp
Record-Route: <sip:192.168.3.34:5060;lr>
From: Walter Schober <sip:address@hidden:5060>;tag=!.X5daDBVFcrGFM
To: <sip:address@hidden>
Call-ID: address@hidden
CSeq: 1 INVITE
Contact: Walter Schober <sip:address@hidden:5060>
max-forwards: 68
Content-Type: application/sdp
Content-Length:   173

2) The X-Ten sends the 100 Trying message back to the first proxy! So
PartySIP retries and never get's an answer. Shouldn't X-Ten always send
the message to it's outbound proxy, which is partysip?

Message received on other proxy:
09-15-03 16:30:57 [6151] INFO network <> - > in UDP from
192.168.3.232:50451: SIP/2.0 100 Trying
09-15-03 16:30:57 [6151] DEBUG transport <> - Packet received:
SIP/2.0 100 Trying
Via: SIP/2.0/UDP
192.168.3.2:5060;branch=z9hG4bKf2731eabe5f901b4e7fd99f175013c7dc.0
Via: SIP/2.0/UDP 192.168.3.34:5060;branch=z9hG4bK~w8s7VLP0xz-gOv
Via: SIP/2.0/UDP 192.168.3.232:5060;branch=z9hG4bKJW5uN3KePuCGLLp
From: Walter Schober <sip:address@hidden:5060>;tag=!.X5daDBVFcrGFM
To: <sip:address@hidden>;tag=950151882
Contact: <sip:address@hidden:5061>
Record-Route: <sip:192.168.3.34:5060;lr>
Call-ID: address@hidden
CSeq: 1 INVITE
User-Agent: X-Lite build 1059
Content-Length: 0

Your comments appreciated!

Rgds,
Walter