The polycoms should then need to be able to resolve the domain names and route them the same, and be using current firmware (3.2.6 or earlier). If the FXS is on a different subnet and uses a different DNS resolver, I would start there.
On Mon, Apr 16, 2012 at 1:06 PM, Mike Graham <mike_gra...@hempfieldsd.org> wrote: > > Content-Type: text/plain; > charset="utf-8" > Content-Transfer-Encoding: 8bit > Organization: SipXecs Forum > In-Reply-To: <107ad.4f8c2...@forum.sipfoundry.org> > X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <67511> > Message-ID: <107b7.4f8c5...@forum.sipfoundry.org> > > > > I'm double checking DNS now. Interesting, we have an FXS > ATA attached to domain A that domain B has no trouble > transferring. The transfers only fail on a Polycom phone. > > Mike > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: tgrazi...@voice.myitdepartment.net Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: helpd...@voice.myitdepartment.net Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
