> 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: ;tag=4881ea36-2ca-6747d965
I'd get your Mitel v
Maybe stupid solution but, when Mitel phone i called, why dont you pickup
put the person on hold, call Mitel phone, and connect them, what i want to
say, add some delay.
2008/7/19 Mark Wiater <[EMAIL PROTECTED]>:
> Matt Watson wrote:
> > On July 19, 2008 11:22:08 am Mark Wiater wrote:
> >> Hi,
>
Matt Watson wrote:
> On July 19, 2008 11:22:08 am Mark Wiater wrote:
>> Hi,
>>
>> I have a client using Mitel 5212 phones in SIP mode with a 1.4.21.1
>> Asterisk server (and a couple of previous 1.4 versions). They're
>> mostly happy with the combination except for this one issue.
>>
>> For incomin
On July 19, 2008 11:22:08 am Mark Wiater wrote:
> Hi,
>
> I have a client using Mitel 5212 phones in SIP mode with a 1.4.21.1
> Asterisk server (and a couple of previous 1.4 versions). They're
> mostly happy with the combination except for this one issue.
>
> For incoming calls only, either origina
Hi,
I have a client using Mitel 5212 phones in SIP mode with a 1.4.21.1
Asterisk server (and a couple of previous 1.4 versions). They're
mostly happy with the combination except for this one issue.
For incoming calls only, either originating from other local SIP
phones or from a PRI, calls won
