search for: napt

...at I copy and paste into R. You can probably guess that I am not a programmer. ## here is the start of my merge document. The "x116" line has the merge field, in this case "Bases-K Ammonium Acetate-2008-116". This changes for each soil sample, and for each type of analysis. ## napt <- read.table(file = "C:/Documents and Settings/jfloren/My Documents/R_Statistics/NAPT/NAPT_09/CertIn2010/Data_for_R/readin_all_for_2010_cert.csv ", header = TRUE, sep = ",") attach(napt) x116 <- subset(napt, Analysis_Soil %in% c("Bases-K Ammonium Acetate-2008-116&qu...

I have sent a Polycom IP500 phone to an overseas remote user who has a Speedtouch adsl modem/router. The phone is connected to the 4 port router which performs NAT for the network. The phone rboots, find the server, downloads it's config and tried to register. Then it immediately becomes UNREACHABLE. Jul 26 17:44:41 NOTICE[21026]: chan_sip.c:9138 handle_request_register: Registration from

Hi people, My asterisk wont register with any sip providers, I have tried three different but they all end up with: Sep 26 17:36:36 NOTICE[114696]: chan_sip.c:4035 sip_reg_timeout: Registration for 'whatever@provider.tld' timed out, trying again There is no firewall and my server has a public IP. Could this be a Asterisk problem? -Fredrik vK

Hi everybody, I'm trying to configure * for make SIP calls. Now I'm doing several test but I have some errors. Firstly I will describe my scenario. Client Software (Private IP 192.168.0.181, SJ Phone over Windows 2000) ---- Router Adsl (Public ip A.B.C.D, and NAPT on port 5060 to 192.168.0.181) ----- FW+Router ----- Asterisk (Public IP E.F.G.H + e400p)------ Spain ISDN I make a call to my * server and this began a SIP (SDP) signaling comunication with Client SJ Phone, during signaling comunication all looks good. But when the client answer the call, the...

Ok here's the deal. I set up Icecast and Oddcast, got them to communicate properly, but cannot access the live audio remotely. On other computers in the LAN it works perfetly. Currently I operate wirelessly behind a D-Link 514 router (a mite outdated by now, yes?) and have opened all necessary ports, turned my firewalls off, set this computer as a DMZ, pretty much everything I can think of -

Hi All, Our internal users need to connect to the bank to do internet banking. The bank requires that the client computers connect to ports 15000-15010. In Shorewall how do I do a masq for anyone trying to connect to these ports? Thanks Raymond

...in a router (which typically forwards all connection requests to the given private IP -- not my personal favorite for Windows machines), but only use a simple port forward from external port e.g. 8000 to internal IP 192.168.1.44, port 8000. This is usually called "virtual server" or "NAPT config" or something like that. If you're using the DMZ setup, maybe the router is also applying some sort of firewall. So, first thing to hack around with is your router. Or spend some $20 for a brand new one with all kinds of useless new features :-) HTH, Maarten

Thank you for your note, Scott. I set rewrite_contact=yes for both contacts, and I also had to do remove_existing=yes because I had to remove the existing contact information (max_contacts = 1 was preventing new contact information) using pjsip qualify demo-alice etc., after which the right IP addresses showed in pjsip show endpoints. Anyway, it works as expected now, I think. My pjsip.conf is

...hkM2Y2ZDNhM2U4NTZmZmE. From: <sip:demo-alice at 192.168.1.139>;tag=b661670b To: <sip:6002 at 192.168.1.139> CSeq: 2 INVITE Content-Length: 0 Any help is appreciated. A topology is shown below in ASCII. < ( Big bad Internet ) > GW/NAPT/Router | ---------------------------------------------------------- / \ | | Host A...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a situation where some Poptop/PPTP sessions (only with FC5/Shorewall to FC5/Shorewall firewall in between) cause the following to appear in the state table (shorewall show connections). unknown 47 420 src=XX.234.79.183 dst=XX.234.137.226 packets=2 bytes=130 [UNREPLIED] src=XX.234.137.226 dst=XX.234.79.183 packets=0 bytes=0 mark=0 use=1

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD 6.x stable branch, support for the FreeBSD 6.x stable branch will also cease at the same point. Users of either of

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Everyone, On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their End of Life and will no longer be supported by the FreeBSD Security Team. Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD 6.x stable branch, support for the FreeBSD 6.x stable branch will also cease at the same point. Users of either of