Answered by:
Call Loop on Lync in case of unallocated number

Question
-
hi,
I saw that lync 2013 make a Loop when it receive a call from PSTN (with the right format E164) toward a number not yet associated to a Lync User. Lync send back the call to the PSTN Gateway which generate a Loop.
I know that there is a Unassigned number feature but with the large range of number managed by lync in my network i cannot manage every day to change the range of number not yet assigned. Sometime i have only 5 or 10 numbers really associated to Lync users over a range of number of 100 possible numbers. I should find a way when the call is received from PSTN Gateway to release the call if the called is not a user lync .
Any solution ?
Tuesday, September 1, 2015 6:44 PM
Answers
-
Lync shouldn't make a call loop by default. Do you have PSTN usages assigned to your trunk? If so, that may very well be the issue.
To check, in the Control Panel, go to Voice Routing -> Trunk Configuration and see if you have PSTN usages assigned. If you have them in there, but you're not intentionally trying to loop calls back out (perhaps to another PBX), you can remove them and test again.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.- Proposed as answer by Eason Huang Wednesday, September 2, 2015 2:12 AM
- Marked as answer by Eason Huang Wednesday, September 23, 2015 8:29 AM
Tuesday, September 1, 2015 7:50 PM -
Hi,
Agree with Anthony Caragol.
On Lync Server Control Panel--Voice Routing--Trunk Configuration, when you want to achieve the function of inter-trunk routing, then you need to associate and configure PSTN usage records to the special trunk configuration.
So you can try to disable this option if you have enabled it before, and then have a test.
You can refer to the link below:
https://technet.microsoft.com/en-us/library/Gg398792(v=ocs.15).aspx
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Eason Huang
TechNet Community Support- Marked as answer by Eason Huang Wednesday, September 23, 2015 8:29 AM
Wednesday, September 2, 2015 2:15 AM
All replies
-
Lync shouldn't make a call loop by default. Do you have PSTN usages assigned to your trunk? If so, that may very well be the issue.
To check, in the Control Panel, go to Voice Routing -> Trunk Configuration and see if you have PSTN usages assigned. If you have them in there, but you're not intentionally trying to loop calls back out (perhaps to another PBX), you can remove them and test again.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer". SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.- Proposed as answer by Eason Huang Wednesday, September 2, 2015 2:12 AM
- Marked as answer by Eason Huang Wednesday, September 23, 2015 8:29 AM
Tuesday, September 1, 2015 7:50 PM -
Hi,
Agree with Anthony Caragol.
On Lync Server Control Panel--Voice Routing--Trunk Configuration, when you want to achieve the function of inter-trunk routing, then you need to associate and configure PSTN usage records to the special trunk configuration.
So you can try to disable this option if you have enabled it before, and then have a test.
You can refer to the link below:
https://technet.microsoft.com/en-us/library/Gg398792(v=ocs.15).aspx
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.
Eason Huang
TechNet Community Support- Marked as answer by Eason Huang Wednesday, September 23, 2015 8:29 AM
Wednesday, September 2, 2015 2:15 AM