[cisco-voip] Caller ID Manipulation

Tue Jan 17 12:56:16 EST 2017

It still works with SIP. It is controlled by the "Transmit UTF-8 for
Calling Party Name" checkbox on a SIP trunk. When unchecked (default),
ASCII Display Name gets sent. If you check it, then Display Name is sent.
If ASCII Display Name is blank, then I believe just the number is going to
be sent out.

On Tue, Jan 17, 2017 at 12:44 PM, Norton, Mike <mikenorton at pwsd76.ab.ca>
wrote:

> Oh yes, that is a good trick I used to use back when my PRI gateways were
> MGCP. Does it work with SIP too? I guess I just always assumed SIP would
> take Unicode names.
>
> Not actually using CUCM any longer, which is why I do the names on the
> gateway now and forgot about the ASCII Name trick.
>
> -mn
> ------------------------------
> From: Evgeny Izetov
> Sent: 17/01/2017 10:31 AM
> To: Norton, Mike
> Cc: Alan Libbee; Cisco VoIP Group; Ben Amick
>
> Subject: Re: [cisco-voip] Caller ID Manipulation
>
> You could also look into changing the ASCII Display Name on line
> appearances as that's what gets sent to trunks by default.
>
> On Jan 17, 2017 12:18 PM, "Norton, Mike" <mikenorton at pwsd76.ab.ca> wrote:
>
> Alan, I think the CNAM database lookup is only U.S. thing. In Canada and
> presumably elsewhere, the calling name is set by the caller (if ISDN or
> SIP, otherwise by their CO switch if analog POTS) and is passed all the way
> through the PSTN to the callee.
>
>
>
> I’ve never understood why the CUCM web interface calls the field “internal
> caller ID” because there is nothing internal about it. The PSTN in some
> countries, such as U.S.A., ignores it, but that shouldn’t be a license for
> Cisco to misname the field, leading to people getting surprised when they
> discover that the name is not kept internal.
>
>
>
> Likewise, there is nothing about Ben’s SIP provider that I would agree is
> “very lax.” To me, it sounds very perfectly normal, because that is the way
> the PSTN works for me.
>
>
>
> On my PRI gateways, I modify the outgoing names by using an inbound SIP
> profile on the incoming SIP dial-peer. This allows me to alter the name in
> SIP From field based on what number is in the From field. So I can put a
> generic name for certain number ranges, special names for specific numbers,
> no change for incoming PSTN calls that are forwarded back out to the PSTN,
> etc. I think you should be able to do the same on a CUBE. Here’s some
> snippets of it as an example:
>
>
>
> request ANY sip-header From modify "^(.+):.*(<sip:\+17808643696
> <(780)%20864-3696>@)" "\1: \"SPRT RVR REG AC\" \2"
>
> request ANY sip-header From modify "^(.+):.*(<sip:\+17805682265
> <(780)%20568-2265>@)" "\1: \"TP CREEK SCHOOL\" \2"
>
> request ANY sip-header From modify "^(.+):.*(<sip:\+17807662294
> <(780)%20766-2294>@)" "\1: \"WMBLY ELEM SCHL\" \2"
>
> request ANY sip-header From modify "^(.+):.*(<sip:\+17805328133
> <(780)%20532-8133>@)" "\1: \"PWSD76\" \2"
>
> request ANY sip-header From modify "^(.+):.*(<sip:\+178035752[01][0-9]@)"
> "\1: \"PWSD76\" \2"
>
> request ANY sip-header From modify "^(.+):.*(<sip:\+1780357522[0-4]@)"
> "\1: \"PWSD76\" \2"
>
> request ANY sip-header From modify "^(.+):.*(<sip:\+178083130[5-9][0-9]@)"
> "\1: \"PWSD76\" \2"
>
> request ANY sip-header From modify "^(.+):.*(<sip:\+17808643741
> <(780)%20864-3741>@)" "\1: \"PWSD76\" \2"
>
>
>
> Note that inbound SIP profiles has to be turned on under “voice service
> voip” in order to work. But I guess you could probably do it on the
> outgoing dial-peer to your SIP provider if you wanted. (I have to do it on
> incoming because my outgoing is PRI.)
>
>
>
> -mn
>
>
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Alan Libbee
> *Sent:* Tuesday, January 17, 2017 8:02 AM
> *To:* Ben Amick <bamick at humanarc.com>
> *Cc:* Cisco VOIP <cisco-voip at puck.nether.net>
> *Subject:* Re: [cisco-voip] Caller ID Manipulation
>
>
>
> Ben,
>
>
>
> You can set calling name on the device or trunk level. Most landlines and
> businesses not using SIP will only receive the calling number, the name is
> looked up through the cnam database. You can query the cnam database here:
> https://www.opencnam.com. The cnam database should be updated to reflect
> your business name, I recommend spot checking your DIDs to see what is
> displayed in cnam. I have access to some different sip carriers if you want
> to do some testing, send me a direct email and I can tell you exactly what
> we are receiving for your calls.
>
>
>
> -Alan
>
>
>
> On Jan 17, 2017 9:41 AM, "Ben Amick" <bamick at humanarc.com> wrote:
>
> So, I’ve discovered we have a very lax SIP provider who passes through all
> our ID signaling from our CUCM to the WAN without any modification – which
> while great for our external CID# mask, means that our internal caller ID
> names (Such as “HR Conference Room” and “John Smith”) are being published
> out as our Caller ID names to any residential or other commercial callers
> (or anyone who has a cell phone with a caller ID app? Haven’t tested that
> as I don’t have access to one). I can change this myself, but it would
> require me to get rid of all our labeling and have everyone have generic
> internal CID, which is not preferable.
>
>
>
> I’ve about to be on the verge of telling our SIP provider to change this
> to force to our company name across the board, but I was wondering if there
> was any way I could elect to enforce this on our CID myself, either on UCM
> or on our CUBE routers for all outbound calls. Globally would be fine, but
> optionally would be great if I could opt-out certain people that do our
> marketing and sales.
>
>
>
> *Ben Amick*
>
> Telecom Analyst
>
>
>
>
>
>
> Confidentiality Note: This message is intended for use only by the
> individual or entity to which it is addressed and may contain information
> that is privileged, confidential, and exempt from disclosure under
> applicable law. If the reader of this message is not the intended recipient
> or the employee or agent responsible for delivering the message to the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this communication is strictly prohibited. If
> you have received this communication in error, please contact the sender
> immediately and destroy the material in its entirety, whether electronic or
> hard copy. Thank you
> _______________________________________________
> 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/20170117/60fe90d8/attachment.html>