ap_6200
-
Posts
139 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by ap_6200
-
-
I can confirm this is a bug in at least the last few releases, you can find several posts in the forum about this. I you an IVR node instead fo the sub attendant, to work around the issue.
I can operate most features in PBXnSIP, but even after reading the wiki, i have no idea how to implement this into an Auto Attendant, or sub-AA..
Could you please post detailed instructions?
Thanks
-
Query regarding syntax.
Wishing to match 1+10-digit or just 10-digit in a single statement.
The following works for matching NANP possible digits dialed:
(1[0-9]{10})@.*|([0-9]{10})@.*
Why doesn't the following work:
(1?[0-9]{10}@.*
Thanks for any hints or tips for a REGEXP match for NANP.
-Krom
Any updates to this question, I am having the same issue... Thanks
-
The pbxnsip software runs at an average 10% CPU ustilization except when paging which drives utilization up to 50 to 90% for a brief moment.
This is an interesting observation, and may explain one of my servers that continually "spikes", as one of my customers do a lot of paging, with multiple end-stations...
PBXnSIP, have you ever noticed this situation, and is there anything that can be done to lower the utilization?
-
That AA is on another system, right? The problem was that the AA#2 gets started with DMTF already coming in, and it happily picks that up?
No, AA#2 is on the same system, same domain.
And AA#2 plays the 1st half just fine, it's the back half that's cut off.
Very easily reproducible.
Without the # - it plays the entire greeting.
-
In 2.1.6.2450 the following scenario is still an issue:
Trunk to AA#1 - In the settings for the direct dial destination, i have "1#" (to force the PBX to pause 3 seconds) to route to AA#2
This works, except it cuts off half of my message on AA#2.
If I take out the # sign, it routes perfectly, and plays the entire AA#2 greeting.
Please advise when this can be fixed.
It's essential that we be able to have direct dial destinations, regardless of Extensions that start with the same digit (i.e. 1)
Thank you
-
Is 2449 for Linux going to be out soon?
Thanks!
-
It is fixed in 2449. Unfortunately, we at this point have only Windows and SuSE Linux, the other versions will follow soon as the servers are up again.
This is still the case - when can we expect the 2449 of the other versions?
-
Anything else from the community?
-
That is generally good news
Generally. Or it means people have gotten numb to posting issues. I want to make sure. ;-)
-
I haven't seen many posts pertaining to the instability of 2.1.6.2448 - Can you please post your findings on this forum?
I'm interested in all known bugs and features that are affected.
Thank you.
-
It is the phone. It says it needs to be dialed using the e164 dialing or something along those lines when you dial without the + sign.
It is a new installation.
You have to enable SIP dialing or whatever the equivalent parameter is for that particular phone.
-
Our experience is different. So far we are over 3 months on 2.1.5.2357.
For the most part we keep a 23 Channel PRI, 70% utilized 5 business days per week with ACT of 2 minutes, thus about 3,800 calls per day with 45 internal SNOM 320 phones. This has been the pace since we upgraded to release 2.0.3 and now on 2.1.5.2357, I think the largest month was 65,000 calls. 3 Nics one to the Local LAN, 1 to the PRI Gateway, and another to what will soon be 6 remote offices with pbxnsip. I placed some documents on this system in the best practices on our windows Installations. Do these agree with what you are doing? We also have a very standard Gentoo install from source that we can use where needed.
I've included both Free Virtual RAM and CPU performance charts over the last 3 months. The single instance of the RAM following was us remotely accessing the system and doing some serious computing to extract a bunch of files...The system returned with more available Virtual RAM. It's a Windows thing, it must have cleaned and release the pool when it dipped low for our remote process.
Do you have any Windows WMI, SNMP, or other agents monitoring the system to indicate the time/day/load where the problem is occurring? it would be interesting to triangulate when the problem occurs. Perhaps it's event driven and not load driven.
we simply see little to no load on our systems. We also fully track all traffic, events on all switches, routers, using our NMS, and SolarWinds.
The Snoms are still using 6.5.x firmware and we are running SRTP internally.. (despite claims of others having troubles with 6.5.x and SRTP)
Perhaps someone can step up with a SIP session tester from IXIA and we can fully load one of these puppys's to the MAX...
It would be nice to see where the smoke comes from...At least we'd know the upper limit, and everything has an upper limit.
This is what we experience on a daily basis...
Version: 2.1.5.2357 (Win32)
License Status:
License Duration: Permanent
Additional license information: Extensions: 224/9999 Accounts: 283/9999
Working Directory: C:\Program Files\pbxnsip\PBX
IP Addresses: 127.0.0.1 10.1.0.10 x.x.x.x (public)
MAC Addresses:
Calls: 5621/2113 (CDR: 5355) 0/0 Calls
SIP packet statistics: Tx: 873362 Rx: 865318
Emails: Successful sent: 107 Unsuccessful attempts: 0
Uptime: 1 10:05:37 (73MB/2047MB 22% 40666880-0) WAV cache: 0
-
IMHO, Voice servers are no different than other servers, and in some ways even more critical. I could schedule a LAN Server upgrade during client work hours with some advanced notification, but not likely could we shut down their telephone system. We have avoided system crashes by investing in server class systems. Lowend Dell Poweredge, 400/800 series, SuperMicro, All with ECC RAM, HARDWARE RAID, and a very strict OS installation setup. Our oldest Windows and Linux machines are going on 2 years back to version 1.5.x with no real crash experiences.
Put them on 2.1.x and put it on the server of your choice and let me know if they make it 30 days without restarting - and have them do about a 7K call volume per day. One domain is doing 4K by itself. The "server" doesn't crash - the application does.
-
I always set service to auto restart. I did that the first time the service crashed. I am not sure if I ever had a service crash since, as it would start right back up, before the complaints come in.
I would rather it not crash - but i get the point - I will probably start it back doing that tomorrow morning.
-
I also got several complaints about blank / hang up messages.
I also got a few that voicemail volume is very low.
I echo the volume low issue as well - I've reported it before, but was discounted on a few levels - so I let it go. I get fewer of those than I get "my phones are saying URL call disabled" because my pbxnsip service decided to shut down with no error indication"
-
One other thing that would be really nice on the voicemail system is if they could add "hangup detection" and not issue a voicemail if that is all it is. We get a lot of voicemails that are just hangups, and it wastes a lot of time. There have to be some common voice processing functions that can determine that pretty easily, especially when the message is less than 10 seconds.
Thanks
-
Oh oh. You are right, here comes the fix:
http://www.pbxnsip.com/download/pbx2.1.6.2447.exe (complete InstallShield)
http://www.pbxnsip.com/download/pbxctrl-2.1.6.2447.exe (bare executable)
http://www.pbxnsip.com/download/pbxctrl-cs410-2.1.6.24467 (CS410)
http://www.pbxnsip.com/download/pbxctrl-debian4.0-2.1.6.2447 (Debian 4.0)
http://www.pbxnsip.com/download/pbxctrl-rhes4-2.1.6.2447 (Redhat ES4)
http://www.pbxnsip.com/download/pbxctrl-suse10-2.1.6.2447 (SuSE10)
PBXnSIP Community - I was running 2.1.5.2357 for about 25 days straight with little to no problems on 3 separate servers.
On Monday - one of them stopped the services unexpectedly - with no indication in the logs (log level 3)
Yesterday - one of them stopped the services unexpectedly - with no indication in the logs (log level 6)
Yesterday - the same server stopped AGAIN unexpectedly - an hour later.
I'm contemplating proactively starting and stopping the services on the 3rd server today - so I don't have to explain the outage to customers when it decides that it is going to restart during business hours.
My question to the community - are we ever going to get a stable release - like 2.0.3.1715 so that I can safely deploy these to my customer base? I'm getting hammered daily by the instability of each release since 2.1.2
Is 2.1.6 - latest version being run in a production environment by anyone? And how long do I need to wait to see if problems are going to occur... I'm trying to quit using my customer base as a testing ground for new releases.
Any help is appreciated.
-
Well you would have to list the extensions or other accounts that should send the daily CDR to the admin. It would essentially be the same email as the daily email CDR, but filtered for that account. That means if you put "123 124 125" in the list, that admin will receive three more emails at night with the CDR where 123 124 and 125 were involved in calls.
I'd have to see this function - but I think we're getting closer to being on the same page.
-
Okay, would it solve the problem to introduce a settings that contains a list of the extensions that should be reported? E.g. "101 102 103 119" would send the daily CDR for those 4 accounts?
Not sure I follow
-
I get one email per call now, that does the job for me. Outlook does the job or sorting the emails into the right folder. The beauty of this solution is that is always up-to-date (no need to wait until midnight) and it is very easy for the PBX (no huge emails at midnight).
OK, envision this:
You are a Sales Manager - and you want to monitor each of your sales reps call activity during the day. And you want it forwarded to the Sales Manager's email address. Currently the way it's set up is that the user's email address (especially if they are getting voicemail to email) all emails will be going to that specific user.
Using your idea of CDRs doesn't work in this scenario - as the Sales Manager doesn't want all of the voicemails - they simply want a report of activity.
Additionally - If I have multiple Accounts to monitor - they will all come from the same email address (the domain settings "from" field). How does exchange sort them out on a per user basis?
I seem to be getting alot of push back from implementing this seemingly easy feature. One email - per user - per night - with their daily call logs.
You have one email for the entire domain CDR's at midnight - and now the complete opposite spectrum of one email per call... I'm asking for something in between.
Again - at least at a bare minimum, increasing the log file from the last 30 CDR when logged in as a specific user to "all calls in a 24 hour period"
Thanks
-
2.1.6 already has a setting called "cdr_email_size" (invisible global setting in pbx.xml) - see http://wiki.pbxnsip.com/index.php/Global_Configuration_File. Check out http://www.pbxnsip.com/protect/pbxctrl-2.1.6.2441.exe if you like.
Since there will obviously be modifications to 2.1.6 - could you please consider Daily CDR's (One email) on a per account basis?
Or at a bare minimum tell me how to get more than 30 calls when logged in as a user. It doesn't seem to be affected by the admin setting of "Default CDR listing size"
Thank you.
-
We have created 6 accounts for a client to directly send all calls to the user Cell Phones.
When those Cell phone users dial the main number, that are given DISA access to make outbound calls. Go to voice mail or go to the Autoattendant
The client would prefer that these users calling from the cell phone are treated as any other caller and no DISA outbound calling capability.
If you add a 1 to the 10 digit phone number stored on the account settings - it will treat them normally.
-
Call me crazy, but is the attached image as you would expect it to be?
Also using 2.1.6.2442 (Win32)
I would say unless there are white spaces in either field - or that the extensions don't exist - but I have to assume they do because you are obviously well-versed in pbxnsip... that it should work the way it's laid out.
-
It should say 1# and 2# - not the destination field. The # makes the pbx wait 3 seconds.
I just verified it on latest 2.1.6 and it works for me - at least initially...
Known Issues with 2.1.6.2448
in Product/Site Comments
Posted
Do you know if multicast works with Polycoms? I have about 20 extension in a paging group (unicast) triggered from a linksys pap2t in a nursing home - lots of paging.