22 May
2007
22 May
'07
7:10 p.m.
Klaus,
I used to suspect the remote IP-PBX, after we test without this IP-
PBX, we get the same result.
I will collect the packet for remote site BYE later.
But I saw the Proxy2 remove the info from route header and put it in
SIP URI, it makes the proxy has no where to go.
And the BYE URI is sip:1.2.3.4:5060;nat=yes;ftag=ooqjvbi7ql;lr=on,
it is exactly the same with record_route which is generated by itself
for ist Invite relay out to next hop.
regards
Chilly
在 2007/5/22 下午 10:39 時，Klaus Darilion 寫到：
wrote:
----Called party hangup
BYE sip:1.2.3.4:5060;nat=yes;ftag=ooqjvbi7ql;lr=on SIP/2.0
Record-Route: <sip:5.6.7.8;lr=on;ftag=as1b41fbeb>
Record-Route: <sip:5.6.7.8;lr=on;ftag=as1b41fbeb>
Via: SIP/2.0/UDP 5.6.7.8;branch=z9hG4bKc74c.bd89ce13.0
Via: SIP/2.0/UDP 5.6.7.8;branch=z9hG4bKc74c.ad89ce13.0
Via: SIP/2.0/UDP 16.3.0.100;branch=z9hG4bKc74c.321ef5e3.0
Via: SIP/2.0/UDP 163.30.0.199:5060;branch=z9hG4bK75e8d6f3;rport=5060
From: <sip:0908900000@sip.edu;user=phone>;tag=as1b41fbeb
To: "0709802020 kl" <sip:0709802020@sip.edu>;tag=ooqjvbi7ql
Call-ID: 3c275da915f9-iylvmp2wjuh0@snom360-00041323058B
CSeq: 102 BYE
User-Agent: Gentrice_IPPBX
Max-Forwards: 67
Content-Length: 0
This looks strange. It looks like a BYE which was already looped one
time. I suspect the Gentrice_IPPBX behaves strange.
For confidence, I need to see the BYE from caller to proxy3 and the
BYE
from proxy3 to proxy2.
regards
klaus