there is something strange on the cfg - please confirm if there is any traffic on loopback interface (messages looping on the proxy).
as the reply shows:
U 62.116.32.102:5060 -> 62.163.103.30:5060 SIP/2.0 407 Proxy Authentication Required..Via: SIP/2.0/UDP 192.168.0.144:5060;received=62.163.103.30;rport=5060;branch =z9hG4bK1888503047..From: sip:gst@sysfrog.org;tag=1481684668..To: sip:00434635361588@eris.sysfrog.org;tag=329cfeaa6 ded039da25ff8cbb8668bd2.4990..Call-ID: 827989729@192.168.0.144..CSeq: 21 INVITE..Proxy-Authenticate: Digest realm="sysf rog.org", nonce="4422d70719ab3dcb1ff421f74a7a9cbefc3dd47a"..Server: OpenSer (1.1.0-dev16 -tls (i386/linux))..Content-Le ngth: 0..Warning: 392 62.116.32.102:5060 "Noisy feedback tells: pid=16521 req_src_ip=62.116.32.102 req_src_port=5060 i n_uri=sip:00434635361588@eris.sysfrog.org out_uri=sip:00434635361588@eris.sysfrog.org via_cnt==2"....
it was indeed created by openser, but as via_cnt=2 and req_src_ip=62.116.32.102 shows, the request cycled on lo.
my guess in that the original request was parallely forked to the PSTN GW and back to the proxy. GW send 401 and proxy 407.
please check this out.
regards, bogdan
Günther Starnberger wrote:
On Fri, Mar 24, 2006 at 12:39:51PM +0200, Bogdan-Andrei Iancu wrote:
Hi,
it's very difficult to formulate an opinion without a network trace. Please post it somewhere in order to take a look.
Both problems which I described occur in the same dump file: http://gst.sysfrog.org/openser/ngrep1.txt
bye, /gst