> 2008/7/19 Mark Wiater <[EMAIL PROTECTED]>: Your problem is the Contact header coming back in the Mitel's Ok response.
Contact:"p:[EMAIL PROTECTED]>;tag=4881ea36-2ca-6747d965 Asterisk is not going to be able to parse that! It should be: Contact: <sip:[EMAIL PROTECTED]>;tag=4881ea36-2ca-6747d965 I'd get your Mitel vendor to log a fault about that. It's a big problem as the Contact field is critical for further in-dialogue SIP requests such as transfer related requests and BYEs. Regards, Greyman. _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users