YMSL

Thanks for your reply,

I am trying to use Incoming anonymous calls behaviour "Pretend to be busy" to send Incoming anonymous calls to voice mail. When set, it act exactly like "reject call" and tle the anonymous caller that I do not wish to get calls from anonymous callers. Is their anything I am missing? PBXnSIP: 4.3.0.5021 (Win32) It does the same for previous version... thanks for your help

Many thanks for your reply, PBXnSIP, now SNOM, did make the PnP for Polycom. Keven Moros even recommend Polycome for conference phone. That before PNXnSIP was acquired by SNOM. PNP are available but their is certainly a bug their. the licence we are using is (C:\Program Files\pbxnsip\PBX) Please advise. In regards of FreeBSD... I am very sorry, but it look something like no details to the little elements are in place. To me it look like if this is their, who know what at other places that we do not know... Sorry to be so attentive to details. Many thanks again

I am trying to auto provision Polycom IP6000 with all proper settings Mac ID OK PNP OK Network OK Polycom auto provisioning is orking fine internally as long as SIP IP Replacement List and IP Routing List are empty. In this situation, devices on the other side of NAT (outside of the local domain) are not providing audio. To get device working fine outside internal network, SIP IP Replacement List and IP Routing List need to be set. In that case, Polycom auto provisioning is not longer working... It look like it is one or the other... what am I missing? SIP IP Replacement List: 10.0.1.200/24.202.225.XXX IP Routing List: 10.0.1.1/255.255.255.0/10.0.1.200/0.0.0.0/0.0.0.0/24.202.225.XXX PBXnSIP Version: 4.3.0.5021 (FreeBSD) - error here, it is running on OSX machine and it say's FreeBSD... If SNOM can trade my polycom IP6000 (just received and NEW) for a MeetingPoint. I am more then willing to trade it :-) Many thanks for your help

I have identified the problem without beiing able to solve it. Version 4.0.1.3499 is doing something on DTMF signaliing with Mediatrix 1204 v5 (all) making the DTMF to other PBX not understanding DTMF for AA. The only setting that work but ONLY with another PBXnSIP will be : voiciIfDtmfTransport : outOfBandUsignRtp This will not work with other pbx ... So if you PBXnSIP is usign Madiatrix 1204 v5 (all) stay away from PBXnSIP 4.0.1.3499 for now. I found no possible ways of getting it respecting all confirmity and Interoperabilities with mediatrix products. PBXNSIP version 3.4.0.3201 is working fine in conjonctions of Mediatrix 1204 voiciIfDtmfTransport : inBand I learned that in the very hard way... Mediatrix frimware version: 1204 V5.0.27.222 SIP MIB 1.5.3.100 PBX support... what would you need, what can I provide you to get this fixed... PCAP but How and what? many thanks

Many thanks for the reply, Strange, because the phone (SPA504G) refuse to register if cable is not shorter... may it be a limitation of the phone with cable lengh? Really need a solutions here!

Can anyone recommend a suitable hardware to regenerate signal, what should I buy if I must be running for 250 ft? Kind of urgent please regards

Since version 4.0.1 have been introduce (great version), Cisco phones that are using TLS and NOT UDP or TCP are no longer registering at all. If I downgrade back to 3.4.X, Cisco Phones using TLS are working just fine

Like all 4.0.X previous version, when calling from 4.0.X to a 3.4.X system, reaching AA. DTMF isn't working at all -- like if 4.0.X is not sending proper DTMF signal to 3.4.X

Certificat? We are not usign certificat with TLS and never used. What setting do you want for SharkTrace?

3.4.0.3201 system is running with Cisco phone, one particular is usign SIP settings TLS protocol Cisco SPA962 frimware V. 6.1.5 (a) When usign PBXCTRL version 4.0.1.3475 the same Cisco phone is never registering. I have tested another Cisco phone, different model and different Frimware, same issus. So I come to the conclusion that TLS on V 4.0.1.3475 hav a little something to prevent Cisco phone to work.

Current build 4.0.1.3446 still not woring properlly with DTMF detections. Outboud and in bound calls are not detecting DTMF with Mediatrix 1204. Exacte same coniguration is working fine with version 3 of pbxnsip

I should not comment at all...

Is it just me that have the impression that PBXnSIP company and software is fadins out... Their is not mutch activities on the forum and not release since several mounts... V 4.0 hase not showed any public info since past may... Hope I am mistaking