Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Organization: SipXecs Forum In-Reply-To: <aa5e.4ba54...@forum.sipfoundry.org> X-FUDforum: 08063afcdd00a6e76393c5b9527381e8 <43714> Message-ID: <aac2.4ba8d...@forum.sipfoundry.org>
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:d3d1b2eac11af...@home.dejagers.net;gr> Should this contain something like: Contact: <sip:mailto:2...@192.168.2.254: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? _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org 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/
