the sipx server is plugged in directly to our switch, no firewall in between, also no NAT. that is what puzzles me. there should not be any issues with nat traversal on the server end.
I'll try the tcpdump and update you On Mar 9, 2010, at 10:13 AM, Robert Joly wrote: > Francis, > I think that the quickest path to understanding your problem would be to > provide either a sip trace as Scott requested or provide a network trace by > running tcpdump -n -nn -s 0 -i any -w remote_user_problem.cap directly from > your sipXecs. > > What kind of router is at the remote location and did you ensure that its SIP > ALG was disabled (if supported)? > > bob > > From: sipx-users-boun...@list.sipfoundry.org > [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Francis Tinio > Sent: Tuesday, March 09, 2010 9:48 AM > To: Tony Graziano > Cc: sipx-users > Subject: Re: [sipx-users] deployed new sipx server....3 phone extensions,only > 1 is accessible inbound > > also, one thing I noticed is that when I first configured the 1st extension, > it was able to accept inbound calls. But once I provisioned the next 2 > phones, only the last provisioned phone was accepting calls and the 1st would > now reflect as user offline (although it still shows registered and can make > outbound) > > > On Mar 9, 2010, at 9:42 AM, Tony Graziano wrote: > >> Oh, those phones are very old and at end of life, they stopped being able to >> provide updates some time ago because the resources were not on the devices >> to take the new code. I would try with 550's or 650's and 3.1.3RevC and see >> if you have the same issue. >> >> On Tue, Mar 9, 2010 at 9:40 AM, Francis Tinio <fti...@toqen.com> wrote: >> ip500 cannot use firmware 2.1.3 and below. it cannot use any newer. and >> 2.1.3 seems buggy that everytime i use it, the icons do not show right so >> i'm using 2.1.2. >> >> >> On Mar 9, 2010, at 9:38 AM, Tony Graziano wrote: >> >>> You should be using firmware 3_1_3_RevC and nothing later with 4.0.4. >>> >>> On Tue, Mar 9, 2010 at 9:26 AM, Francis Tinio <fti...@toqen.com> wrote: >>> I'm running the latest stable of sipx. 4.0.4 I think. >>> >>> For polycom, it's ip500 and the latest software and bootrom are buggy, so I >>> downgraded 1 version down. I don't think the problem is with the firmware >>> though. >>> >>> >>> On Mar 9, 2010, at 9:15 AM, Scott Lawrence wrote: >>> >>> > On Mon, 2010-03-08 at 16:46 -0500, Francis Tinio wrote: >>> >> >>> >> I deployed another sipx server (server is remote located with public >>> >> IP (firewall is within server, no NAT). I provisioned 3 polycom >>> >> phones. All 3 phones are created via phone group, so all have the >>> >> same settings. All 3 phones have successfully registered with the >>> >> server as well and all 3 phones can make outgoing calls. >>> >> >>> >> However, incoming call does not work. Only the last extension >>> >> provisioned can receive incoming calls. With the other 2 extensions, >>> >> I get a user is unavailable and get directed to voicemail. Even >>> >> internal calls within extensions, the 2 phones cannot be reached and >>> >> i'm getting the same message that the user is offline. >>> >> >>> >> What could be wrong? I checked the phone settings of the three phones >>> >> and they are all similar. All 3 phones are registered and can make >>> >> outbound. >>> > >>> > What version of sipXecs are you running? >>> > What version of the polycom firmware? >>> > >>> > What evidence are you using that the phones are registered? icon on the >>> > phone? registrations display on sipXecs? >>> > >>> > When you say that they have the same settings, does that include that >>> > they have the same user configured, or is each a separate line? >>> > >>> > Have you tried getting a call trace of a successful and an unsuccessful >>> > call to see how they differ? See: >>> > >>> > http://wiki.sipfoundry.org/display/xecsuserV4r0/Display+SIP+message+flow+using+Sipviewer >>> > >>> > when you get the trace data, take a look at it using sipviewer >>> > and/or post the trace with a description of your configuration >>> > (identify components by IP address), what you were doing, and >>> > which call in the trace you're talking about (by call-id or >>> > frame number in the trace, preferably). >>> > >>> > >>> >>> _______________________________________________ >>> sipx-users mailing list sipx-users@list.sipfoundry.org >>> List Archive: http://list.sipfoundry.org/archive/sipx-users >>> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users >>> sipXecs IP PBX -- http://www.sipfoundry.org/ >>> >>> >>> >>> -- >>> ====================== >>> Tony Graziano, Manager >>> Telephone: 434.984.8430 >>> Fax: 434.984.8431 >>> >>> Email: tgrazi...@myitdepartment.net >>> >>> LAN/Telephony/Security and Control Systems Helpdesk: >>> Telephone: 434.984.8426 >>> Fax: 434.984.8427 >>> >>> Helpdesk Contract Customers: >>> http://www.myitdepartment.net/gethelp/ >>> >>> Why do mathematicians always confuse Halloween and Christmas? >>> Because 31 Oct = 25 Dec. >>> >> >> >> >> >> -- >> ====================== >> Tony Graziano, Manager >> Telephone: 434.984.8430 >> Fax: 434.984.8431 >> >> Email: tgrazi...@myitdepartment.net >> >> LAN/Telephony/Security and Control Systems Helpdesk: >> Telephone: 434.984.8426 >> Fax: 434.984.8427 >> >> Helpdesk Contract Customers: >> http://www.myitdepartment.net/gethelp/ >> >> Why do mathematicians always confuse Halloween and Christmas? >> Because 31 Oct = 25 Dec. >> >
_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
