Hi thanks I think that has actually done the job and the firmware appears to be better as I had a beta version. I will test the incoming calls now to see if they actually can get transfered and let you know.
Sara.
--------------------------------------------------------------------------------
Sent to tls:192.168.1.3:5061 at 20/9/2007 22:15:33:929 (547 bytes):
REGISTER sip:192.168.1.3 SIP/2.0
Via: SIP/2.0/TLS 192.168.1.6:1025;branch=z9hG4bK-tml41bj696i3;rport
From: "PBX Gateway" <sip:200@192.168.1.3>;tag=ezdw7g6xl2
To: "PBX Gateway" <sip:200@192.168.1.3>
Call-ID: 3c26702ac79f-0h495mvgwdbu
CSeq: 1 REGISTER
Max-Forwards: 70
Contact: <sip:200@192.168.1.6:1025;transport=tls;line=zq5p1hzm>;q=1.0;flow-id=1;+sip.instance="<urn:uuid:38070bbf-d2cf-4420-90d0-b950ac8255f3>"
User-Agent: snom370/7.1.19
Supported: gruu
Allow-Events: dialog
X-Real-IP: 192.168.1.6
Expires: 86400
Content-Length: 0
--------------------------------------------------------------------------------
Received from tls:192.168.1.3:5061 at 20/9/2007 22:15:34:391 (462 bytes):
SIP/2.0 401 Authentication Required
Via: SIP/2.0/TLS 192.168.1.6:1025;branch=z9hG4bK-tml41bj696i3;rport=1029
From: "PBX Gateway" <sip:200@192.168.1.3>;tag=ezdw7g6xl2
To: "PBX Gateway" <sip:200@192.168.1.3>;tag=41c8826e02
Call-ID: 3c26702ac79f-0h495mvgwdbu
CSeq: 1 REGISTER
User-Agent: pbxnsip-PBX/2.0.3.1715
WWW-Authenticate: Digest realm="192.168.1.3",nonce="b21e2d2e47efc0d2102367c4c8f04ee3",domain="sip:192.168.1.3",algorithm=MD5
Content-Length: 0
--------------------------------------------------------------------------------
Sent to tls:192.168.1.3:5061 at 20/9/2007 22:15:34:407 (726 bytes):
REGISTER sip:192.168.1.3 SIP/2.0
Via: SIP/2.0/TLS 192.168.1.6:1025;branch=z9hG4bK-p5hy1m7sj0xp;rport
From: "PBX Gateway" <sip:200@192.168.1.3>;tag=ezdw7g6xl2
To: "PBX Gateway" <sip:200@192.168.1.3>
Call-ID: 3c26702ac79f-0h495mvgwdbu
CSeq: 2 REGISTER
Max-Forwards: 70
Contact: <sip:200@192.168.1.6:1025;transport=tls;line=zq5p1hzm>;q=1.0;flow-id=1;+sip.instance="<urn:uuid:38070bbf-d2cf-4420-90d0-b950ac8255f3>"
User-Agent: snom370/7.1.19
Supported: gruu
Allow-Events: dialog
X-Real-IP: 192.168.1.6
Authorization: Digest username="200",realm="192.168.1.3",nonce="b21e2d2e47efc0d2102367c4c8f04ee3",uri="sip:192.168.1.3",response="1e0c846356a4845d892ec6a27cb325a2",algorithm=MD5
Expires: 86400
Content-Length: 0
--------------------------------------------------------------------------------
Received from tls:192.168.1.3:5061 at 20/9/2007 22:15:34:471 (436 bytes):
SIP/2.0 200 Ok
Via: SIP/2.0/TLS 192.168.1.6:1025;branch=z9hG4bK-p5hy1m7sj0xp;rport=1029
From: "PBX Gateway" <sip:200@192.168.1.3>;tag=ezdw7g6xl2
To: "PBX Gateway" <sip:200@192.168.1.3>;tag=41c8826e02
Call-ID: 3c26702ac79f-0h495mvgwdbu
CSeq: 2 REGISTER
Contact: <sip:200@192.168.1.6:1025;transport=tls;line=zq5p1hzm>;q=1.0;flow-id=1;+sip.instance="<urn:uuid:38070bbf-d2cf-4420-90d0-b950ac8255f3>";expires=360
Content-Length: 0
--------------------------------------------------------------------------------
EDIT: Nope it did not work. I have to setup two connections one with TLS and one without and this creates a subscription but I am able to receive incoming calls in the clear and make outgoing calls secured. This is a very strange situation indeed.