[cisco-voip] change displayed number when dialing out?

[Evgeny Izetov]

Another option that might accomplish what you need is to use "Remote
Number" CSS on the phone page (or corresponding field in the device pool).
You'd need to set "Apply Transformations on Remote Number" Service
Parameter to True for this to work.

On Sep 2, 2016 12:48 PM, "Brian Meade" <bmeade90 at vt.edu> wrote:

> Looks like you can also do "no update caller-id" under voice service voip
> if this is just the connected number showing.
>
> On Fri, Sep 2, 2016 at 12:46 PM, Brian Meade <bmeade90 at vt.edu> wrote:
>
>> https://supportforums.cisco.com/discussion/11813771/function
>> -always-display-original-dialed-number-cube
>>
>> That's how to do it in CUBE but you can also just set "Always Display
>> Originally Dialed Number" in CUCM.
>>
>> On Fri, Sep 2, 2016 at 12:27 PM, NateCCIE <nateccie at gmail.com> wrote:
>>
>>> Does it just flash the long number, then update to the correct number?
>>> You cube should be sending a caller id update that shows the routed number.
>>>
>>>
>>>
>>> There are some bits to flip on updating that on CUBE, the you have to
>>> deal with PPI and PAI or what ever that stuff is.  But take this message as
>>> a glimmer of hope that you can make your users happy again.
>>>
>>>
>>>
>>> What is your config under voice service voip?
>>>
>>>
>>>
>>> -Nate
>>>
>>>
>>>
>>> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On
>>> Behalf Of *Nick Barnett
>>> *Sent:* Friday, September 02, 2016 10:19 AM
>>> *To:* Cisco VoIP Group <cisco-voip at puck.nether.net>
>>> *Subject:* [cisco-voip] change displayed number when dialing out?
>>>
>>>
>>>
>>> Long story short, I have to use steering digits to send calls to the
>>> correct CUBE and then select the proper SIP trunk to egress to PSTN.  This
>>> works well for our setup, but now the users occasionally complain that
>>> their phone is displaying "weird numbers."
>>>
>>>
>>>
>>> For instance, calling out of our corp office 800-555-1212, the user has
>>> to dial a 9 so they are used to seeing 918005551212.  Now they see
>>> 10010718005551212.
>>>
>>>
>>>
>>> My outbound dial peer on the cube matches those steering digits and then
>>> strips them to send to the PSTN. If I had a way of stripping the digits
>>> with the inbound dialpeer, the steering digits would likely be removed...
>>> but I can't think of a way to do that.
>>>
>>>
>>>
>>> I have 1 cluster, 2 CUBEs and each CUBE has 3 sip trunks from different
>>> carriers.
>>>
>>>
>>>
>>> Any ideas on how to "fix" this "problem" ?
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Nick
>>>
>>>
>>>
>>> To expand on the "long story short", nearly all of our business uses EM
>>> and they are located all over the country. We have a corp data center and a
>>> remote DC. Half of all phones register in each DC. Each DC has a CUBE and 3
>>> SIP trunks. I wanted to use standard local route groups and DPs to guide
>>> the outbound calls to the proper sip trunk, but EM profiles don't have
>>> device pools. This may not sound like an issue, but some of our offices
>>> have DIDs from multiple carriers. If I send calls from a Carrier1 DID out
>>> the Carrier2 SIP trunk, I have to pay alien TN charges. Despite all of
>>> this, the solution in place works except for this minor annoyance.
>>>
>>> _______________________________________________
>>> cisco-voip mailing list
>>> cisco-voip at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>
>>>
>>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160902/a17508a9/attachment.html>