Tuesday, January 24, 2012 8:12 AM
Just discovered a weird issue bug which i discovered today with simultaneous rings/ Team Call settings, as we have a requirement for a large team call group of 16 Users when users are called internally using Lync and the call rolls to the team group anyone on that team call group is unable to answer that call and when answering you get a "Call is not successful error message" and "the caller will get a network issues are preventing the call message" in the client
I discovered that you can have up to 9 team members before where the internal call works fine but after that number and you have more than 10 team members i get the mentioned error
All External Calls work fine with this Team Call Group Settings and users can answer as per normal when the call rolls to them
Im guessing there may be some sort of bandwidth limitation with the internal Lync call if anyone has any ideas on this would love to hear some workaround as you can imagine getting alot user complaining as they think that external callers are affected which of course they are not but try change a users mind about that :)
Below is a trace i ran which shows the error the as being The call was cancelled by the caller before the remote party answered" this appears for every person who is in the team call group
Via: SIP/2.0/TLS 10.8.16.10:5061;branch=z9hG4bK4C9CDF84.25C2D438EE8AC331;branched=TRUE;ms-internal-info="absapZQ1gIqcWa6_okkkcJdtgCaMl_fAGnIG7hqSgFJtM41MIlXLt1UgAA"
Via: SIP/2.0/TLS 10.8.16.10:49607;branch=z9hG4bK91A44363.140DBC10EE83F330;branched=TRUE;ms-received-port=49607;ms-received-cid=617900
Via: SIP/2.0/TLS 10.17.64.111:59584;branch=z9hG4bKED4A7D64.86800A8DCAE1332B;branched=FALSE;ms-received-port=59584;ms-received-cid=5FC800
Via: SIP/2.0/TLS 10.8.16.207:50055;ms-received-port=50055;ms-received-cid=6E9C00
User-Agent: CPE/4.0.7577.4047 OCPhone/4.0.7577.4047 (Microsoft Lync 2010 Phone Edition)
Ms-client-diagnostics: 52092;reason="The call was cancelled by the caller before the remote party answered"
Proxy-Authorization: TLS-DSK qop="auth", realm="SIP Communications Service", opaque="14BCB837", targetname="SYDLYNCSBS01.$$$$.internal", crand="4fe6186f", cnum="819", response="536fc29f6d5d133b09ffd69191f9b4d43e0687c2"
- Edited by maz124ss Tuesday, January 24, 2012 8:14 AM
Wednesday, February 01, 2012 12:54 PMModerator
If the parameter AllowCallForwarding is set to True, users assigned to this policy can forward calls. If this parameter is set to False, calls cannot be forwarded.
Please confirm you’ve set the voice policy correctly. And make sure assign the voice policy by the cmdlet Grant-CsVoicePolicy. Hope helps.
TechNet Community Support
Wednesday, February 01, 2012 9:31 PM
This Forward function works fine if the Team Call Group is set to 9 or less people after that number is when calls fails, having said the call only fails when it is an internal Lync Call, PSTN calls work fine
I have a PSS call open with MS and has been escalated several times so i have feeling this issue is more serious than just a setting in more Lync Voice Policy
Saturday, February 04, 2012 6:27 AMModerator
Sunday, February 05, 2012 6:32 AM
PSS have confirmed this in fact a limitation in the source code which for internal calls they are limited to 20 Extensions (In our envitonment evry user uses the client and Lync Phone so 2 channels each)
I was advised to use a response group but this is in no way pratical for us as in a Broking environment every user has a DID and other users need the ability to pick these calls if not answered
This brings me to huge problem i have with Lync as in our envirmoment Line Appearences was a common feature in our old PBX and with that not being available in Lync, Team Call has to be used and this cause me the most grief with users, especially when these Team Call limitations exist
Which brings me to the questions will Lync ever offer the Line Appearence Function like other vendors including Cisco?
Wednesday, May 16, 2012 5:15 PM
Yes, using snom UC Edition "apollo" beta has this type of feature. take a look:
+Say thanks and observe basic forum courtesy:
+If this post answered your question, Mark As Answer
+If this post was helpful, Vote as Helpful
windowspbx blog: my thots/howtos
see/submit Lync suggestions here: simple and public
- Proposed As Answer by Matt LandisMVP Friday, March 08, 2013 7:23 PM
Thursday, May 24, 2012 4:35 AM
As soon as i saw your reply i ordered the Snom 821 and the Apollo firmware and what do u know all the line appearances function as intended
First impressions is the Snom does not have the seamless ease of the Windows Phone Edition devices but on the other hand as they are not locked down so many more functions are possible
As i am very impressed and some of the most annoying complaints i have about the Windows Phone Edition such are now fixed by the Snom including
- Lack of line appearances
- Delay in answering Response Group
- Delay when transferring a call
- Hold Music on Phone
- Disable Call Waiting Beep
So very impressed by this but after having deployed 700+ Polycom CX600 to all our sites i am stuck now, i hope Microsoft release an upgrade Windows Phone edition for Wave 15, why a third party vendor can get their act together and resolve all these issues and MS cant make me wonder