3.1

[Vodia PBX]

For those who can live without extensive release notes, there are new images for 3.1 out:

 

http://pbxnsip.com/download/pbxctrl-3.1.0.3043.exe (Windows, manual upgrade)

http://pbxnsip.com/download/pbx3.1.0.3043.exe (full Windows installer)

http://pbxnsip.com/download/pbxctrl-freebsd7.0-3.1.0.3043 (FreeBSD7.0 32-bit)

http://pbxnsip.com/download/pbxctrl-rhes4-3.1.0.3043 (RedHat 4)

http://pbxnsip.com/download/pbxctrl-centos5-3.1.0.3043 (CentOS 5)

http://pbxnsip.com/download/pbxctrl-suse10-3.1.0.3043 (SuSE10)

http://pbxnsip.com/download/pbxctrl-debian4.0-3.1.0.3043 (Debian 4)

http://pbxnsip.com/cs410/update-3.1.0.3043.tgz (CS410)

 

We'll have the release notes and the missing OS (e.g. MacOS) ready probably on Tuesday, until then please drive carefully!

[pbx support]

For those who can live without extensive release notes, there are new images for 3.1 out:

 

http://pbxnsip.com/download/pbxctrl-3.1.0.3043.exe (Windows, manual upgrade)

http://pbxnsip.com/download/pbx3.1.0.3043.exe (full Windows installer)

http://pbxnsip.com/download/pbxctrl-freebsd7.0-3.1.0.3043 (FreeBSD7.0 32-bit)

http://pbxnsip.com/download/pbxctrl-rhes4-3.1.0.3043 (RedHat 4)

http://pbxnsip.com/download/pbxctrl-centos5-3.1.0.3043 (CentOS 5)

http://pbxnsip.com/download/pbxctrl-suse10-3.1.0.3043 (SuSE10)

http://pbxnsip.com/download/pbxctrl-debian4.0-3.1.0.3043 (Debian 4)

http://pbxnsip.com/cs410/update-3.1.0.3043.tgz (CS410)

 

We'll have the release notes and the missing OS (e.g. MacOS) ready probably on Tuesday, until then please drive carefully!

 

 

Mac OS version has been uploaded to the sever.

http://pbxnsip.com/download/pbxctrl-darwin9.0-3.1.0.3043.zip (Mac OS)

[olecoot]

Can you tell me please if the issue with Agent Queue Statistics has been corrected in this release? This is the issue where there are no statistics are collected if the domain is in a different time zone that the server. This was broken when 3.x was introduced.

[Vodia PBX]

Can you tell me please if the issue with Agent Queue Statistics has been corrected in this release? This is the issue where there are no statistics are collected if the domain is in a different time zone that the server. This was broken when 3.x was introduced.

 

You mean http://forum.pbxnsip.com/index.php?showtopic=1312? 3.1 is the "next build"...

[andrewgroup]

Somewhere along the way the dynamic recording feature has become inactive on our SNOM phones. VM, CDR, Performance and Status changes are all working ok, but recording shows it's recording on the server, but is never delivered via email. Has this feature setting changed or gone away. Cheers.

3.1.0.3043 (Win32)

this was likely broke in late august or sept, but nobody noticed...

[Carl Johnson]

Couple issues on test to this version.

 

All tel (10 digit) aliases had 011 appeneded to them, that is a lot of work to fix!

 

Inbound calls on trunk, unchanged from 3.0.1 to 3.1 will not hit extension based on tel alias (account) as before .. for example we get a 10 digit DNIS and have the account set with that 10 digit as an account alias but it does not match as expected and goes to default (AA)?

 

Outbound issue with forcing ANI on redirections from outside is still exisitng.

[Carl Johnson]

More issues ..

 

On the trunk settings, the NAPNA 10 digit, it totally ignores that as it is still sending +[CC][AC][NUMBER]

 

Also, when it saves the aliases, it stores them as +[CC][AC][NUMBER] even when entered as [AC][NUMBER] so on inbound the rule from 2.x, 3.0 does not work?

[Vodia PBX]

Couple issues on test to this version.

 

