cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2060
Views
5
Helpful
4
Replies

Caller ID on Call Forward All

JessePinkman
Level 1
Level 1

Hi,

one of our customers has a Call Forward All (CFA) set up on his Distribution Number (DN).

He is forwarding his calls to his mobile phone, which is working fine.

But the caller ID being displayed on his mobile phone always gets mixed up.

This does only happen on calls that are being diverted from his CUCM.

For example:
His DN is 123 and his mobile phone number is 0160123456789.

Now if he gets a call - that was diverted by CUCM -  from this number 0160987654321, he will either see:

+4900160987654321 or

+00049160987654321

as the caller ID.

I guess the country code is probably being added to the CLID by either our telephone provider or his mobile phone provider.
But what we would need is to get rid of the zeros.

The set up of our CUCM is pretty basic -> no Route Groups, Route Lists or Calling Transformation Patterns.

I've also attached a screenshot ouf our Gateway configuration.

Call Manager version: 6.1.2.1131-1

Phone: 7941

Gateway: Cisco 2821 v04

Thank you very much in advance for your help.

4 Replies 4

paolo bevilacqua
Hall of Fame
Hall of Fame

Wrong forum post in "IP telephony". You can move your post using the actions panel on the right.

I think this probably happens because telco receives "incorrect" TON (type of number) from CUCM and thus prefixes it with Country Code

By default TON is set to CallManager. It means that the previous TON would be used. If CUCM receives TON=NAT and forwards this number to PSTN it will use TON=NAT again due to Type of number = Cisco CallManager

You have to clarify the following:

1) What TON does you telco expect from you?

2) Configure corresponding Translation rules either on CUCM or on VG

br,

Vadym

Hi Vadym,

first of all thanks for your reply.

But I have been experiencing some trouble setting up the right Translation Pattern on CUCM.

I've set up the following Translation Pattern:

0.0![0-9#]

Discarding the PreDot, so it should discard any number that starts with two 0s.

But then the call will be displayed like this:

+1 609-876-5432

on the cell phone - which looks like the call is coming from an US DN.

And if I enter a 0 as a Prefix Digit under Called Party Transformations, I'm back to +490016...-thing

What am I doing wrong?

Please bear with me, I'm no CUCM expert

In the SDL logs I have found the following lines with the specific number:

---------

073129527| 2013/06/17 11:24:57.849| 001| SdlSig | SsCallInfoRes | processingCFA | Forwarding(1,100,164,52593) | ForwardManager(1,100,163,1) | (0,0,0,0).0-(*:10.40.17.5) | [R:NP - HP: 0, NP: 0, LP: 0, VLP: 0, LZP: 0 DBP: 0]Type=16777221 ssKey=52593 sideASsNode=1 sideASs=18764654 sideADsla=(0,18764654,85010442,27348) AHold=0 sideAPSS=0c296a50-7d92-26da-7247-3699683c0aab sideACMDevType=7 sideAEncodingType=10 sideAIsPreferAltScript=0 sideBNode=0 sideBSs=0 sideBDsla=(0,0,0,0) BHold=0 sideBPSS= sideBCMDevType=4 sideBEncodingType=0 sideBIsPreferAltScript=0 cgPart= cgPat= cgTags= cgValues= pretransCgp:tn=0npi=0nd=0015140669091pi=0si1 cgpn:tn=2npi=1nd=0015140669091pi=1si3 unModCgpn:tn=2npi=1nd=0015140669091pi=0si3 untransformedCgpn:tn=2npi=1nd=0015140669091pi=1si3 origCgpn:pi=0si1 FQCGPN:pi=0si1 cgNameInfo=locale: 3 Name: UnicodeName: pi: 0 cgLocName=locale: 1 Name: UnicodeName: pi: 0 cgpnMailbox= cgpnVMPN= cgpnVMPCss= cgCause=0 cgDevName=10.40.17.5 cgDevCepn= cgDevLocale=3 dialedNum:tn=2npi=1nd=290pi=0si1 cdPart=PT-Internal cdPat=290 cdTags= cdValues= pretransCdpn:tn=0npi=0nd=290pi=0si1 cdpn:tn=0npi=0nd=290pi=1si1 unModCdpn:tn=0npi=0nd=290pi=0si1 cdNameInfo=locale: 3 Name: pi: 0 cdLocName=locale: 1 Name: UnicodeName: pi: 0 cdpnVM= cdpnVMPN=444 cdpnVMPCss=0c296a50-7d92-26da-7247-3699683c0aab cdCause=0 cdDevName= cdDevCepn=772f84f4-aabc-39e8-9b6d-d195ff04ef18 cdDevLocale=3 oPart=PT-Internal oPat=290 oTags= oValues= oDialedNum:tn=2npi=1nd=290pi=0si1 oCdpn=tn=0npi=0nd=290pi=0si1 FQCDPN=tn=0npi=0nd=7296290pi=0si1 oCdpnVM= oCdpnVMPN=444 oCdpnVMPCss=0c296a50-7d92-26da-7247-3699683c0aab oCdpnRFR=0 oCdpnCause=0 LRPartition=PT-Internal LRPattern=290 LRWithTags= LRWithValues= LRNum=tn=0npi=0nd=290pi=0

---------

Thank you very much in advance.

ashok_boin
Level 5
Level 5

Hello,

We need to first rule out the segment in call flow where this caller id change is happening. At Cisco CUCM or VG or provider?

The easy and best way would be enable "debug h225 asn1" during non busy hours on VG, make test calls and see what's happening at VG logs. This will rule out both VG and provider possible changes to caller ID.

Ashok.

Sent from Cisco Technical Support iPhone App


With best regards...
Ashok
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: