FreePBX 2.10

[mbrevda]

The FreePBX team are continuing to improve FreePBX 2.10.

The latest beta includes the automatic drop-down menus that lots of people asked for - freepbx.org/news/2011-10-10/2-10-update-and-come-say-hi-at-astricon-this-year

I updated the demo system to reflect this - http://sysadminman.net/blog/2011/freepbx-2-10-beta-demo-system-2944

Glad you like it!

 

[blanchae]

The drop-down menus are pretty nice and also the custom extensions and destinations - sweet.

When creating an extension with a extension number that already exists, a status window appears (good!) but when I hit OK, I receive a page of this:

��;is㶒�

 

[blanchae]

I noticed that when configuring an extension, there is the option to set NAT (good move!) but in the help bubble, it states that setting NAT=yes should work for both internal and external extensions. I've found that with internal Cisco 7960 phones, that setting it to "yes" causes strange problems (phone behaviour) to occur. The phones prefer NA=no.

Just to ask others if they've seen similar strange extension behaviour for internal extension with NAT=yes or if it is just a Cisco issue?

 

[Sacrilego]

I've always set mine to yes and never had any issues.
Some PAP2s, Nortel 1535s, a dlink DPH-540 and some Asstra 6739i.

I noticed that when configuring an extension, there is the option to set NAT (good move!) but in the help bubble, it states that setting NAT=yes should work for both internal and external extensions. I've found that with internal Cisco 7960 phones, that setting it to "yes" causes strange problems (phone behaviour) to occur. The phones prefer NA=no.

Just to ask others if they've seen similar strange extension behaviour for internal extension with NAT=yes or if it is just a Cisco issue?

 

[phoneguy]

The older Cisco phones did not support NAT so setting it to yes in the Extension would cause it not to work.

The same is true with CyberData Paging products. You have to set those to Nat Never or No

 

[psetti1]

I've had my office on 2.10 for a week now and it's been working great. The only issue I've had are dropped parked calls every now and then, but I'm positive that those are related to the Aastra XML scripts. I like the new UI a lot!

One other thing. In the CDR I don't see any files for recorded calls. I have recording set up at the trunk level - shouldn't that mean that any time a call goes over the trunk that it should create a file for the entire call? The files do appear to be being created - they're just not available in the GUI.

 

[tm1000]

I dont think it's ever done that

One other thing. In the CDR I don't see any files for recorded calls. I have recording set up at the trunk level - shouldn't that mean that any time a call goes over the trunk that it should create a file for the entire call? The files do appear to be being created - they're just not available in the GUI.