Hi all,
 
This improvement request has been captured in XCF-3397: Polycom Outbound
Proxy - use per-Phone settings for default when possible.
 
Thanks.



-Paul 
[email protected] 

 


________________________________

        From: Tony Graziano [mailto:[email protected]] 
        Sent: February 20, 2009 9:41 AM
        To: Mossman, Paul (CAR:9D30); [email protected]
        Cc: Parfitt, Christopher (MOP:9D30)
        Subject: Re: [sipX-dev] Polycom Remote Worker - Outbound Proxy:
per-Phone orper-Line?
        
        
        Agreed, it should be easier to configure and find. In my case I
have one remote worker with a phone registered via two different sipx
systems. It is enormously helpful to have this easier to understand,
though I think the help text provided actually needs to alert the admin
to the possibility of the pitfalls of just such a configuration.
        
        We're in the process now of trying to understand why the remote
line can register & receive incoming calls, but when dialing voicemail,
it is not recognized as an internal line (user has to put in line & pin
to check voicemail) and calls outbound via the ITSP have one way audio
issues, when everything is privately routed via VPN and nothing is
blocked. Even though it is set to use the correct outbound proxy for
that account.
        
        So if everyone feels this is supportable, then it would be good
to have a how-to guide on the wiki for those of us who still can't quite
get it yet.
        
        Tony
        
        >>> "Paul Mossman" 02/20/09 8:56 AM >>> 

        Hi all, 

        Polycoms have two locations for setting the Outbound Proxy.  The
first is a per-Phone setting on the "SIP Servers" screen.  The second is
a per-Line setting under "Lines" -> X -> "Registration" (and "Show
Advanced Settings".)

        Chris recently asked me which one should be adjusted in the case
of a Remote Worker Phone. 

        The correct answer is the per-Line setting.  This is because a
non-blank per-Line value overrides any per-Phone value, and with
XCF-1614 the per-Line default value is now the Line's SIP domain (i.e.
non-blank.)

        The problem is that the GUI tempts you to configure the
per-Phone setting, which is wrong: 
        - A superadmin who starts looking will almost surely find this
setting first, since it isn't buried under Lines or tucked away under
Advanced.

        - The default value is currently blank, which might lead you to
believe you can simply fill in the desired Outbound Proxy value and be
done.

        - The help text doesn't give you any indication that the value
will be ignored because the per-Line setting is non-blank.

        We should fix this.  But rather than directing the superadmin to
the hard to find setting, let's turn the easy to find setting into the
correct one.

        In most cases a Phone will only ever need a single Outbound
Proxy, so let's use the per-Phone setting.  i.e. The SIP domain of the
first Line is used as the default per-Phone value.  All Lines using this
SIP domain will have a blank default per-Line value, so that the
per-Phone value is used instead.

        Occasionally a Phone will also have an External Line, which
means a different Outbound Proxy will be required.  In this case the
per-Line default value will be the SIP domain of that Line, so that the
per-Phone value is overridden.  (Help text will be added to the
per-Phone setting indicating a non-blank per-Line value takes
precedence.)

        For a Remote Worker Phone the superadmin will only need to
adjust the single per-Phone Outbound Proxy value, which is easy to find.

        In rare cases a Phone will have an External Line where the
default Outbound Proxy value is not correct.  But even in this case I
think the correct action will be intuitive: The External Line's Outbound
Proxy value must be changed, not the per-Phone value.

        I think this approach will make the typical Remote Worker case
considerably easier, without introducing any confusion to the rare case.

        Thoughts? 


        -Paul 
        [email protected] 


_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to