It is not recommended to have the same line provisioned on more than 5 polycom phones.
If you are doing this, then DON'T. Polycom has a big "DON'T" on that, and it would explain a lot. Hunt group or not. Thanks for solving this mystery. The cause is not sipx or lan. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: [email protected] <[email protected]> To: Discussion list for users of sipXecs software <[email protected]> Sent: Sat Nov 20 13:50:31 2010 Subject: Re: [sipx-users] Inbound Verizon Callers @R P - It doesn't matter which phone we unplug to reduce to 7 phones, or which phone we delay the ringing. It still works with 7 or less phone, not with 8. @Michael - we have two numbers A and B. A goes to a hunt group with the 8 extensions assigned to line one of the phones, the extension being the phone number calling in. Number B goes to a user, that user is assigned to line 2 one all 8 phones. The issue is there either way. If I look at a TCP dump from the SipXecs server what I see is we recieve the invite and respond with a 100 Trying, and 180 ringing while the SipX box starts inviting the 8 phones. before some one can answer we receive a cancel, but only if all 8 phone ring a once. If we set one extension to ring if no answer, or remove the number 2 user from one phone all calls comes in fine. Bryan On Fri, Nov 19, 2010 at 3:22 AM, Michael Picher <[email protected]> wrote: > What does the inbound ringing look like? Are you trying to ring all 8 > phones at once? If so, how are you doing it? Hunt group or a separate > user > on each phone or a phantom user with forwarding to ring at the same time > on > a bunch of phones? > > Mike > > > On Thu, Nov 18, 2010 at 5:40 PM, R P Herrold <[email protected]> wrote: > >> On Thu, 18 Nov 2010, Bryan Anderson wrote: >> >> > All phones get their IP's from the DHCP server distributed >> > on the SipXecs ISO. >> >> It is not unheard of for a MAC address, which is used to try >> to ensure uniqueness of IP assigmment to be duplicated by a >> hardware vendor [I have some specialty hardware that >> intentionally does just that] ; similarly an IP assignment >> pool can sometimes be exhausted >> >> IP conflicts on a lan can cause failures. >> >> I think I would be firing up tcpdump on the monitor port of a >> switch, or setting up hubbed fabric between the DHCP server >> and the rest of the LAN, and watching the DHCP assignment >> conversations closely [port 68] as I plugged and unplugged >> units at this point >> >> something like: >> tcpdump -i eth0 -nN -xX -s 1500 port 68 >> >> see for more details: >> http://www.owlriver.com/tips/tcpdump-tech/ >> >> -- Russ herrold >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> > > > > -- > There are 10 kinds of people in this world, those who understand binary > and > those who don't. > > [email protected] > blog: http://www.sipxecs.info > call: sip:[email protected] <sip%[email protected]> > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
