Supporting Busy on Busy with Skype for Business
This should be just used as basic approach on how you can support busy on busy.
First you can check if the new APPLICATION was installed correctly:
The newly created appliance will be loaded during the Frontend server startup procedure and you will be able seeing a not in Event 30253, indicating the application was included in the loading process.
Here you will find a pre-defined set towards busy on busy.
Generally busy on busy messages look like this example below:
Via: SIP/2.0/TLS 192.168.0.13:49887;received=18.104.22.168;ms-received-port=41538;ms-received-cid=9F6B100
CSeq: 1 INVITE
1034;reason="Previous hop federated peer did not report diagnostic information";
Good luck troubleshooting....
Author: Thomas Poett MVP, Business Unit Lead Microsoft Unified Communication
Post a Comment