Re: [asterisk-users] Polycom Blf / Directed Pickup

2011-01-13 Thread Sebastien Thomas
/etc/asterisk/sip_custom.conf callevents=yes notifyringing=yes limitonpeers=yes I also override some of the sip.cfg settings in the polycom dir with: --- Sebastien Thomas Amplisys Inc. - Digital Telephony Integration Specialists T: 514.225.4141 x222 F: 514.225.4162 TF: 1-877-AMPLISYS

Re: [asterisk-users] Polycom Blf / Directed Pickup

2011-01-13 Thread Sebastien Thomas
Is the buddy watch tag activated in your -directory.xml file ? 1 Sebastien Sebastien Thomas 222 1 1 --- Sebastien Thomas Amplisys Inc. - Digital Telephony Integration Specialists T: 514.225.4141 x222 F: 514.225.4162 TF: 1-877-AMPLISYS On 2011-01-13, at 1:32 AM, Mark Murawski wrote

Re: [asterisk-users] Recommendation for a new server

2010-10-21 Thread Sebastien Thomas
I just put in an HP DL360 G6 for a client spec with a Sangoma 4x PRI, a Sangoma 4x FXS and about 150 devices. Running live now on 1x PRI approx 20-calls and 60 phones, load is at zero. We went with the base machine Xeon 5500 + 4GB RAM, 2x PS, 2x HD (raid mirror)... about 3K$ but Im certain we

Re: [asterisk-users] Polycom getting DCHP address from wrong VLAN

2010-10-08 Thread Sebastien Thomas
One more thing: Make sure that the port going to your data-DHCP server doesn't have the voice VLAN set on it. I troubleshot an installation for a few hours before thinking of this... Bests, Seb On 2010-10-08, at 2:37 AM, Thermal Wetland wrote: > Hello, > > I have been tearing my hair out on

Re: [asterisk-users] Polycom getting DCHP address from wrong VLAN

2010-10-08 Thread Sebastien Thomas
t VLAN to the Polycom. We did this kind of setup in a large scale (100+) installation. Bests, Seb --- Sebastien Thomas Amplisys Inc. - Digital Telephony Integration Specialists T: 514.225.4141 x222 F: 514.225.4162 TF: 1-877-AMPLISYS On 2010-10-08, at 2:37 AM, Thermal Wetland wrote: &

Re: [asterisk-users] Polycom dhcp boot

2010-09-13 Thread Sebastien Thomas
Your string and boot-option look good. In the SonicWall config, its a two step process: - create the new boot option under "DHCP Server" menu > "Advanced" button > "Add Option" - assign it to your lease scope under "DHCP Server" menu > "DHCP Server Lease Scopes" section > "Edit" button > "Advanc