pbx support

Ok, We will take another swing at it. We will try to make the diversion header flexible and editable like the other headers so that you have more control on it.

The order is Extension, Domain, Trunk ANI. Yes, if the extension ani is not set, then PBX uses the domain ani. If that is not set either, then trunk ANI. If nothing is set, the extension number will be sent out (which probably not work for most trunk providers!) There is "ANI for emergency calls:" under the extension. The snomONE will send that if set. Otherwise, the above rule will be applied.

Changing it back to other values should work, unless you have some "wrong" customization. The .1075 has an issue in the mailbox area. Please check http://forum.snomone.com/index.php?/topic/6063-mailbox-reporting-full-but-its-empty/page__p__25778__hl__mailbox__fromsearch__1#entry25778

There is no difference between those 2 versions with respect to buttons. Just make sure you have selected the right button number.

If you open the snom_3xx_phone.xml and snom_820_phone.xml have the below setting (almost at the end) <admin_mode perm="">off</admin_mode> Either you can delete that line or you can change off to on The First Method under http://wiki.snomone.com/index.php?title=Modifying_Plug_and_Play_Files explains some generic details.

It is very hard to match every possible combinations of providers. Many times "more settings = more confusion". The "assume call coming from user" is used for the incoming calls to overwrite the "From" user. This definitely has impact on the caller id.

Under "Admin->Settings->PnP" page, there are special settings for snom 300 keys 3-6. You can cleanup these first depending on the requirement, i.e., you can take out the least important key setting there and make it available for the service flag button. Then you can create and assign a button profile (http://wiki.snomone.com/index.php?title=Buttons, http://wiki.snomone.com/index.php?title=Button_Programming) for that extension.

Yes, it will be incorporated in the next software revision.

Well, "If I jump from a 10 story build, I will break my legs or worse..... But I will still jump" :-)

In the older versions, we had the option to change the User-Agent string. But,unfortunately, in 4.5 we do not have that option.

Multicast support is not associated with the license. It is just the settings on the PBX. What is the OS? We had seen cases where you had to tweak the OS to get the "...multicast join" to work.

Not sure why you had to change the templates for this one. If you are doing PnP, most simple method is to put the MAC address of each these phones in the "Extension->Registration: Bind to MAC Address:" separated by spaces. Ex: 000413261234 000413261245 000413261256 Only thing that will not work is "have the call missed indicator light go out on all phones when cancelled on one phone".

Can you please check out this - http://wiki.snomone.com/index.php?title=Plug_and_Play ?

You can safely ignore that. We just log that before we initialize few things. We will remove that log in the future versions.

I think the transfer to mailbox still happens/works. But we did some "intelligent" thing in the case of the blind transfer to provide more control to the transferor. PBX does not hangup the transferor automatically like it used to do before. Seems like that created this situation when you transfer the call directly to VM. We will take care of this issue in the future versions.

I meant set the conference account number as part of the conference name itself. There is no variable for that. Instead of setting the name as Alabu Conference Room, set it as Alabu Conference Room x555

Are you referring to cell phone calling into the system and then dialing out (to an external number) or cellphone calling into the system and then calling an extension number? Since you are talking about DISA, I assume you are not referring to the 'extension associated cellphone'.

Currently, there is no option for the body. But the number 5555551212 should be your access number for the conference. If you still want to send alias for the conf room, then you can probably make it part of the description. Say, The conference room name is "AlabuConference Room x555"..

Oh..PBX does not have any control on the delay of the cell phone hangup after sending a BYE message to the trunk provider when the internal user(snom phone) hangs up. So only the SIP message trace can tell us where the delay is.

Did anyone check out - http://snomone.wordpress.com/2012/02/21/snomone-virtual-appliance/ ?

If snomONE can't contact the license server this can happen. Is there any error in the snomONE log file?

After discussing with the phone team, there is a setting we need to add to the phone templates. That setting is using_server_managed_dnd. In the snom_3xx_phone.xml and snom_820_phone.xml: After line: <user_active idx="{lc}" perm="RW">on</user_active> Add line: <using_server_managed_dnd idx="{lc}" perm="RW">on</using_server_managed_dnd> Then you have to either re-sync or reboot the phones to take effect.

I believe there was an issue in that version either renaming or adding aliases. It has been fixed in the next version.

Did you check out http://wiki.snomone.com/index.php?title=How_to_implement_fax_on_snomONE%3F ?

SOAP access is restricted at the system level using "SOAP trusted IP address" field. So, we assume that the admin knows exactly what he/she is doing when it comes to database access using SOAP messages(especially, DBSet). Note that you can use ModifyAccount (http://wiki.snomone.com/index.php?title=Access_to_the_Database#ModifyAccount) to do similar operations and it does have some error checking.