Good tip, thanks. Turns out it was a 401 authorization error and I found a thread from last Dec. where someone else had the exact same problem with Aastra's. The proxy port must be set to 0 in the MAC.cfg file. The Aastra module sets this to 5060 by default and that creates the problem. There was some speculation in the thread that it was also domain name sensitive, where a host name would not work with Aastra's due to the way they queried DNS for SRV records, but I found it's less sensitive to this (host name, domain name, or even IP address works) and more sensitive to having proxy port set to 5060. I imagine I should file a change request for this, but for now I think I'll build a custom version of the Aastra jar.
Bruce On 10/5/09 10:24 AM, "Dale Worley" <[email protected]> wrote: > On Mon, 2009-10-05 at 09:38 -0700, Bruce Reed wrote: >> Any ideas on how I should shoot this problem or does anyone know if >> this is a known problem with Aastra¹s and sipXecs? > > Set logging to DEBUG level. Reboot the Aastra. When it's running, > leave a message on voicemail for it. Observe that MWI light does not > come on. Take snapshot. > > Examine snapshot to determine why the SUBSCRIBE from the Aastra does not > work correctly. > > Dale > > _______________________________________________ sipx-users mailing list [email protected] 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/
