12-29-2016 03:12 AM - edited 03-15-2019 05:37 AM
Hello,
We have setup native call queue in CUCM 11.0 and its working fine. Only problem is when Agents make outbound call (PSTN), there caller ID is displaying the PRI's main number 17981000.
Our HuntPilot is 1234 (It is part of our PRI DID range).
Agent's extensions are 8001, 8002, 8003 (these extensions are out off of PRI DID range).
How can we setup system to appear outbound caller ID as 1234 for internal calls (within CUCM) & 17981234 for outbound call ( to Mobile network/PSTN) ?
Regards
Solved! Go to Solution.
01-04-2017 07:44 AM
For internal calls, you could utilize the "Caller ID for Calls from This Phone" field on the device page. You'd have to configure a Calling Party Transformation Pattern that masks 800X with 1234.
12-29-2016 09:19 AM
Simply adjust at the RP/RL calling party number as required, if you don't want this for all phones, you might need to create a new RP to change this.
12-30-2016 07:12 AM
Thank Jaime,
RP/RL will reflect calling party number for PSTN calls, what about internal calls (within CUCM ext to ext) ?
12-30-2016 10:02 AM
Unless you change something to change the call routing internally, those are direct calls and you'll see the DN they have configured. Have you tried this?
12-31-2016 12:36 AM
No, I haven't tried yet. We are on new year holidays, will be working from Monday 2 Jan 2017. I will try and update.
Thanks
Happy New Year
12-30-2016 03:46 PM
Hi,
Please let me know if I understand this correctly.
you want agent's extension to be displayed as 1234 for internal calls and 17981234 for external calls.
How about doing the following configuration on Agent's Extension(8001)
on Route patterns taking the call out to PSTN you will have to check the box against
Use Calling Party's External Phone Number Mask
if you check that, it will use the 17981234 and display that as the caller id on PSTN and
on internal calls 1234 go as the caller id.
Let me know if that works for you.
Please rate and mark correct if helpful
Regards,
Adarsh Chauhan
12-31-2016 12:38 AM
Yes Adarsh, exactly the same I was looking for.
We are on New Year Holidays, will work from 2 Jan 2017. I will try your suggestion and will update here.
Thank
Happy New Year
01-01-2017 11:16 PM
01-03-2017 10:49 PM
Hi,
I tired a couple of things but couldn't take it away. I am not sure if we can take that away.
Would that not work for you?
Please rate and mark if helpful
Regards,
Adarsh Chauhan
01-04-2017 07:44 AM
For internal calls, you could utilize the "Caller ID for Calls from This Phone" field on the device page. You'd have to configure a Calling Party Transformation Pattern that masks 800X with 1234.
01-10-2017 10:13 PM
Hello,
I got this working via Translation Pattern.
Now I want to block incoming calls to agents ext 800X. Call to 1234 (Main number) should work which is working but calls to agent ext 800X is also working which should be blocked.
I tried with calling search space and partition but its blocking call to 1234 as well.
How can I restrict calling to 800X only NOT 1234 ?
Regards
01-11-2017 07:34 PM
You could create a new partition and not add it to any CSS. Then change the partition of 800X directory numbers to the new partition while leaving the Hunt Pilot 1234 partition as is.
The hunt pilot will still be dialable but nothing will be able to dial the 800X numbers directly.
01-07-2017 06:54 AM
Hello,
Calling Party Transformation Pattern made it work as required.
Thank you all for time and response.
Regard
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide