voipguy

Where do you see firmware ver 8.4.32? Thought the latest was 8.4.31.

it doesn't matter what ata you use, your still doing T38 faxing which is not perfect and relies on so many things such as your local internet connection, who you use for T38 termination and so on. A Linksys SPA2102 with the 5.2.12 firmware update from Jan 2011 improved the reliability of it's T38. I can get 6 or 7 out of 10 faxes to go through without errors, before the 5.2.12 update it was less then 50%. If you want 100% success rate which is what you should want then use PSTN or HTTPS faxing - the faxback guys perfected that and Audicodes helped out with the firmware for the ATA.

This bug is known and has been fixed. I think in version 4.2.1.4014 and up it's fixed, maybe fixed even before version .4014.

Ahh, that makes sense. Thanks for the quick answer.

Has anyone else noticed the MOS graph gets erased at midnight? The green vertical bar is still there at current time when viewing it but the history is gone from previous day (to the right of the green vertical line)....ver 4.2.4014 and earlier had no problems. My other 3 graphs are fine. Running pbxnsip on 32 bit centos.

Is it a silverlight based ap?

Your right, PAP2 can't do T.38 - it can do G711 faxing but not as reliable as T.38. The SPA2102 with latest firmeware Jan/2011 is much better for T.38 faxing.

Thanks for putting this in ver 4 - just tested it and it works great!!

I was still locked out of the phone so I had to do the snom recovery method to reset the phone. I did the above custom file settings and they worked! Thanks Now I have the caller id working for SNOM 300/320 and the 870.

Hi pbs support, Thanks for the fast reply - I'll try this. Thanks.

I did the above and the display name setting worked but now I'm locked out of the snom 300 phone? The snom_300_custom.xml is an exact copy of the snom_3xx_phone.xml file but with the added custom display name config line....is that what's supose to be in the snom_300_custom.xml file? Any idea how to get back into the snom 300 phone? I looked in the generated directory and in the xml file I have the password but it's not working - also the PnP Domain master password doesn't work anymore. Thanks

I added <display_method idx="{lc}" perm="RW">display_number_name</display_method> to the snom_3xx_phone.xml file but like I thought it now screws up the SNOM 370 phones - caller id shows twice now with this setting. I removed it from the snom_3xx_phone.xml file. I went into the Web page Control tab and loaded Reg_texts.htm and added <option>snom_300_phone.xml</option>...then loaded snom_300.xml...in this file I changed <file url="{https-url}/snom_3xx_phone.xml?model=snom300" /> to <file url="{https-url}/snom_300_phone.xml?model=snom300" /> so it will use the settings from the new custom snom_300_phone.xml file that I created in reg_texts.htm....in the new snom_300_phone.xml all the standard settings are there and I added the <display_method idx="{lc}" perm="RW">display_number_name</display_method> line - saved it...turned on full logging...rebooted snom 300 phone...the setting didn't take...looked in the pbxnsip log and I see this: [8] 2011/04/24 16:38:42: Received request for file snom_300_phone.xml [8] 2011/04/24 16:38:42: Error finding snom_300_phone.xml, Send back 404 Not Found I checked the extensions generated folder and there is no snom_300_phone.xml file - so this tells me the binary doesn't create it for some reason.....I also tried all of the above for a 320 phone and same results. Looks like pbxnsip can only generate a snom_3xx_phone.xml file - I can't add the display setting line in that file because it will screw up all the 370/821/870 phones. pbxnsip can you confirm the binary doesn't create snom_300_phone.xml files or snom_320_phone.xml files? I also copied the snom_300_phone.xml file into that extensions generated folder and rebooted phone but it still didn't work. Thanks,

Thanks, I'll give it a try but I think that will also change all the other snom models as well 370/821/870's ? because the snom_3xx_phone.xml template is used by all phone models. I read somewhere that I can set custom settings for all 300's and 320's that wont effect 370/821/870's. It's only the 300 and 320's that have the caller id problem - and I want to set this on a global basis for my hosted system. Can you give me some pointers to do this?

Hi pbx support, Thanks. I changed the setting inside the phone to "Number Name' and now I can see the full caller id number and part of the name. It's a 2 line display - you would think they would use the top line for name and bottom line for number like the rest of the world What files do I change inside pbxnsip so this setting will always stay even after firmware upgrade? We run hosted version so we can't do the above for the remote 300's and 320's. Thanks.

Anyone?

Hi pbx support, That would be awesome if you could evaluate this and put it in ver4. Ver 5 sounds like it's going to be amazing - bringing everything down to the domain level makes the software much more powerful. Thanks,

I tried that but couldn't get it to work. But I did get it to work by replacing "url {http-url snom}/adrbook.xml?user={id}&auth={webhash}" which is under Settings/PnP tab in the Button 4 field with this "url {http-url snom}/adrbook.xml?user={id}&auth=basic" Now the Directory button works on my SNOM 300's....looks like the problem is with "auth={webhash}" when it should be "auth=basic" I don't know but I do know it works now. I understand but since the SNOM 300 comes out of the box with button 4 labeled as the Directory key I think pbxnsip should provision it as the Directory key and if the person wants to change it on there own then they can. As of right now nothing is provsioned in button 4 - I could see if pbxnsip provsioned it as a voice mail key or something else but it's just blank so it's still useless.

