pbx support

Did you forget attachment?

Please change it to url {http-url snom}/adrbook.xml?auth=basic. That should take are of the directory issue.

That is just the call-id that remote side is sending. Nothing really serious.

Is the call recording turned on there? In any case we will double check.

Are you really using Delta Aurigids (4.5.0.1075)? Can you check the Admin->Status page? We tested on this version and with the configuration you have every call should be "Pas permis" Here is something you can do to restrict local = 2 digit indicatif 01, 02, 03, 04, 05 Example: Pref---------------- Trunk------------------------Pattern------------------------- Replacement 150------------------Not Allowed------------ ^(0[1-5]*)@.*-----------------<leave it empty> But if you want to allow the same pattern, then you can do something like this to block everything else. Pref---------------- Trunk------------------------Pattern------------------------- Replacement 150------------------trunk1------------ ^(0[1-5]*)@.*-----------------sip:\1@\r;user=phone Similarly, you can add other patterns and at the end you can have this Pref---------------- Trunk------------------------Pattern------------------------- Replacement 200------------------Not Allowed------------ *-----------------<leave it empty>

Before digging into the XML files, can you check what is set on Admin->Settings->PnP:Setting for snom 300 (button 4): ? If you are using one of the recent versions(snomONE), you should see url {http-url snom}/adrbook.xml?auth=basic. That should provision the directory button properly.

Alternatively, you can use the web interface to download the audio prompts too (provided, you create the folder manually). See "Updating Audio Files" section under http://wiki.snomone.com/index.php?title=Software_Update

The "force local ringback" is only for outbound calls. It is used when the remote switch(provider) does not play ringback when a PBX extension makes an outbound call. If the issue is with the incoming call, then I would suggest to set "Ringback(Support early media):" to "Message 180". That 'sort of' suggests the provider to play the ringback to the caller.

Error 535 is the authentication issue. Did you setup the Admin->Email page correctly?

No, that was not part of the changes in this version. There is an overlap between the changes made after 4.2 in that area and music issue. That is still an issue to be fixed.

If I understood you correctly, you want to access the generated XML files for snom 300 phones so that you can find out what the user name / password to login to the phone's web interface. Assuming that's what you are trying to do, you can ssh to the SoHo(provided that is not an issue anymore) and then navigate to PBX working directory (generally /usr/local/snomONE, you can double check this on the System->Status page). You will see the same file structure as the desktop setup. Then you can open those files to see the login info.

You can still dial 1 and then 8201 if you are calling from mobile.

Hello, The latest 4.5 snomONE version(Delta Aurigids) has been released. This version is built on top of the Coma Berenicids. The release notes and the download links can be found here - Delta Aurigids Note: This is snom ONE release (i.e., not applicable to pbxnsip customers). Thank you for the continued support. The snomONE team!

Is 40 is the index of the extension or the account number? If it is the account number, you need to first get the index and then try to get the other parameters. Look at the DBSearch function in the same page.

Are these TCP based registrations or UDP? There was an issue in the low level TCP layer in the last version(symptom was TCP CDR stopped working). Just wanted to see if that is the case here too. This problem has been fixed. If both are related, then this should be fixed too. We are releasing the new version later today.

Maybe the last SOHO version had some issues. We changed some javascript in the next version. We will release the version this week. Of course, that is not an answer to your "how to factory reset Soho", but to inform that we have a fix from next version onwards.

Yes, the next version will use launchDemons.

Do you mean you trunk is getting de-registered or something else?

Engineering has suggested that the next version will have this change. Basically, 4899 can make use of the Extension->Permission:Only the following extensions may call this extension: settings and Extension->Redirection:Call forward calls when busy to setting divert the calls from other than 4811, 4813 and whole external calls to the secretary.

Not really sure how the SugarCRM accepts SOAP messages. We may have to do some work in the next months release. But meanwhile, you may send the PBX message to a custom SOAP server(any program that can receive SOAP messages from PBX) that knows how to talk to the SugarCRM.

Looking at the error codes from http://developer.apple.com/library/ios/#DOCUMENTATION/System/Conceptual/ManPages_iPhoneOS/man2/intro.2.html, the 60 is for timeout. I assume, because of that the send is failing. May be something else is happening (something with RTP). We will check it out.

The outbound calling is something few folks had issues with after the upgrade from 4.3 to 4.5. You may be one on them. If you have the INVITE going from PBX or the trunk provider using 4.3, then it is very easy to make it work on the 4.5 too using http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers Also, there are some samples here http://wiki.snomone.com/index.php?title=Custom_Headers_on_the_Trunk If you still have issues, please post the INVITE from 4.3.

We realized that it is not as 'easy' as we thought. So, it is not added to the software yet

Error code seems to be related to "Socket is not connected". PBX tries to connect to 10.2.3.4:8080 first before sending the data. Possibly, it is taking more time to connect to 10.2.3.4:8080. Does the server on the 10.2.3.4:8080 accept connections without any delay?

If you have the SIP message trace it would be easy to figure it out. Do you have one? http://wiki.snomone.com/index.php?title=Logging_SIP_Settings has some help if you want to know how to get SIP logging if you are running older versions of PBX. If you are running the newer versions of PBX, you can just set the "Log call messages" and ignore rest of the settings on the "Logging" page.