ap_6200

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.

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

Any updates to this question, I am having the same issue... Thanks

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?

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!

This is still the case - when can we expect the 2449 of the other versions?

Anything else from the community?

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.

You have to enable SIP dialing or whatever the equivalent parameter is for that particular phone.

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 CPU_UTIL.bmp

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 would rather it not crash - but i get the point - I will probably start it back doing that tomorrow morning.

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

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.

I'd have to see this function - but I think we're getting closer to being on the same page.

Not sure I follow

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

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.

If you add a 1 to the 10 digit phone number stored on the account settings - it will treat them normally.

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.

I just verified it on latest 2.1.6 and it works for me - at least initially...