Jump to content

Sara

Members
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sara

  • Rank
    Newbie
  1. Yes my Motorola has 128 bit encryption, it is a hidden feature of the phone I found when flexing.
  2. OK, I have finally got the encryption working. If you add the line transport=tls to your outbound proxy it plays havock with the encryption on Snom 370 but if you just register the Snom to the ip address without the tls line it shows that it offers AES Encryption. I tried it with a call to my mobile which supports secure calls and it encrypted the call ok. So I dont know why the tls line would effect the encryption but it does, you can either have outbound over tcp with tls or outbound over udp with tls or just outbound over tcp but these do not work with encryption, as soon as a line is added
  3. I use xxx.xxx.xxx:5061;transport=tls on outgoing proxy and yes I have encryption enabled on the Snom 370 phones all with firmware version 7.1.19, the pbxnsip is version 2.0.3.1715 windows. When I use xxx.xxx.xxx:5061;transport=tls it runs over UDP with my VPN OK but when I use sip:xxx.xxx.xxx:5061;transport=tls it does encrypt but I cannot receive any incoming calls. Sara.
  4. I hooked up my three Snom 370 Phones and all have encryption enabled so one would think they would automatically encrypt calls between each of the phones but NO they don't. I did a network scan and could see the unencrypted packets travelling back and forward ready for me to gather statists on the VOIP call and play it back in the clear. I have tried just about everything but to no avail. Sara.
  5. 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
  6. mmmmm, in outbound proxy on the phone I used 192.168.1.3:5061;transport=tls - this works fine for outgoing calls. I did notice that when using the vpn calls come in as udp and there is no RTP at all but it still connects to the PBX ok, it is only when I enter the extension number that I get nothing but voice mail or white noise. Here is the sip trace within SNOM 370. Sent to udp:192.168.1.3:5061 at 19/9/2007 07:46:25:866 (536 bytes): REGISTER sip:192.168.1.3 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.6:1025;branch=z9hG4bK-tfcna53qu529;rport From: "PBX Gateway [Out]" <sip:200@192.16
  7. SNOM 370 can connect ok with 5061;transport=tls but cannot get any calls passed from pbxnsip to extensions. The calls come in ok to pbxnsip but as soon as the user enters the extension pbxnsip cant pass the call, all they hear is white noise. I have been shooting off emails to every man and their dog trying to work this out but Im stumped, can someone please help me set up incoming TLS connections that actually work, I have attached a Snom 370 pcap which clearly shows TLS is working and the other pbxnsip file shows that it clearly doesnt do anything, it goes straight to voice mail. When I
×
×
  • Create New...