Cloud PBX functionality changed: "Call For" Another User Doesn't Show Their Caller ID to Callee

%3CLINGO-SUB%20id%3D%22lingo-sub-25573%22%20slang%3D%22en-US%22%3ECloud%20PBX%20functionality%20changed%3A%20%22Call%20For%22%20Another%20User%20Doesn't%20Show%20Their%20Caller%20ID%20to%20Callee%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-25573%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20a%20heads%20up%3A%20We've%20just%20noticed%20that%20Cloud%20PBX%20functionality%26nbsp%3Bhas%20changed%20so%20that%20when%20a%20delegate%20%22Calls%20For%22%20another%20user%2C%20their%20CallerID%20is%20presented%20to%20the%20remote%20party%20instead%20of%20the%20the%20user%20they%20are%20%22calling%20for%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20sure%20if%20this%20was%20designed%20or%20inadvertant%20(support%20didn't%20know)%3C%2FP%3E%3CP%3Eread%20more%3A%3CBR%20%2F%3E%3CA%20href%3D%22http%3A%2F%2Fwindowspbx.blogspot.com%2F2016%2F10%2Foffice-365-cloud-pbx-alert-cloud-pbx.html%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Fwindowspbx.blogspot.com%2F2016%2F10%2Foffice-365-cloud-pbx-alert-cloud-pbx.html%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-25573%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECloud%20PBX%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EVoice%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-50199%22%20slang%3D%22en-US%22%3ERe%3A%20Cloud%20PBX%20functionality%20changed%3A%20%22Call%20For%22%20Another%20User%20Doesn't%20Show%20Their%20Caller%20ID%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-50199%22%20slang%3D%22en-US%22%3E%3CP%3EMatt%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20know%20why%20they%20would%20have%20changed%20this%20feature%20as%20it%20seems%20to%20be%20backwards%3F%20If%20you%20call%20out%20on%20behalf%20of%20somebody%2C%20you%20want%20the%20caller%20ID%20of%20that%20other%20person%20and%20not%20yourself%2C%20otherwise%20you%20fail%20to%20act%20as%20a%20delagate.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tested%20this%20on%20a%20tenant%20this%20week%20and%20it%20is%20still%20working%20that%20way%2C%20and%20I've%20raised%20a%20call%20to%20ask%20why%20this%20is%20the%20case.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20issue%20is%20more%20key%20as%20the%20CLI%20manipulation%20cmdlets%20don't%20seem%20to%20be%20functional%20currently%2C%20or%20they%20are%20only%20in%20preview%20...%20I'm%20not%20quite%20sure.%20Again%20I%20have%20raised%20a%20case%20for%20this.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJed%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

Just a heads up: We've just noticed that Cloud PBX functionality has changed so that when a delegate "Calls For" another user, their CallerID is presented to the remote party instead of the the user they are "calling for".

 

Not sure if this was designed or inadvertant (support didn't know)

read more:
http://windowspbx.blogspot.com/2016/10/office-365-cloud-pbx-alert-cloud-pbx.html

1 Reply

Matt,

 

Do you know why they would have changed this feature as it seems to be backwards? If you call out on behalf of somebody, you want the caller ID of that other person and not yourself, otherwise you fail to act as a delagate.

 

I have tested this on a tenant this week and it is still working that way, and I've raised a call to ask why this is the case.

 

This issue is more key as the CLI manipulation cmdlets don't seem to be functional currently, or they are only in preview ... I'm not quite sure. Again I have raised a case for this.

 

Jed