I have two installs here I am testing (ISO and manual install). Delivered-To: [email protected] Received: by 10.231.241.67 with SMTP id ld3csp89764ibb; Sat, 7 Jul 2012 11:40:04 -0700 (PDT) Received: by 10.224.206.131 with SMTP id fu3mr3990108qab.72.1341686403424; Sat, 07 Jul 2012 11:40:03 -0700 (PDT) Return-Path: <[email protected]> Received: from pbx.uc.myitdepartment.net xxxx-RichmondVA.hfc.comcastbusiness.net. xxxx]) by mx.google.com with ESMTP id gw1si28181686qab.13.2012.07.07.11.40.02; Sat, 07 Jul 2012 11:40:03 -0700 (PDT) Received-SPF: neutral Authentication-Results: mx.google.com; [email protected] Received: from pbx.uc.myitdepartment.net (localhost [127.0.0.1]) by pbx.uc.myitdepartment.net (Postfix) with ESMTP id AA23FC1A50 for <[email protected]>; Sat, 7 Jul 2012 14:40:01 -0400 (EDT) From: Voicemail Notification Service <[email protected]> To: [email protected] Message-ID: <[email protected]> Subject: Voice Message: Tony Graziano MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1_1690651.1341686401317" X-SIPX-FROMURI: "Tony Graziano" <sip:[email protected]> X-SIPX-MSGID: 100000001 X-SIPX-MBXID: 200 X-SIPX-MSG: yes Date: Sat, 7 Jul 2012 14:40:01 -0400 (EDT)
I think in this above case it was a manual install from a centos 6.2 netinstall (minimal) and sipx did not add or require sendmail (hmmm), as it had postfix and I had to add after the fact. If this is the fact, maybe the minimal install instructions should be changed to add sendmail and mta switcher how to use the mta switcher to flip to sendmail after install, prior to installing sipx or have sipx script tdo this for you? I will have to spin the other instance up and look and see what it is sending as hostname too. On Fri, Jul 13, 2012 at 9:10 AM, Mircea Carasel <[email protected]> wrote: > > > On Wed, Jul 11, 2012 at 12:43 PM, Tony Graziano > <[email protected]> wrote: >> >> also.. >> >> sendmail sends as “localhost.{hostname}”, instead of “hostname”. > > Tony, > can you please let us know the scenario where you spotted > localhost.{hostname} when sending emails. > I tried few thinks like voicemail notification, alarm sending and cannot > reproduce... > Thanks > Mircea >> >> >> proxy does not answer calls until any reconfiguration/refresh to force >> restart of proxy. So during the initial configuration there is no auto >> send of the server profiles to instantiate this automatically? >> >> On Wed, Jul 11, 2012 at 5:40 AM, Tony Graziano >> <[email protected]> wrote: >> > On Sat, Jul 7, 2012 at 11:11 PM, Douglas Hubler <[email protected]> >> > wrote: >> >> On Sat, Jul 7, 2012 at 8:31 AM, Tony Graziano >> >> <[email protected]> wrote: >> >>> FWIW - The certificate is not being regenerated, as it still have the >> >>> original create date/time on it. >> >> >> >> I'll look into this. What if you delete the files, are they then >> >> created correctly after you send profiles? >> > >> > I never thought and noone ever mentioned to delete the files. >> >> >> >> >> >>> It also seems to keep putting in the dns of its "old" ip address >> >>> recieved via dhcp, even after manually changing it and the alias in >> >>> sipxconfig. >> >> >> >> Changing an alias is very different then changing IP. Did you change >> >> it in server list? >> > >> > I did. >> > >> > hostname and IP’s are stale even after manually reconfiguring, so once >> > sipx has an ip address, what is the proper procedure to change the >> > system address? >> >> >> >> >> >>> >> >>> How does one manually manage iptables? >> >> >> >> There should be setting for Unmanaged. All the rules sipxecs would >> >> create have extension *.unmanged. They may help you shape your new >> >> ones. >> >> >> >> >> >>> Is it expected that the setup script (centos or sipx) will not allow >> >>> one to define ip/mask/gateway manually? >> >> >> >> It's doesn't care anymore. configuring the network is between you and >> >> the OS. >> > >> > I think this is a stumbling block, because when you install from the >> > ISO it does not ask you to run "system-config-network-tui, and gives >> > you ZERO options. I think it (as well as wget and nano) should be on >> > the ISO and that system-config-network-tui should be called at the end >> > of the installation before the setup script, or the mailing list will >> > be full of people having network config issues. >> >> >> >> >> >>> named would not start with the bare records created. I deleted the >> >>> zone file and created it manually. There seem to be multiple syntax >> >>> errors with out-of-zone data. Probably formatting but it was >> >>> unapparent to me so I just took a template and replaced it to get bind >> >>> up. >> > >> > default zone information has improperly configured serial number, bind >> > fails. >> > >> > The following errors were found in the BIND configuration file >> > /etc/named.conf or referenced zone files .. >> > dns_rdata_fromtext: uc.myitdepartment.net.zone:2: near >> > '1341997405869': out of range. >> > (the running number being calculated is wrong, which is a good reason >> > IMO to use a different format altogether) >> > zone uc.myitdepartment.net/IN: loading from master file >> > uc.myitdepartment.net.zone failed: out of range >> > zone uc.myitdepartment.net/IN: not loaded due to errors. >> > _default/uc.myitdepartment.net/IN: out of range >> > >> > I think I see what is happening here. The serial number is based on >> > the “original” ip address perhaps using a running number? Due to ANY >> > potential change with the IP, it would pretty much break DNS zone from >> > being reachable later on. It broke RIGHT AWAY for me. Based on this, I >> > would suggest the serial number format be based on yymmdd instead. >> > >> > Managing DNS manually is not directly editable in the zone.conf file, >> > where is it (syntax to verify manual configuration) now? >> > >> > disabling dhcp does not stop dhcp server? disabling DNS still >> > overwites zone serial number preference from bind? >> >>> >> >>> not that this matters right now: cant get any output from index.php >> >>> after logging into webhomer (server error 500). >> >> >> >> you need to enable "SIP Capture" and "SIP Capture Search" in >> >> Experimental features. With the help of homer team, next rev will >> >> instruct you to use your superadmin credentials on homer login screen. >> >> It is a problem that out of the box, you can get yourself into an >> >> error. >> >> >> >>> >> >>> [Sat Jul 07 08:10:19 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Constant _HOMEREXEC already defined in >> >>> /var/www/html/webhomer/components/login/login.php on line 30 >> >>> [Sat Jul 07 08:10:19 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Undefined index: login in >> >>> /var/www/html/webhomer/components/main/main.php on line 42 >> >>> [Sat Jul 07 08:10:19 2012] [error] [client 10.255.255.247] PHP >> >>> Warning: date(): It is not safe to rely on the system's timezone >> >>> settings. You are *required* to use the date.timezone setting or the >> >>> date_default_timezone_set() function. In case you used any of those >> >>> methods and you are still getting this warning, you most likely >> >>> misspelled the timezone identifier. We selected 'America/New_York' for >> >>> 'EDT/-4.0/DST' instead in >> >>> /var/www/html/webhomer/components/main/main.php on line 46 >> >>> [Sat Jul 07 08:10:19 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Undefined variable: header in >> >>> /var/www/html/webhomer/components/main/main.php on line 52 >> >>> [Sat Jul 07 08:10:19 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Undefined variable: level in >> >>> /var/www/html/webhomer/components/main/main.php on line 52 >> >>> [Sat Jul 07 08:10:21 2012] [error] [client 10.255.255.247] File does >> >>> not exist: /var/www/html/favicon.ico >> >>> [Sat Jul 07 08:10:29 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Constant _HOMEREXEC already defined in >> >>> /var/www/html/webhomer/components/login/login.php on line 30, referer: >> >>> http://10.255.252.59/webhomer/ >> >>> [Sat Jul 07 08:10:29 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Undefined index: login in >> >>> /var/www/html/webhomer/components/main/main.php on line 42, referer: >> >>> http://10.255.252.59/webhomer/ >> >>> [Sat Jul 07 08:10:29 2012] [error] [client 10.255.255.247] PHP >> >>> Warning: date(): It is not safe to rely on the system's timezone >> >>> settings. You are *required* to use the date.timezone setting or the >> >>> date_default_timezone_set() function. In case you used any of those >> >>> methods and you are still getting this warning, you most likely >> >>> misspelled the timezone identifier. We selected 'America/New_York' for >> >>> 'EDT/-4.0/DST' instead in >> >>> /var/www/html/webhomer/components/main/main.php on line 46, referer: >> >>> http://10.255.252.59/webhomer/ >> >>> [Sat Jul 07 08:10:29 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Undefined variable: header in >> >>> /var/www/html/webhomer/components/main/main.php on line 52, referer: >> >>> http://10.255.252.59/webhomer/ >> >>> [Sat Jul 07 08:10:29 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Undefined variable: level in >> >>> /var/www/html/webhomer/components/main/main.php on line 52, referer: >> >>> http://10.255.252.59/webhomer/ >> >>> [Sat Jul 07 08:10:46 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Constant _HOMEREXEC already defined in >> >>> /var/www/html/webhomer/components/login/login.php on line 30, referer: >> >>> http://10.255.252.59/webhomer/index.php?component=search >> >>> [Sat Jul 07 08:10:46 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Undefined index: login in >> >>> /var/www/html/webhomer/components/main/main.php on line 42, referer: >> >>> http://10.255.252.59/webhomer/index.php?component=search >> >>> [Sat Jul 07 08:10:46 2012] [error] [client 10.255.255.247] PHP >> >>> Warning: date(): It is not safe to rely on the system's timezone >> >>> settings. You are *required* to use the date.timezone setting or the >> >>> date_default_timezone_set() function. In case you used any of those >> >>> methods and you are still getting this warning, you most likely >> >>> misspelled the timezone identifier. We selected 'America/New_York' for >> >>> 'EDT/-4.0/DST' instead in >> >>> /var/www/html/webhomer/components/main/main.php on line 46, referer: >> >>> http://10.255.252.59/webhomer/index.php?component=search >> >>> [Sat Jul 07 08:10:46 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Undefined variable: header in >> >>> /var/www/html/webhomer/components/main/main.php on line 52, referer: >> >>> http://10.255.252.59/webhomer/index.php?component=search >> >>> [Sat Jul 07 08:10:46 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Undefined variable: level in >> >>> /var/www/html/webhomer/components/main/main.php on line 52, referer: >> >>> http://10.255.252.59/webhomer/index.php?component=search >> >>> [Sat Jul 07 08:14:54 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Constant _HOMEREXEC already defined in >> >>> /var/www/html/webhomer/components/login/login.php on line 30 >> >>> [Sat Jul 07 08:14:54 2012] [error] [client 10.255.255.247] PHP Notice: >> >>> Undefined index: login in >> >>> /var/www/html/webhomer/components/main/main.php on line 42 >> >>> [Sat Jul 07 08:14:54 2012] [error] [client 10.255.255.247] PHP >> >>> Warning: date(): It is not safe to rely on the system's timezone >> >>> settings. You are *required* to use the date.timezone setting or the >> >>> date_default_timezone_set() function. In case you used any of those >> >>> methods and you are still getting this warning, you most likely >> >>> misspelled the timezone identifier. We selected 'America/New_York' for >> >>> 'EDT/-4.0/DST' instead in >> >>> >> >>> so I edited /etc/php.ini and put it >> >>> ;date.timezone = >> >>> date.timezone = "America/New_York" >> >>> >> >>> I get no more timezone errors from php, still can't login. >> >> >> >> ok, i think we can address this, can you create an issue. >> > >> > Nice to have mp3 option finally.!! Why cant we serialize the voicemail >> > filename from freeswitch like we do faxes with the date/time stamp >> > though? >> >> _______________________________________________ >> >> sipx-dev mailing list >> >> [email protected] >> >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >> > >> > >> > >> > -- >> > ~~~~~~~~~~~~~~~~~~ >> > Tony Graziano, Manager >> > Telephone: 434.984.8430 >> > sip: [email protected] >> > Fax: 434.465.6833 >> > ~~~~~~~~~~~~~~~~~~ >> > Linked-In Profile: >> > http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> > Ask about our Internet Fax services! >> > ~~~~~~~~~~~~~~~~~~ >> > >> > Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab >> > 2013! >> >> >> >> -- >> ~~~~~~~~~~~~~~~~~~ >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> sip: [email protected] >> Fax: 434.465.6833 >> ~~~~~~~~~~~~~~~~~~ >> Linked-In Profile: >> http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 >> Ask about our Internet Fax services! >> ~~~~~~~~~~~~~~~~~~ >> >> Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab >> 2013! >> >> -- >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> sip: [email protected] >> >> Helpdesk Customers: http://myhelp.myitdepartment.net >> Blog: http://blog.myitdepartment.net >> _______________________________________________ >> sipx-dev mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013! -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