All tel (10 digit) aliases had 011 appeneded to them, that is a lot of work to fix!

 

But then there must have been something wrong with these numbers? If you set the country code to "1" the PBX must think that this is a international number. Can you give an example?

 

Inbound calls on trunk, unchanged from 3.0.1 to 3.1 will not hit extension based on tel alias (account) as before .. for example we get a 10 digit DNIS and have the account set with that 10 digit as an account alias but it does not match as expected and goes to default (AA)?

 

Well, the point of all these canonicalizations is to solve this problem. There is a conversion rule in the trunk now that you can set. If you choose the 10/11-digit rule then the PBX will assume the trunk is in NAPNA and then automatically convert numbers into the +1(xxx)xxx-xxxx format.

[Vodia PBX]

More issues ..

 

On the trunk settings, the NAPNA 10 digit, it totally ignores that as it is still sending +[CC][AC][NUMBER]

 

Also, when it saves the aliases, it stores them as +[CC][AC][NUMBER] even when entered as [AC][NUMBER] so on inbound the rule from 2.x, 3.0 does not work?

 

Hmm. That should work (we are using this rule in our Boston office). Can you give a concrete example?

[hosted]

PnP doesn't work still.............aarrrrrrrrrgggggggggghhhhhhhhhhhh How is it possible to deploy a snom phone in a PnP environment? Its not! Guess its back to the good old fashion manual configured.... (nooooooooo)

 

I cant make is stop sending calls like this:

Trunk Gateway sends call to +18012223333 in domain 208.187.1.1

 

And the cellular service flags still don't work....

And the VM issues still exists (when VM is set to email and delete, the VM light never goes away)..

 

#1 bug tester i am.

 

oh my. Other that those glaring issues for us the new additions are cool.

on the cellular thing,, cant press ## to transfer the call back to the PBX yet?

[hosted]

ok so in a different thread you are able to fix the VM light..

 

Is the PnP and the cellular service flag able to be fixed with this release?

 

How can I make it not add the +1 to every call (incoming and outgoing)

[Carl Johnson]

Okay on the transformations .. we have the dialplan set as NAPNA 3 digit and when entering an extension as:

 

** Inbound DNIS **

 

In v3.0 we had setup extensions as 123 with a tel:40612345678 alias and after conversion to 3.1 it added the 011 to all of these so in the ext it showed 123 011 40 61234567 or something similar?

 

v3.1 - when we have an extension same as the areacode it tried adding +1 to it?

 

v3.1 - 123 4061234567 it changes to 123 (406)123-4567 on the screus-en and then in the user alias db entry it stores

 

445.xml:<row><display>(406)123-4567</display><domain>2</domain><name>+140612345678</name><user>35</user></row>

 

We took care of the issue with the inbound by adding that to the incoming number as it was coming in as 10 digits so we prepended in the inbound trunk +1 to those .. should that be required just to a version upgrade?

 

Before: !([0-9]{10})!\1!t!500 .. for 2.x 3.0

After: !([0-9]{10})!+1\1!t!500 for 3.1

 

** Logging **

 

Also, we are trying enable logging which full debug and it just ignores me and does not do so, no file no log entries in the status->log

 

** Outbound **

 

Why does it still transform the OUTBOUND ANI to a full number

[Vodia PBX]

Okay on the transformations .. we have the dialplan set as NAPNA 3 digit and when entering an extension as:

 

** Inbound DNIS **

 

In v3.0 we had setup extensions as 123 with a tel:40612345678 alias and after conversion to 3.1 it added the 011 to all of these so in the ext it showed 123 011 40 61234567 or something similar?

 

v3.1 - when we have an extension same as the areacode it tried adding +1 to it?

 

v3.1 - 123 4061234567 it changes to 123 (406)123-4567 on the screus-en and then in the user alias db entry it stores

 

445.xml:<row><display>(406)123-4567</display><domain>2</domain><name>+140612345678</name><user>35</user></row>

 

We took care of the issue with the inbound by adding that to the incoming number as it was coming in as 10 digits so we prepended in the inbound trunk +1 to those .. should that be required just to a version upgrade?

 

