Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Extension mobility call routing issues on 7912 and 7940

We have a problem with Extension Mobility. When the user logs on the 7970 can make calls to translation pattern *0.[67]XXXXXXX on the partition "disable_calling" and calling search “TARIFADAS”. When the user logs on the 7912 or 7940 cannot make calls to this pattern .We have a translation pattern to hide the extension number from the user when calls to internal numbers. Within translation pattern, on the section "calling party transformations" on the fields "Calling Line ID Presentation" and "Calling Name Presentation*" is "restricted". On the Dna analysis output, the call flow is correct and the result is “Route this pattern”. I try too make a specific route *071956062 and work only on 7970.

Cisco Unified CM Administration

System version: 6.1.3.3190-1

SCENARIO:

Extension: 2198

Partition: "ramal"

CSS: "CSS_FL_FIELD_TPATTERN"

Called number: *071956062

CSS: "CSS_FL_FIELD_TPATTERN"

Partitions: "disable_calling"

TRANSLATION PATTERN:

Route: *0.[67]XXXXXXX

Description: local calls to mobile

Partition: disable_calling

Css: Tarifadas

Calling party transformations: "Calling Line ID Presentation" and "Calling Name Presentation*" is "restricted".

TRANSLATION PATTERN:

Route: 2XXX

Description: internal calls

Partition: disable_calling

Css: Tarifadas

Calling party transformations: "Calling Line ID Presentation" and "Calling Name Presentation*" is "restricted".

CSS TARIFADAS

Partitions: PRT_FL_LOCAL_CELULAR, RAMAL

ROUTE PATTERNS

Route: *0.[6-9]XXXXXXX

Partition: PRT_FL_LOCAL_CELULAR

Route group: Gateways h323

ROUTE PATTERNS

Route: *0.71956062

Partition: MOBILE

Route group: Gateways h323

OBSERVATIONS:

To even putting the partition “mobile” inside the css “private” as being to first option, the call is not completed. Example:

Extension: 2000

Partition: "ramal"

CSS: "CSS_FL_FIELD_TPATTERN"

Called number: *071956062

CSS PRIVATE

Partitions: option 1 "mobile"

option 2 "disable_calling"

I appended one file that explain better.

4 REPLIES
Hall of Fame Super Silver

Re: Extension mobility call routing issues on 7912 and 7940

Hello Eduardo,

have you created a user device profile for each phone model?

the line with the calling rights in what position is in the phone button template?

Hope to help

Giuseppe

Silver

Re: Extension mobility call routing issues on 7912 and 7940

As the user when logging on the 7970 is allowed to make the call then the combination of the Users CSS and the 7970 CSS are correct but when they log on to the other phones it fails. The issue must be with the other handsest CSS - check what Partitions are in the other handset`s CSS

New Member

Re: Extension mobility call routing issues on 7912 and 7940

Sorry, but What would be a handset? You want to say hardphone?

Both hardphone (7970, 7912) have the same css.

New Member

Re: Extension mobility call routing issues on 7912 and 7940

I removed to translation pattern *xxx and functioned correctly! Problem solved. BUT because functioned in the 7970 or IpCommunicator? In the partition disable_calling I had the following translation patterns: *xxxx 2xxx 3xxx 6xxx

Interesting it is that the callmanager is not going to choose the priority, what would be very helpful.

189
Views
0
Helpful
4
Replies
CreatePlease to create content