(Dale... if you're going to get active on supporting these phones, which would be very very welcome, it would work better if you used the mailing lists directly - the threading from the forums is not very good, and they are evidently corrupting some of your message: see the insertion of 'mailto:' schemes into the addresses below).
On Tue, 2010-03-23 at 10:41 -0400, Dale D wrote: > I have a bit more information on this problem. I appears > from the trace that I've uploaded in my prior email that > after the 180 Ringing message from the aastra phone, the > phone is returning a 200 OK message that contains a bad > Contact: field. It contains: > Contact: > <sip:~~gr~mailto:[email protected];gr> > Should this contain something like: > Contact: > <sip:mailto:[email protected]:5060;transport=udp> > > Because of this the ACK for the OK is never received by the > Aastra phone and it times out. (The trace shows the ACK > goes to the proxy and never gets to the calling phone.) > > Does this make sense? Can someone confirm for me that it is > an Aastra problem and not a sipXecs problem by looking at > the SIP trace info? The Astra is trying to use a 'gruu'; this is a form of the contact that is (should be) globally routable. Some older versions of sipXecs have some issues with these (which we believe are fixed in the current development version). You may be able to make progress by disabling support for gruu in the phones until you can move to the latest sipXecs. _______________________________________________ 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/
