Jump to content

Len

Members
  • Posts

    6
  • Joined

  • Last visited

Len's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Sounds good and definitive. Thanks.
  2. Well, at the time I wrote that, I had looked for pbxnsip binaries but they were not there yet. They are now. No dead end any more . I installed 4025 and it works fine. Thanks. Now let's see how it behaves at the next incident. BTW. I read that the fix is to declare a 408 error on the trunks when the registering stops. I then can receive an e-mail, go into the web interface and click "REGISTER". That's much better than how it was. However, I would prefer to be able to automatically recover from an incident . Right now I am thinking of doing so by automatically "clicking" on the REGISTER link of each trunk. So I am still interested in the incantation to do that with proper authentication : 'http://<pbx ip address>/dom_trunks.htm?trunkreg=<trunk index>' and then some extra stuff. Or something similar.
  3. So that is a dead end for now. Bummer. I tried another avenue where I have this Python script running in the background. It analyses the log file as it develops and detects when the SIP register messages do not appear any more. The idea is to have the script simulate a 'click' on the link that I normally click manually if I want to restart registrations again (http://<pbx ip address>/dom_trunks.htm?trunkreg=<trunk index>). Unfortunately I am unable to get past the authentication stuff. Would anyone know the right incantation that my script should send to the pbx in order to make it simulate my clicking on this link? The alternative would be to send a text message to my cell phone, but I'd hate to receive those in the middle of the night: most-times the registration process stops when I am fast asleep. Thanks.
  4. Hi, I have the same problem of all my trunk registrations (7 of them with 2 providers) stopping suddenly. I tried the Debian link at http://pbxnsip.com/snomone/beta/debian/pbxctrl-debian4.0-2011-4.2.1.4025. The sip connections seem to be all up, but this is difficult to verify as a significant number of website pages refuse to be returned. So now I am back at Version: 4.2.0.3981 (Linux) Created on: Jan 28 2011 17:22:18 License Status: pbxnsip Europe - TopIT - Dencad - Office Pro 10 - Upgrade Protection Ends - 31th August 2011 License Duration: Permanent Additional license information: Extensions: 10/10 Accounts: 16/500 Upgrade: 08 31 2011 Working Directory: /root/pbxnsip MAC Addresses: 00248CC1EEAF Calls: 0/0 (CDR: 276/282/270) 0/0 Calls SIP packet statistics: Tx: 618 Rx: 618 Emails: Successful sent: 9 Unsuccessful attempts: 0 Available file system space: 75% Uptime: 2011/6/29 13:55:54 (uptime: 0 days 00:12:00) (7211 8446912-0) WAV cache: 0 Number of HTTP sessions: Sessions: PAC=0, HTTP=1; Threads: SIP=5, HTTP=1 Any suggestions? Thanks.
  5. I find this snippet in my logs: [3] 20090623215918: Could not connect to 75.150.83.3:443 [1] 20090623215918: Could not send via TCP: 68 bytes [4] 20090623220018: HTTP client: Timeout Reverse IP lookup tells me that this address belongs to pbxnsip. Is there anyone who can tell me where the pbx might be connecting to and for what reason?
  6. Hmmm, on page http://wiki.pbxnsip.com/index.php/Installing_in_Linux it is stated that one should unzip his freshy downloaded audio zip files with "unzip xvfz audio_xx_20.zip". That did not work for me. The phrase xvfz looks like tar options, but tar does not read a zip file properly. Just "unzip filename -d <pbx dir>" did the job for me.
×
×
  • Create New...