On Mon, 2008-06-16 at 16:03 -0400, Hegner, Travis wrote: > Hello Everyone, > > > > I am testing 3.11.4-012884 with Exchange 2007.
That's really a sipx-dev list issue, since that isn't nearly a stable version yet. > I am having an issue with my Exchange AA while transferring to a sipx > extension. The Exchange server uses a REFER to initiate the transfer, > to which sipx replies with a “407 Proxy Authentication Required”. In > order to utilize the Exchange AA features, I have it set up as a > gateway with a custom dialplan. I can not find any way to force sipx > to not require authentication from just that server, nor a way to > allow exchange 2007 to authenticate. > Any help is greatly appreciated. There is a hack in sipXecs to help with compensating for some bad behavior of Exchange. Check to see if your /etc/sipXproxy-config file has these lines in it: SIPX_PROXY_HOOK_LIBRARY.210_msftxchghack : /usr/lib/authplugins/libMSFT_ExchangeTransferHack.so SIPX_PROXY.210_msftxchghack.USERAGENT : ^RTCC/ turn the sipXproxy logging up to DEBUG and get a message trace. -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
