Jump to content

jlumby

Members
  • Posts

    290
  • Joined

  • Last visited

Posts posted by jlumby

  1. I just got hit by the friendly scanner again, this time the source IP was 92.61.60.3 Unfortunately since Version 4 with DoS protection is still under development, it took the server down, until I could block it at the firewall. THe packet capture looks identical to the one I posted above

  2. I did a search of the entire PBX directory for files larger than 4mb Other than PBXCTRL.EXE I came back with hundreds of call recordings, most that averaged around 10 meg, and a few that were up to 50 meg, in addition to that, there were 2 non call recording files that were about 6 meg each. One was a voicemail where the person hung up, however the voicemail system kept recording silence for 1 hour, and the other was a name recording where there was nothing but noise in the background. Is there any way we can figure out which extension the voicemail name recording belongs to so that we can properly remove it, or is it OK to just delete the file?

     

    After restarting the system last night, the problem has disappeared, and the current memory line reads:

    (uptime: 0 days 15:39:21) (47MB/2046MB 18% 8228480-0) WAV cache: 1

  3. The TFTP has firmware for many different models of phones in it, so it is 135Mb, and the server is also doing call recording, so the recordings directory is a few gigs. Do you think either of these point to my issue with it not playing system recordings, or am I looking in the wrong place. I just figured those memory numbers might be the issue since they look significantly different from every other PBXnSIP install, and the others are not having issues.

  4. I have a Windows 2003 server running 3.4.0.3202 that has an uptime of about 60 days. When checking voicemail, or calling an auto attendant, most of the time there is just silence. This seems to happen more frequently the longer that the server has been online. A reboot seems to fix the problem for a while. I have done a packet capture to verify that there is 2 way RTP. Is this a known issue with the version, or are there any workarounds available?

     

    On a second glance I see the following line on the status page:

    (93MB/2046MB 25% 1760960164-1709445284)

     

    What do these numbers mean??? On the PNXnSIP support site it says what the 93MB/2046MB means, however the other numbers are not described (25% 1760960164-1709445284) The 1760960164-1709445284 concerns me since other pbxes that are not having an issue end in a -0

  5. I have had this happen as well. Sometimes I even have had them end up in another domain. I think it has something to do with 2 people logging in to administer the pbx at once, or having 2 coppies or tabs of internet explorer open at once to administer the PBX. It is hard to duplicate, however I am pretty sure that this is what has happened.

  6. I have found that if you enter an incorrect extension number in an auto attendant, and the voice prompts you that you have done so, the redirect timeout is no longer in effect. This is problematic since if I you want to replay the greeting, you cannot do so after a certain amount of inactivity. I am on version 3.4.0.3202 Win32

  7. I experienced the same problem. I had a call path that went hunt group 1>auto attendant>hunt group 2>voicemail The problem is it would cut off after the 3rd leg, so it would never get to the voicemail. Adjusting the Max Loop in the PBX.xml from 10 to 20 fixed the issue, however I would like to know why the issue happened in the first place. If it was set to 10, why was it cutting me off at 3? Obviously it was the right value since adjusting it to 20 fixed the problem.

  8. I am thinking about adding another ITSP that does inbound calling on a per path basis. I am wondering if there is a way that I can tell the total number of simultaneous inbound calls on a trunk. I can monitor the specific trunk with SNMP, however it shows both inbound, as well as outbound call totals. Any way to get just inbound?

  9. there is no sure fire way. It all depends on the software that is on it. Although holding down pound while booting, and then pressing 123456789*0# when the side lights start to flash in order down the right hand side of the screen, works on most software versions. Be prepared to have all firmware available, since it erases the flash.

  10. I am running 3.4.0.3201 (Win32) and I am having an issue where the DTMF digits are rarely recognized while the greeting is playing, however they work perfectly in the silence after the greeting is done being played. Any suggestions for improving the recognition during the greeting?

×
×
  • Create New...