On Fri, Apr 29, 2011 at 11:25 AM, George Niculae <[email protected]> wrote:
> > On Wed, Apr 13, 2011 at 8:22 PM, andrewpitman <[email protected]>wrote: > >> >> >> >> I've noticed something odd while testing shared line >> appearance for remote workers in sipXecs 4.4.0. My phones >> are Polycom 450s running firmware 3.2.5, but I noticed the >> same behavior in 3.2.4. >> >> When my remote workers' primary (non-shared) line and the >> shared line have TCPonly set for "Outbound Proxy Transport" >> for their registrations, there is no line presence >> indication shown on any of the other phones when a call is >> up on the shared line. When I set the registration for the >> shared line only to be UDPonly on all the phones, shared >> line appears to work normally. That is, a solid light for >> the appearance when on a call, blinking when on hold and the >> call on hold can be picked up on any phone with the shared >> line when blinking. >> >> Has anyone else seen this? >> > > Could you please provide a packet capture? As I understood TCP is really > hard to traverse over NAT. Joegen suggested that If you get this all the > time, a snoop from sipx towards the concerned phone would be helpful and > easy to collect. > > Andrew, not sure why I didn't receive your replies to this post, I noticed on forum you replied 2 times http://forum.sipfoundry.org/index.php?t=msg&th=15696&goto=58586&S=3af7dece4cd843cc17d88432ca87d9a3#msg_58586 Will look at provided dump and come back to you George
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