Before: !([0-9]{10})!\1!t!500 .. for 2.x 3.0

After: !([0-9]{10})!+1\1!t!500 for 3.1

 

** Logging **

 

Also, we are trying enable logging which full debug and it just ignores me and does not do so, no file no log entries in the status->log

 

** Outbound **

 

Why does it still transform the OUTBOUND ANI to a full number

 

Did you use "1" as country code? Then those transformations IMHO make sense. Okay, the upgrade procedure is a little bit bumpy, but then we have a clean solution.

 

The whole magic is disabled when there is no country code. But IMHO it makes sense to specify the country code and let the PBX convert the different telephone number formats into a normalized format.

[Carl Johnson]

I did have 1 as the CC before the upgrade and yes it was a bit bumpy .. any feedback on the logging issue?

[Carl Johnson]

Additional issue .. in the RC for some reason VM messages are not recording (that is why is need the logging working) and it seems related to this situation and not "normal" extenstions.

 

Caller comes into AA then presses 6 which transfers them to an extenstion with NO registrations, when the caller is connected the VM (goes right to VM as it is unregisterd .. lets call this a VM only ext) the prompts and recordings are playing and the user is leaving a VM but for some odd reason unless the caller presses # or a digit it will NOT leave the VM which is very odd as usually a call disconnect works just as well and is certanly not expected!

 

PLEASE check this out.

[Vodia PBX]

Additional issue .. in the RC for some reason VM messages are not recording (that is why is need the logging working) and it seems related to this situation and not "normal" extenstions.

 

Caller comes into AA then presses 6 which transfers them to an extenstion with NO registrations, when the caller is connected the VM (goes right to VM as it is unregisterd .. lets call this a VM only ext) the prompts and recordings are playing and the user is leaving a VM but for some odd reason unless the caller presses # or a digit it will NOT leave the VM which is very odd as usually a call disconnect works just as well and is certanly not expected!

 

PLEASE check this out.

 

Yea, this is really strange (was also reported by other people). If you like, try http://pbxnsip.com/protect/pbxctrl-3.1.1.3091.exe this may fix the problem.

[Carl Johnson]

can you please produce a debian 4.0 x86 binary?

[Carl Johnson]

Any advice on the Country code response and logging question?

[shopcomputer]

Now with 3.1, having the capability to require confirmation when receiving calls on a cell phone. It would be nice to be able to enable groups to forward to cell phones. Right now we use manual registrations for cell phones that must participate in groups, however that lacks the confirmation capability.

[Carl Johnson]

can you please produce a debian 4.0 x86 binary?

 

Debian revision? Also, please address the logging issue? Lastly, I still have not had an answer on forcing outgoing ANI changes as currently it sends the incoming ANI out for redirected calls and that is always not possible as some vendors make your ANI be one of the known DIDs?

[Vodia PBX]

Debian revision? Also, please address the logging issue? Lastly, I still have not had an answer on forcing outgoing ANI changes as currently it sends the incoming ANI out for redirected calls and that is always not possible as some vendors make your ANI be one of the known DIDs?

 

Debian: http://pbxnsip.com/protect/pbxctrl-debian4.0-3.1.1.3094

 

ANI: Did you try choosing the "Remote Party/Privacy Indication"? Maybe just set it to "No Indication"?

[Tim]

Debian: http://pbxnsip.com/protect/pbxctrl-debian4.0-3.1.1.3094

 

ANI: Did you try choosing the "Remote Party/Privacy Indication"? Maybe just set it to "No Indication"?

 

We would like to put this on a test system, any chance of getting a build for CentOS 5?

 

Tim

[Vodia PBX]

We would like to put this on a test system, any chance of getting a build for CentOS 5?

 

Ehh - we are currently wresting with a ugly problem in the transfer area. You better wait a day until that is finished. When it may be time to generate a set of new builds!

[Carl Johnson]

tested 3.1.1 build, VM issue is still ugly. What can I do to help as I can reproduce readily?

[pbx support]

tested 3.1.1 build, VM issue is still ugly. What can I do to help as I can reproduce readily?

What's the issue with the voicemail? Was it already posted in this thread?