> 
> Scott Lawrence wrote: 
> 
>       On Thu, 2009-02-26 at 13:57 -0500, Joly, Robert 
> (CAR:9D30) wrote:
>       
>         
> 
>                       I think that our presumption should be 
> that the 'default' 
>                       behavior of anything should work 
> smoothly in an HA environment.
>                             
> 
>               Not configuring the outbound proxy will 
> effectively break call
>               pickup/call park when phones behind remote NATs 
> are involved.  Any
>               direction we go, we lose functionality.  LG 
> already supports SRV lookups
>               - do we have an assesment from them as to how 
> much complexity would be
>               involved in fixing this?
>                   
> 
>       
>       I understand, and clearly getting the phone fixed is 
> the real answer.
>       However - in the mean time there will be more local 
> phones on HA servers
>       than remote phones on either flavor, so the defaults 
> should be set
>       accordingly.
>       
>         
> 
> Also for the remote worker phones, the outbound proxy in most 
> cases is set to the external facing IP address of the SUT  - 
> which btw has to be set manually anyways. 

It is true but but does not have to be that way.  The recommendation for
HA and remote workers would be to configure an outbound proxy (if it
worked properly) and use split DNS.

> Therefore I think 
> the default of not having an outbound proxy is a good choice 
> till such time that LG fixes the issue. 

For the record, if a local phone does not use outbound proxy, that will
prevent it from successfully completing some call pickup/call park
scenarios when a remote worker is the target of the pickup or transfer.
Having said that, I agree with your recommendation of not using outbound
proxy for LG.

_______________________________________________
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