pbx support

Interesting. We tried black listing address/contact both on domain level and user level. It worked perfectly fine. We have tested this on Windows version.

Is there any log (with log level 8 and everything but the CPU intensive turned on)? It would be helpful if the log is taken when nothing else is going on. Of course, if you do not want to post it here, PM to support@pbxnsip.com

Do you mean once you hit 4, it has to go to another AA? I maybe missing the point here.

Please checkout http://wiki.pbxnsip.com/index.php/Simple_C...at#CDR_XML_file

That should be working. We have tried it here and using it BTW on windows. All you have to do is put the MAC addresses separated by space under "Registration->Bind to MAC..." field. Any specific OS?

Yes. Check out the last paragraph http://wiki.pbxnsip.com/index.php/PAC#Repl...ackground_image

That may be the issue. If you follow the wiki, http://wiki.pbxnsip.com/index.php/PAC#Monitoring_extensions, it has a screen shot that shows how and what to configure.

Do you have any extensions configured to monitor?

which is the current version of software you are running? We are running 3.3.1.3177 (http://pbxnsip.com/download/pbxctrl-3.3.1.3177.exe) and do not see this issue.

There was an issue in that version. We have created a new version that fixes this issue http://pbxnsip.com/cs410/update-3.3.2.3181.tgz

Try turning on the recording settings on the extension itself and see if it fixes the issue.

Thanks Alex. I think we have to clarify in the wiki that one can use the config files shown in the wiki page if the PnP does not work for some reason. Please send the markup file to Pradeep and he will take care of the rest!

Let me try to understand the setup here first - you have a PBX in the USA receiving calls for number starting with 44xx......?

What is the software version you are running? I tried it on .3177 and a limited release .3181. Both seem to work fine.

Tested the same thing on .3177 here (Windows version). Did see the problem. Any more details? Are you repeating the speed dial star code?

Well, if you keep the default value "Entering the Agent group" for "Event for connecting the call" AND "Regular ringback when agent rings" for "Ringback tone" (the very next field), you will achieve what you want. But as 'pbxnsip' mentioned in one of the earlier responses, the caller will be charged from the beginning. With these settings, the caller will be connected at the beginning itself, the 90 seconds issue will not arise.

Can you increase the log level to 8 and send us the log for this case? something does not seem right. Also, can you tell us what is set in "Event for connecting the call" field for the agent group?

Well, based on the above log file, there are 2 UAs registered for extension 210 (destination). That is definitely a reason why intercom did not work. Polycom [9] 2009/04/17 13:42:23: SIP Tx udp:209.190.xxx.xxx:59342: INVITE sip:210@10.0.0.76 SIP/2.0 x-lite SIP Tx udp:209.190.xxx.xxx:49274: INVITE sip:210@10.0.0.65:40048;rinstance=50629d8654072332 SIP/2.0

We will take a look at this

We do have PnP support for CISCO 7960. Although we have not really re-tested it in the recent versions. We do require that CISCO firmware files be in the TFTP folder for any phone version upgrades. If you can not get the PnP going with the 7960 for whatever reasons, you can follow the wiki to make it work in a semi-PnP fashion. BTW, 79x0 do not support xml. There are for 79x1 phones.

Not much progress has happened on the PAC front in the last month. Once we release 3.3.2.x and major issues are resolved (if any), PAC will get a chance again!

I am not sure what to say here.. why do they offer RFC2833 when they ask to you use inband DTMF? pbxnsip works fine with both in-band and out-of-band(end to end). What we did not support is one leg in-band and other leg out of band. But we have added that support now and is in the testing phase.

TLS port setting is in Admin->Settings->Ports page

Hmm, looks like that file is not being used in the latest 3.0 version. So it might have been removed. Alternatives: 1) you can record a file and copy it as mb_to_copy.wav into the audio_en folder (you have to record with 8kHz, 16 bit mono or use the AA to record this file) 2) Upgrade to latest software version that is on the download page.

Have you tried downloading the latest audio files from the download page?