I have a BLF configured on SPA514G as "fnc=blf+sd+cp;sub=201@$proxy".
The proxy forwards SUBSCRIBE to our presence server.
The "200 OK" on SUBSCRIBE and the NOTIFY to SPA contains record-route.
When the SPA re-SUBSCRIBE, it sends directly to the presence server from contact header.
The route header is correct.
The PROXY is dual-homed:
192.168.3.15 -> 192.168.3.3 --- 192.168.2.3 -> 192.168.2.5
SPA514G ---------------- PROXY -------------- PRESENCE
I've tested firmware 7.5.6a and 7.5.2b.
Partial trace:
192.168.3.15:5060 -> 192.168.3.3:5060
SUBSCRIBE sip:201@sip.domain SIP/2.0
Via: SIP/2.0/UDP 192.168.3.15:5060;branch=z9hG4bK-6df8985a
From: "Cisco" <sip:215@sip.domain>;tag=2d763ae2f27077d6
To: <sip:201@sip.domain>
Contact: "Cisco" <sip:215@192.168.3.15:5060>
Event: dialog
User-Agent: Cisco/SPA514G-7.5.2b
192.168.3.3:5060 -> 192.168.3.15:5060
SIP/2.0 200 OK
Record-Route: <sip:192.168.2.3;r2=on;lr;ftag=2d763ae2f27077d6>
Record-Route: <sip:192.168.3.3;r2=on;lr;ftag=2d763ae2f27077d6>
Via: SIP/2.0/UDP 192.168.3.15:5060;rport=5060;received=192.168.3.15;branch=z9hG4bK-6df8985a
From: "Cisco" <sip:215@sip.domain>;tag=2d763ae2f27077d6
To: <sip:201@sip.domain>;tag=57902af3e183b228161407cf3808f4bc-81e5
Contact: <sip:192.168.2.5:5060>
192.168.3.3:5060 -> 192.168.3.15:5060
NOTIFY sip:215@192.168.3.15:5060 SIP/2.0
Record-Route: <sip:192.168.3.3;r2=on;lr;ftag=57902af3e183b228161407cf3808f4bc-81e5>
Record-Route: <sip:192.168.2.3;r2=on;lr;ftag=57902af3e183b228161407cf3808f4bc-81e5>
Via: SIP/2.0/UDP 192.168.3.3;branch=z9hG4bK06a2.97fdfb93.0
Via: SIP/2.0/UDP 192.168.2.5:5060;rport=5060;branch=z9hG4bK06a2.6e6e2853.0
To: <sip:215@sip.domain>;tag=2d763ae2f27077d6
From: <sip:201@sip.domain>;tag=57902af3e183b228161407cf3808f4bc-81e5
Event: dialog
Contact: <sip:192.168.2.5:5060>
Subscription-State: active;expires=180
Content-Type: application/dialog-info+xml
192.168.3.15:5060 -> 192.168.3.3:5060
SIP/2.0 200 OK
To: <sip:215@sip.domain>;tag=2d763ae2f27077d6
From: <sip:201@sip.domain>;tag=57902af3e183b228161407cf3808f4bc-81e5
Via: SIP/2.0/UDP 192.168.3.3;branch=z9hG4bK06a2.97fdfb93.0
Via: SIP/2.0/UDP 192.168.2.5:5060;rport=5060;branch=z9hG4bK06a2.6e6e2853.0
Record-Route: <sip:192.168.3.3;r2=on;lr;ftag=57902af3e183b228161407cf3808f4bc-81e5>
Record-Route: <sip:192.168.2.3;r2=on;lr;ftag=57902af3e183b228161407cf3808f4bc-81e5>
192.168.3.15:5060 -> 192.168.2.5:5060 <--------- Should use PROXY (192.168.3.3)
SUBSCRIBE sip:192.168.2.5:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.3.15:5060;branch=z9hG4bK-f35b1d45
From: "Cisco" <sip:215@sip.domain>;tag=2d763ae2f27077d6
To: <sip:201@sip.domain>;tag=57902af3e183b228161407cf3808f4bc-81e5
Route: <sip:192.168.3.3;r2=on;lr;ftag=2d763ae2f27077d6>, <sip:192.168.2.3;r2=on;lr;ftag=2d763ae2f27077d6>
Contact: "Cisco" <sip:215@192.168.3.15:5060>
Event: dialog
