Jump to content

Sara_Donald

Members
  • Posts

    43
  • Joined

  • Last visited

Everything posted by Sara_Donald

  1. HI, I have an issue after installing SUSE 10.3 where I connect to a windows machine to contact the PBXnSIP admin settings but when I connect using firefox using https it tells me that the certificate is out of date, infact ended last year. Is there any way to fix this problem? Sara.
  2. I have two NICS (192.168.1.1 and 192.168.0.1) but I keep seeing this entry in the status general file: 127.0.0.1 [::1] 192.168.1.1 [fe80::5efe:c0a8:101] 192.168.0.1 [fe80::5efe:c0a8:1] 192.168.36.16 [fe80::5efe:c0a8:2410] I also noticed in my logs that I keep getting: SNMP: Received packet from non-trusted source 192.168.36.53:49246 So, can someone tell me what this means since I have two NICS only and there appears to be a third ip address connecting to the management interface. Could it be that someone on my VPN is attempting to get into the admin settings of PbxnSip, I dont allow remote connection though? Kindest Regards, Sara Donald.
  3. What I have noticed is that when you do this there is a blank drop down list and you have to look at your config file to see what timezone you are using. Usually it will default to whatever timezone you are in but not always. Sara Donald.
  4. I will endeavour to get it working but I think I may have to settle for aanother PC with a single NIC and pbxnsip installed so that there is only one IP address to forward ports to. Hopefully this will overcome the problem. I only used the single RTP port to test if the phone would work directly to the router which it did but once I setup the pbx on another PC I will allow for a range of ports. Kindest Regards, Sara Donald.
  5. After all my efforts to eliminate things one by one to find out where the problem is using two NICs with Internet Connection Sharing, I uninstalled the pbx and tried to use the ip phones direct through the shared PC but nada, it would register ok with the VoIP Provider but no audio in or out. I have forwarded UDP Ports 5060 for VoIP and 5100 for RTP. Here is the strange thing. When plugging the phone into the router directly and forwarding the same ports to 192.168.1.2 which is the IP phones address when connected to the router, the thing worked clear as a bell, audio in and out, no problems. Plug the phone back into the shared PC switch and forwarding the same ports to the shared computer which is 192.168.1.1 and nothing, it registers but no audio in or out. So I disabled all firewalls and still nothing. Why is windows ICS so hard to do things with when its supposed to map ports automatically which you would presume would let the sip traffic in and out perfectly, especially without any firewalls and port forwarding. Can someone please help me out. Kindest Regards, Sara Donald.
  6. Im not sure how to do that as the remote VPN Server is a hosted service. I see what is happening, I am using tls to connect to the pbx but then the VPN uses L2TP which uses UDP transport for its VoIP on port 5060. That along with the NAT issues are killing me. I read an article on TLS having problems over L2TP. I am going to change my VPN to OpenVPN as it is better suited to TLS. I will choose a VoIP Company that allows TLS connections. Hopefully that will solve the problems. Kindest Regards, Sara Donald.
  7. Proof that the Snom Phones keep things in memory which causes problems later when you change routers. I tested the phones on a d-link router once and used a satellite connection and connected to the snom admin via an ip address of 192.168.5.5. I no longer use this network nor do I use the d-link router (not in production). It used UDP previously and now even after I have set TLS it doesnt do what its supposed to. I noticed in my scan of the 192.168.0.1 network that Snom has a checksum error: 590 71.323695 192.168.0.1 192.168.0.82 UDP Source port: 49920 Destination port: 56426 [uDP CHECKSUM INCORRECT] Here is a pcap from the phone which has been edited but you'll get the idea of what it's doing. 1 0.000000000 192.168.0.1 192.168.0.154 UDP Source port: 50198 Destination port: 53576 to 53 0.530881000 192.168.0.1 192.168.0.154 UDP Source port: 50198 Destination port: 53576 54 0.534094000 192.168.0.154 192.168.5.5 TCP 1028 > http [sYN] Seq=0 Win=5840 Len=0 MSS=1460 TSV=14803 TSER=0 WS=0 55 0.538629000 192.168.0.154 192.168.0.1 UDP Source port: 53576 Destination port: 50198 to 86 0.843667000 192.168.0.1 192.168.0.154 UDP Source port: 50198 Destination port: 53576 87 0.849741000 192.168.0.154 192.168.0.1 TCP https > 50144 [FIN, ACK] Seq=1 Ack=1 Win=11040 Len=0 88 0.850789000 192.168.0.1 192.168.0.154 TCP 50144 > https [ACK] Seq=1 Ack=2 Win=16326 Len=0 89 0.858153000 192.168.0.154 192.168.0.1 UDP Source port: 53576 Destination port: 50198 to 319 4.138182000 192.168.0.154 192.168.0.1 UDP Source port: 53576 Destination port: 50198 320 4.150070000 192.168.0.154 192.168.0.1 TLSv1 Application Data 321 4.158116000 192.168.0.154 192.168.0.1 UDP Source port: 53576 Destination port: 50198 322 4.165976000 192.168.0.1 192.168.0.154 TLSv1 Application Data 323 4.167510000 192.168.0.154 192.168.0.1 TCP solid-mux > sip-tls [ACK] Seq=788 Ack=434 Win=10967 Len=0 TSV=15166 TSER=1881341 324 4.170829000 192.168.0.1 192.168.0.154 UDP Source port: 50198 Destination port: 53576 to 330 4.247156000 192.168.0.1 192.168.0.154 UDP Source port: 50198 Destination port: 53576 331 4.250827000 192.168.0.154 192.168.0.1 TLSv1 Application Data 332 4.258875000 192.168.0.154 192.168.0.1 UDP Source port: 53576 Destination port: 50198 333 4.264652000 192.168.0.1 192.168.0.154 TLSv1 Application Data 334 4.265884000 192.168.0.154 192.168.0.1 TCP solid-mux > sip-tls [ACK] Seq=1294 Ack=727 Win=10967 Len=0 TSV=15176 TSER=1881350 335 4.278123000 192.168.0.154 192.168.0.1 UDP Source port: 53576 Destination port: 50198 to 708 9.258513000 192.168.0.154 192.168.0.1 UDP Source port: 53576 Destination port: 50198 etc.
  8. True. I still have two NICs and I did a pcap trace on the Snom 370 phone which uses firmware 7.1.30 and noticed that the phone was using UDP instead of TCP even though I have outgoing proxy set as :5061;tls. I also noticed another IP address when trying to negotiate the call, the IP address is from another network when I used to use the phone on Satellite. This problem would be a software problem or memory problem. I think snom have far more issues relating to tls than any other phone. I have tried to sort out tls with them previously but it fell on deaf ears. The only thing I can do is reset the phones to factory default and start over. I will also try the PC without two NICs and connect via the network from the router and see if that makes a difference. Kindest Regards, Sara Donald.
  9. Port forwarding works with software phones behind the same network NAT, using the same IP address setup. All software phones work without having the scrambled ring tone. The Snom phones do not work properly behind the setup I have. I setup a VoIP ATA behind the NAT and address setup and it works fine with port forwarding to 192.168.1.1. The only thing I can think of is that if pbxnsip is routing all ip addresses including the vpn then that could cause problems. IP Addresses: 127.0.0.1 [::1] 192.168.1.1 [fe80::51cf:7cec:7066:16fc] [fe80::5efe:c0a8:101] 192.168.0.1 [fe80::f03d:fe22:48ef:f8ab] [fe80::5efe:c0a8:1] 192.168.14.38 [fe80::5efe:c0a8:e26] 192.168.14.38 [fe80::5efe:c0a8:e26] is the VPN. Kindest Regards, Sara Donald.
  10. Well here is the answer: There is nothing wrong with windows routing as I tried it with Bria software, I had port forward enabled on port 5060 and it rang normally. Snom IP Phones are the problem by not allowing the phone to route through nat properly when there is more than one IP. I even turned off the firewall and allowed all traffic through and it still didnt work. but if I connect the Snom to the router directly and use the VoIP providers details then it works brilliantly. The Snom will call out behind the firewall and Nat with scrambling sounds instead of a normal ringtone but calls when asnswered are clear and both ways. Snom really need to address this issue as if it cannot work with multiple IPs and Nat then what use is it. I know have to test Snom with STUN but I cannot see it working if it cannot get past the IP issues. Kindest Regards, Sara Donald.
  11. I think you may be right about vista and its routing, you only have to look at Microsoft who built the latest SP1 for Vista which puts text on the bottom of your screen saying you have a valuation version even though you have a fully activated RTM. I did try XP and cant say I noticed the scrambling sound. I think I have to go back to the beginning and start without the vpn and forward port 5060 to the pbx machine without the packet scheduler enabled and only using NAT on the router and see if that fixes the problem. Then go back to the vpn and try the same thing by forwarding port 1701 and 5060. If it works on the pbx machine with and without the vpn then it was the router not setup right, if it doesnt then it will definately be a Vista routing issue. Thank you for you advice so far. Kindest Regards, Sara Donald.
  12. Yes, I have several Snom 370's on a private network which uses a PC with two NICs. The private lan is 192.168.0.1, the public lan is 192.168.1.1 which uses VPN and is attached to the billion adsl router which connects to the internet. This router has nat and packet scheduling firewall enabled. 192.168.1.1 uses internet connection sharing to connect all PCs and IP Phones via a switch. 192.168.1.1 has the windows firewall enabled. All ports on the switch use seperate untagged VLANs. I use windows Vista on all PCs. The pbx uses a sip trunk for outgoing calls. The problem is that the phones are not able to get a ringing tone, just scrambled gaga until the call is answered on the other side (this doesnt happen on internal calls). I have tried ringing in via a mobile and sometimes the ringtone is heard but other times there is silence until someone picks up the ip phone. It is obviously a NAT issue and I have turned off the firewalls and placed the public lan 192.168.1.1 into DMZ but it made no difference, the scrambling sound still occurred. Kindest Regards, Sara Donald.
  13. I looked in the logs and found that I have a UDP binding error and RTP error. I allow all of the associated ports outgoing but I do not allow anything back in as I am very security concious. I am using a Billion NAT Router with Firewall enabled and have set all of the associated port in the packet scheduler. I did try allowing DMZ for the computer hosting the pbx but it didnt make a difference, probably because the firewall does not allow incoming connections. Here are the log messages, what do they mean and how do I overcome this situation? [0] 20080128185056: UDP: bind() to port 61584 failed [0] 20080128185112: UDP: bind() to port 61360 failed [5] 20080128185244: BYE Response: Terminate 3c271250d983-xdwq0s2qoe0s [5] 20080128185256: RTP Timeout on 3c2712b62ee7-o2fv21f428lm#a3a998c80b [3] 20080128185256: Via is empty, cannot send reply Kindest Regards, Sara Donald.
  14. I had to change the dst offsets as they are wrong and I left out WA dst as I dont know what it is. Here is the file below: <?xml version="1.0" encoding="utf-8"?> <timezones dict="timezones.xml"> <item id="AUS1">Western Australia</item> <item id="AUS2">South Australia</item> <item id="AUS3">Northern Territory</item> <item id="AUS4">Queensland</item> <item id="AUS5">New South Wales</item> <item id="AUS6">Australian Capital Territory</item> (that would include Victoria and Tasmania) <zone name="AUS1"> <description>Western Australia</description> <gmt_offset>28800</gmt_offset> <dst_offset>28800</dst_offset> <dst_start_day_of_week>1</dst_start_day_of_week> <dst_start_month>10</dst_start_month> <dst_start_time>02:00</dst_start_time> <dst_start_week_of_month>Last</dst_start_week_of_month> <dst_stop_day_of_week>1</dst_stop_day_of_week> <dst_stop_month>3</dst_stop_month> <dst_stop_time>02:00</dst_stop_time> <dst_stop_week_of_month>Last</dst_stop_week_of_month> </zone> <zone name="AUS2"> <description>South Australia</description> <gmt_offset>37800</gmt_offset> <dst_offset>34200</dst_offset> <dst_start_day_of_week>1</dst_start_day_of_week> <dst_start_month>10</dst_start_month> <dst_start_time>02:00</dst_start_time> <dst_start_week_of_month>Last</dst_start_week_of_month> <dst_stop_day_of_week>1</dst_stop_day_of_week> <dst_stop_month>4</dst_stop_month> <dst_stop_time>02:00</dst_stop_time> <dst_stop_week_of_month>1</dst_stop_week_of_month> </zone> <zone name="AUS3"> <description>Northern Territory</description> <gmt_offset>34200</gmt_offset> </zone> <zone name="AUS4"> <description>Queensland</description> <gmt_offset>36000</gmt_offset> </zone> <zone name="AUS5"> <description>New South Wales</description> <gmt_offset>36000</gmt_offset> <dst_offset>39600</dst_offset> <dst_start_day_of_week>1</dst_start_day_of_week> <dst_start_month>10</dst_start_month> <dst_start_time>02:00</dst_start_time> <dst_start_week_of_month>Last</dst_start_week_of_month> <dst_stop_day_of_week>1</dst_stop_day_of_week> <dst_stop_month>4</dst_stop_month> <dst_stop_time>02:00</dst_stop_time> <dst_stop_week_of_month>1</dst_stop_week_of_month> </zone> <zone name="AUS6"> <description>Australian Capital Territory</description> <gmt_offset>36000</gmt_offset> <dst_offset>39600</dst_offset> <dst_start_day_of_week>1</dst_start_day_of_week> <dst_start_month>10</dst_start_month> <dst_start_time>02:00</dst_start_time> <dst_start_week_of_month>Last</dst_start_week_of_month> <dst_stop_day_of_week>1</dst_stop_day_of_week> <dst_stop_month>4</dst_stop_month> <dst_stop_time>02:00</dst_stop_time> <dst_stop_week_of_month>1</dst_stop_week_of_month> </zone> </timezones>
  15. How do I set the PBX for Australian Central Standard Time DST. I have looked in the admin settings but nothing appears even close? Kindest Regards, Sara Donald.
  16. Thats what I thought except I did try the noise.wav thing and I got silence at the beginning of my call so much that I couldnt even hear the ringing of the phone. I am not using srtp and dont know how to turn it off in the latest version. I just use the old 5060 port which then goes over VPN. I dont know if this could be the problem but am I supposed to allow the client to have incoming outgoing use of port 5060 or just outbound the PBX is on a client that connects to the VPN? Regards, Sara.
  17. Thank you for the reply, so do I have this right, I rename the noise.wav file to something like nonoise.wav and create another file called noise.Ok or do I create a blank file called noise.wav using notepad? Regards, Sara.
  18. Hi, I have this problem where when I dial out the pbx gives me this extremely loud scrambling noise until the call is connected. I use a VPN to route VoIP. I have allowed the RTP ports outbound and all other associated L2TP VPN ports outbound to the server. The sound is almost like a fax sound and underneath you can hear the dialing taking place but it doesnt shut up until someone answers the call then everything is crystal clear. Im using the latest Windows version on Vista. Can someone please help me as I never used to get this problem in the earliest version 2. Regards, Sara.
×
×
  • Create New...