DND issue with Mitel phone

ok, its fixed now. After adding option "promiscredir=yes" to sip.conf for Mitel extension it works fine.

It fixed DND mode, but disrupt call forward (noanswer/busy/all). It says in log
"Sent into invalid extension '"
Executing [i@from-outside-redir:3] Zapateller("Local/12312321@from-outside-0072;2", "") in new stack
When I remove "promiscredir=yes" the forwarding is working properly, but DND doesn't, as mentioned Had. Any idea how to get both these features working?

Seems this issue touch only thirdlane system. What we have:

During forwarding in SIP packet (SIP/2.0 302 Forwarding...) we have:
Contact:sip:1008@11.22.33.44

During dnd in SIP packet (SIP/2.0 302 Busy Here) we have:
Contact:sip:1009-moc@11.22.33.44:5060

Seems that the system can't find 1009-moc.

Workout for this: create PBX Feature->Feature Codes for each extension:
Feature Code: 1009-moc
Description: voicemail-workaround
Script: tl-goto-voicemail
Mailbox: 1009

what is moc?

you realize that you could probably get away with a pattern instead of a feature code for every extension.

It is Tenant name.
Forget to mention that we use Multitenant version

You are right about pattern, but it need additional coding, creating new script.

Hi,

We have the same issue with a mitel deployment. It looks like the redirect uses the -tenantname in the sip response which causes * to give the invalid extension message. Any workaround for this ? Is this to be expected. Most endpoints return 486 .. not 302.

Thanks

have you tried to add extension-tenantname to featurecodes, as described above? In this case asterisk will recognize it.

No but in understand that it will work. However this is not a scalable workaround since this project / tenant has over 200 extensions. I don't want to create a FC for every single one of them. not to mention the overhead this will introduce. is there a way to fix this using variables and scripting ?

Please advise

Alex

are you trying to re-use existing mitel sip phones? or did you just like the mitel phone so much thats what you wanted to roll out? It doesnt sound too good of a deal if its not sending a 486 on DND. IS there no way to program them to do 486 on DND? I would think that would be a setting somewhere on the phones.

After multiple calls with MItel I understand that this the way it is ... :-( A workaround hint other than feature code would be greatly appreciated. We also found that there is an issue with BLF "early" state doesn't seem be working. Only Active or Idle. And yes we where forced into this project with Mitel phones :-)

Thanks

Alex

Don't you have any other issues with Mitel phones (except DND and forwarding)?
We have completely stopped using them. Mitel phones in Minet mode seems to be great phones but when they are switched to SIP mode they don't seems to be that good any more. We had issues that the phones stopped responding to SIP option and also stopped re-registering (and similar). We also tried the latest SIP firmware but that didn't make no difference.
After all we have replaced all Mitel phones for Polycoms and problems disappeared.
What's your experience with Mitel phones?

Peter (Had)
Trinitel Ltd
www.trinitel.co.uk

Hi we still use them for a few of our customers and found out that there are 2 items that require attention

1: SIP 302 instead on 486 on DND
2: BLF Implementation

In regards to the BLF implementation, they use a Broadsoft alike "BLF list" approach. The busy and idle state work great, but the "early" state (when the phone is ringing) is completely ignored by the telephone.

Has anybody implemented BLF Lists instead of multiple hint registration in Asterisk ? Is there such compatibility with Broadsoft's BLF implementation ?

Alex