1
Mitel MiVoice Business/MCD/3300 / Re: Hot Desking
« on: July 24, 2019, 11:32:22 AM »
Thanks for your comments, will adjust our settings accordingly and see what happens!
News:
Welcome to Mitel Forums. The Mitel resource - by techies, for techies...
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
2
Mitel MiVoice Business/MCD/3300 / Hot Desking
« on: July 24, 2019, 10:34:37 AM »
Hi all,
We have a Mitel 3300 with 5312 handsets.
We want to set certain users up as 'hot desk' users so they can login to other handsets using the hot desk login/logoff feature access codes. While this does seem to be working we have an issue we can't work out.
If the user logs in to another handset it all works fine on that new handset but the handset designated as their base handset (which is the handset on their main desk) disassociates itself from the phone system and sits there with 'USE Superkey TO SEND PIN' on the display. Under 'Service Profile' for the relevant user who wants to hot desk, all we are changing is 'Hot Desking User' to 'Yes' for this feature to work.
Is there some way we can set their main phone handset on their main desk as some sort of 'dummy' phone which they log in to when sat there, but when they go elsewhere and login on another handset it doesn't become disassociated from the phone system, and simply sits on a user login type of prompt?
Hope the above makes sense, appreciate any suggestions!
We have a Mitel 3300 with 5312 handsets.
We want to set certain users up as 'hot desk' users so they can login to other handsets using the hot desk login/logoff feature access codes. While this does seem to be working we have an issue we can't work out.
If the user logs in to another handset it all works fine on that new handset but the handset designated as their base handset (which is the handset on their main desk) disassociates itself from the phone system and sits there with 'USE Superkey TO SEND PIN' on the display. Under 'Service Profile' for the relevant user who wants to hot desk, all we are changing is 'Hot Desking User' to 'Yes' for this feature to work.
Is there some way we can set their main phone handset on their main desk as some sort of 'dummy' phone which they log in to when sat there, but when they go elsewhere and login on another handset it doesn't become disassociated from the phone system, and simply sits on a user login type of prompt?
Hope the above makes sense, appreciate any suggestions!
3
SIP On Mitel / Re: External Transfer on 3300 with SIP
« on: October 12, 2016, 05:13:13 AM »
Thanks all for your assistance.
4
SIP On Mitel / Re: External Transfer on 3300 with SIP
« on: October 11, 2016, 04:57:25 PM »
Hi, thanks for the reply, there is no MBG.
5
SIP On Mitel / External Transfer on 3300 with SIP
« on: October 11, 2016, 11:24:34 AM »
Hi all,
We have a Mitel 3300 using a SIP supplied by a national UK provider.
Everything works as it should, but we're unable to transfer calls to an external number. For example, if someone calls our office, and we want to transfer that call to a staff member's home number (if they're working from home) the call goes through but there is no voice, on either end.
We used to have a SIP trunk provided by BT, who used a Proxy, and this external transfer worked fine. We've made no other changes other than the SIP provider (who don't use a Proxy). We're assuming it's Firewall/NAT related, but Wireshark shows both RTP streams are successful, and there's no lost packets, it's almost as though the two streams aren't being connected together as a complete call.
Wireshark shows the internal IP address of the Mitel handset making the external transfer on the OK200, which I gather is normal for a Mitel system, should this be set to the external IP address of the PBX somehow, or is this behaviour OK?
Does anyone have any ideas? Thanks
We have a Mitel 3300 using a SIP supplied by a national UK provider.
Everything works as it should, but we're unable to transfer calls to an external number. For example, if someone calls our office, and we want to transfer that call to a staff member's home number (if they're working from home) the call goes through but there is no voice, on either end.
We used to have a SIP trunk provided by BT, who used a Proxy, and this external transfer worked fine. We've made no other changes other than the SIP provider (who don't use a Proxy). We're assuming it's Firewall/NAT related, but Wireshark shows both RTP streams are successful, and there's no lost packets, it's almost as though the two streams aren't being connected together as a complete call.
Wireshark shows the internal IP address of the Mitel handset making the external transfer on the OK200, which I gather is normal for a Mitel system, should this be set to the external IP address of the PBX somehow, or is this behaviour OK?
Does anyone have any ideas? Thanks
6
Mitel MiVoice Business/MCD/3300 / Re: Incoming number display (SIP)
« on: May 06, 2016, 05:21:57 AM »
Thanks for that, our trunks' SDP and Header options are the same as yours, the only difference is we have 'AVP Only Peer' set to 'No' and 'Avoid Signaling Hold to the Peer' set to 'Yes' under 'SDP Options'.
Under 'Signaling and Header Manipulation' we have 'Use To Address in From Header on Outgoing Calls' set to 'Yes'
Not entirely sue any of those would make any difference? Maybe the AVP Peer one?
The trunks themselves are in a Class of Service group, could that be causing a problem? There are a set of display options in there.
Under 'Signaling and Header Manipulation' we have 'Use To Address in From Header on Outgoing Calls' set to 'Yes'
Not entirely sue any of those would make any difference? Maybe the AVP Peer one?
The trunks themselves are in a Class of Service group, could that be causing a problem? There are a set of display options in there.
7
Mitel MiVoice Business/MCD/3300 / Re: Incoming number display (SIP)
« on: May 05, 2016, 03:55:50 PM »
Hi, yes it is, and all with the same supplier. The issue is some numbers route via a different SIP server within the suppliers network but they are unwilling/unable to make any changes at their end as they say all their servers conform to the SIP standard (but they agree the numbers are being presented differently depending on which of their servers route which number) and it's down to us to amend our PBX accordingly.
8
Mitel MiVoice Business/MCD/3300 / Re: Inward Dialing Modification Tutorial
« on: May 05, 2016, 03:55:24 PM »
Thank you, I will try this tomorrow.
9
Mitel MiVoice Business/MCD/3300 / Re: Incoming number display (SIP)
« on: May 05, 2016, 11:28:44 AM »
Hi, yes we've tried that and it doesn't make any difference.
10
Mitel MiVoice Business/MCD/3300 / Incoming number display (SIP)
« on: May 05, 2016, 11:14:15 AM »
Thank you to everyone who helped on my previous post, I seem to unable to get that to work as I was expecting so maybe I'm looking at it from the wrong perspective. I'm starting a new thread as I believe this may be a different question/solution.
We have a SIP trunk that has lots of different numbers pointing to it. When we dial some of these numbers, the incoming call shows as it should (e.g. 01234 567890).
When we dial some of the other numbers, we get the 44 (e.g. 441234 567890)
I was hoping to be able to absorb the 44 and replace with a 0 but that didn't work out.
We've run a Wireshark trace and can see that on the incoming calls that display the incoming caller ID fine, the SIP header reads as:
From: <sip:01234567890@sip.provider;user=phone>;tag=xxxxxxxxxxxxxx
SIP from address: sip:01234567890@sip.provider;user=phone>
But on the calls that show the extra 44 information, the SIP header reads as:
From: "+441234567890"<sip:01234567890@sip.provider;user=phone>;tag=xxxxxxxxxxxxxx
SIP Display info: "+441234567890"
SIP from address: sip:01234567890@sip.provider;user=phone>
So, in essence, it's adding a 'SIP Display info' line to the header, then using the information contained within that to populate the 'From' header also.
So, is there a way to ignore the 'SIP Display Info' field and just use the number displayed in the "sip:01234567890@sip.provider" part of the header?
We have a SIP trunk that has lots of different numbers pointing to it. When we dial some of these numbers, the incoming call shows as it should (e.g. 01234 567890).
When we dial some of the other numbers, we get the 44 (e.g. 441234 567890)
I was hoping to be able to absorb the 44 and replace with a 0 but that didn't work out.
We've run a Wireshark trace and can see that on the incoming calls that display the incoming caller ID fine, the SIP header reads as:
From: <sip:01234567890@sip.provider;user=phone>;tag=xxxxxxxxxxxxxx
SIP from address: sip:01234567890@sip.provider;user=phone>
But on the calls that show the extra 44 information, the SIP header reads as:
From: "+441234567890"<sip:01234567890@sip.provider;user=phone>;tag=xxxxxxxxxxxxxx
SIP Display info: "+441234567890"
SIP from address: sip:01234567890@sip.provider;user=phone>
So, in essence, it's adding a 'SIP Display info' line to the header, then using the information contained within that to populate the 'From' header also.
So, is there a way to ignore the 'SIP Display Info' field and just use the number displayed in the "sip:01234567890@sip.provider" part of the header?
11
Mitel MiVoice Business/MCD/3300 / Re: Inward Dialing Modification Tutorial
« on: May 05, 2016, 08:41:49 AM »
Thank you for your help anyway, much appreciated.
12
Mitel MiVoice Business/MCD/3300 / Re: Inward Dialing Modification Tutorial
« on: May 05, 2016, 08:12:32 AM »
Thanks for your help, screenshots of the two forms attached. You will see we have 3 SIP peer profiles but I have applied the Inward Dialing Modification to each profile.
Incidentally, when a call comes in it displays '447777012345' but as soon as the handset is picked up, the display changes to '9012345'
It seems to strip the first 6 digits and insert a 9, this is something else that's been happening since the software upgrade.
Incidentally, when a call comes in it displays '447777012345' but as soon as the handset is picked up, the display changes to '9012345'
It seems to strip the first 6 digits and insert a 9, this is something else that's been happening since the software upgrade.
13
Mitel MiVoice Business/MCD/3300 / Re: Inward Dialing Modification Tutorial
« on: May 05, 2016, 06:30:51 AM »
Thanks x-man, but that doesn't seem to have made any difference either 
I now have:
Digits to Match: x
Digit Length Operator: Greater than or equal to
Digit Length: 12
Number of digits to absorb: 2
Digits to be inserted: 0
I left the '0' on 'Digits to be inserted' as I would like the '44' to be replaced with a '0'.
Incoming calls still display as '441234567890' instead of '01234567890'
I now have:
Digits to Match: x
Digit Length Operator: Greater than or equal to
Digit Length: 12
Number of digits to absorb: 2
Digits to be inserted: 0
I left the '0' on 'Digits to be inserted' as I would like the '44' to be replaced with a '0'.
Incoming calls still display as '441234567890' instead of '01234567890'
14
Mitel MiVoice Business/MCD/3300 / Re: Inward Dialing Modification Tutorial
« on: May 05, 2016, 05:30:07 AM »
OK, everything is set correctly and applied to the peer on 'Calling Party Inward Dialing Modification' but it doesn't seem to have any affect, calls still come in showing the '44' prefix.
Anything else I might have missed? Does it require a reboot to trigger the change? To confirm I have it set as:
Digits to Match: 44
Digit Length Operator: Greater than or equal to
Digit Length: 9
Number of digits to absorb: 2
Digits to be inserted: 0
Anything else I might have missed? Does it require a reboot to trigger the change? To confirm I have it set as:
Digits to Match: 44
Digit Length Operator: Greater than or equal to
Digit Length: 9
Number of digits to absorb: 2
Digits to be inserted: 0
15
Mitel MiVoice Business/MCD/3300 / Re: Inward Dialing Modification Tutorial
« on: May 05, 2016, 05:15:44 AM »
Thanks, yes I applied to the Peer, will try again with a different digit length.
Pages: [1] 2