I have to disagree with you. This feature didn't even exist until I requested it to be put into the software. I requested it in June 2010 and 2 days later Pradeep sent me a new build 4.1.0.4011 with this feature that we now see in the software today. The reason I requested this feature was so the end users/employees can't see the Domain/Companies address book. Why? because the Domain/Company address book can contain VIP info like LLB's, hiring/firing people, plus notes on each listing - you don't want your employees to see or even worse edit/delete this info but you do want your President, VP and managers to have access to the Domain/Company address book. Back in June when I requested this feature and it was implemented I tested it for the phone and it does work - the users can't see the Domain address book data on their phones but I never thought to login to the web interface as a end user (I always stay logged in as Admin) and see if it removes the Domain address book tab until yesterday when a new client I setup emailed me and complained that his employees can see the Domain/Company address book listings. This was a feature I sold him on and now he can't use it. I know - I did hide the option for the end user so the end user can't select what phone book he can see - that's not the problem. This was added so that the end user can't see the Domain address book - only the admin can setup who can and can't see what phone book based on if the person is a manager/president etc. This field only exists because it's part of my feature request from June 2010. We know - that's why I requested the feature to control who can and can't see what type of phone book. This is a hosted system so that would effect all my other Domains - which we can't do because then all the other Managers in other Domains won't have access to the Domains address book in their pbxnsip web interface - no way to add/delete auto dial etc the phone book entries. What needs to be done is fix the software so it obeys the setting that was created for this feature "Under the users extension settings, the admin can set the users directory button to allow/see: -Both domain and personal addresses -Domain addresses only -Personal addresses only" If the users account is set to "Personal addresses only" then when the user logs into his pbxnsip web interface under the List tab the user wont see the "Domain Addresses" tab. If the users account is set to "Domain addresses only" then when the user logs into his pbxnsip web interface under the List tab the user wont see the "Personal addresses" tab. If the users account is set to "Both domain and personal addresses" then when the user logs into his pbxnsip web interface under the List tab the user will see "Both domain and personal addresses" tab. Could you please add this to the fix q. Thanks

Hi snom ONE, You completely didn't understand my post. Why would I edit the template which effects all users/domains when that part/feature works fine in the pbxnsip web interface - that works - that's not the bug.

PnP works fine for the SNOM 300 but the directory key (button 4) doesn't work. In pbxnsip under Settings/PnP tab for the SNOM 300 button 4 it has this listed: url {http-url snom}/adrbook.xml?user={id}&auth={webhash} ...then after the phone gets PnP'd I go into the phones web interface and it has this in button 4; http:// pbxnsip server ip:80/snom/adrbook.xml?user=181&auth=bf0a(long hash code)bbb3 when you press the directory key nothing gets displayed. In my SNOM 320 phones web interface it has this listed for the directory key; http:// pbxnsip server ip:80/snom/adrbook.xml?auth=basic so I manually put http:// pbxnsip server ip:80/snom/adrbook.xml?auth=basic in my SNOM 300 button 4 and now my directory key lists my directory info on my SNOM 300 - it works! so then I took http:// pbxnsip server ip:80/snom/adrbook.xml?auth=basic and put it in pbxnsips Settings/PnP tab for button 4 and then rebooted my snom 300 so it would get provisioned again but now for button 4 it's empty and of course the directory key no longer works. How can I get my directory key working on SNOM 300's without manually programming button 4 in each of the SNOM 300's web interface? This is for a remote client setup - 5 phones. Thanks

Under the users extension settings, the admin can set the users directory button to allow/see: -Both domain and personal addresses -Domain addresses only -Personal addresses only If you set it to "Personal addresses only" then on the users phone they can only see phone directory listings that they created and not the phone listings created in the Domain address book - this works....but if the user logs into the pbxnsip web interface under their own user extension they can see the entire Domain address book listings - that is the bug. The Domain address book is for VIP listings that the employees should not have access to. Please confirm this is a bug and add it to the fix Q. Thanks

I also just tested a SNOM 320 and I get the same results - incomming caller id only displays the callers name and no number. I downgraded the SNOM's firmware to ver 7.3.30 on both the 300 and 320 and same results. Also changed the trunk settings "Remote party/Privacy indication:" to all options and still same results. Trying to resolve this before Monday when client gets back to office - all 8 phones - 5 SNOM 300's and 3 SNOM 320's have no incomming number in the call display. SNOM 370/821 and 870 work fine. Anyone else have this problem with the 300/320's/ Thanks

The best option would to have your clients Visa machine connect via internet instead of phone line - this way you don't have to worry about SPA2102 or VoIP settings to make the Visa machine work. All the newer Visa machine terminals have that option.

Hi, We just PnP 5 SNOM 300's with pbxnsip ver 4.2.1.4010 32bit centos and everything works except for incomming caller id only shows the callers name and not the number. Is this a bug or a setting I'm missing? Customers previous phone system had caller id now this new system I installed for them only shows the callers name - customer is not happy. The caller id works fine on the SNOM 370's. Thanks, Daryl

The virtual assistant is only offered when calling an auto attendant - it would be great if it was also offered when calling your extension/DID direct. Some clients don't have auto attendandts and can't use this virtual assistant. Also, the virtual assistant is only offered if the PBX can see your cell's caller id - some cells have private caller id and the PBX can't see it so the virtual assistant is not offered - make it so it's an option in the users mailbox - user logs into mailbox from any telephone number and then can make an outbound call.