CME- How can i make outgoing PSTN calls only with a key like FAC (in cucm)

Answered Question
Jan 14th, 2009

I would like to know if it is possible to assign something like FAC (Forced Authorization Code in CUCM) for each user in a call manager express enviroment to make outgoing PSTN calls. if the user does not have a key, he cannot make outgoing PSTN calls.

I have this problem too.
0 votes
Correct Answer by filiberto.aguirre about 5 years 3 months ago

hola manuel,

no te funciona porque primero necesitas que el CME verifique la marcación,una vez validada el CME lo manda por el puerto analógico. en el ejemplo que te envié aparecen 2 dial-peer , el primero es un voip que es el usa el CME para recebir los datos del PIN, el otro dial-peer es un pots.

haz la anologia con el ejemplo que te dí pero ahora, la diferencia es que yo te envie uno con un controllador e1 y tu usas una troncal analogica.

saludos

  • 1
  • 2
  • 3
  • 4
  • 5
Average Rating: 0 (2 ratings)
Paolo Bevilacqua Thu, 01/15/2009 - 03:58

The simpler way is "afterhours and pin override" - check CME documentation. All other methods involves TCL scripts, that is a bit more complicated.

Hope this helps, please rate post if it does!

Nicholas Matthews Thu, 01/15/2009 - 05:46

Hi Manuel,

Forced Access Codes (FAC) is not currently a supported feature. This feature is in the roadmap for CME, but it does not have any current support. This isn't to be confused with Feature Access Codes (FAC), which is a different FAC :)

Here's a link from the CME support wiki that outlines the steps and guides, as well as provides the script:

http://supportwiki.cisco.com/ViewWiki/index.php/SBCS:Call_Handling_-_Cisco_Unified_Communications_500_Series_-_Cisco_Smart_Business_Communication_Systems#Can_UC500.2FCME_be_configured_to_prompt_a_caller_for_a_PIN_before_placing_a_call.3F

hth,

nick

filiberto.aguirre Thu, 01/15/2009 - 13:39

Hi manuel,

some months ago I found this info in tis forum,is aplied to UC500 buy I set in my CME 7.0 , it works but sometimes the PIN is not asked, I don't know why, maybe is a bug

1) IP Phone user dials a particular pattern (international destination, for example)

2) If this destination is enabled for FAC, the user will hear a voice prompt asking for an Account number and PIN

3) The user enters the Account/PIN pair. If valid, the call proceeds, if not the call is dropped.

Configuration Steps

1) Obtain the application package from our FTP location. The package contains two audio files that need to be moved to the UC500 flash:

Simple-FAC-SBCS.zip

2) Copy the individual audio files to the UC500, using TFTP for example.

3) Enter the following commands in configuration mode, to load and activate the script (in this example the Account and PIN are three digits long):

application

service clid_authen_collect

param uid-len 3

param pin-len 3

4) Create usernames for authentication. Notice that the username/password will represent the Account and PIN that the caller will have to dial to be successfully authenticated. You can create multiple usernames and then hand those out to select personnel that will be allowed to place premium calls. In this example both Account and PIN are three digits long. The system supports a maximum of 16 digits for codes:

aaa new-model

aaa authentication login h323 local

aaa authorization exec h323 local

aaa authorization network h323 local

username 123 password 123

username 321 password 321

5) Create a dial-peer for each pattern that you want cover using this application. Start with index 2500. In this example, only one dial-peer is shown with 9011.T as the pattern, which is the International prefix in the US. Notice that the pattern is preceded by an access code (9) that could vary per implementation:

dial-peer voice 1000 voip

description cell nal PIN

service clid_authen_collect

destination-pattern 9045..........

session target ipv4:x.x.x.x ---------------> CME IP

incoming called-number 9045..........

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

!

dial-peer voice 1001 pots

corlist outgoing LADA-cell

description cell Nal PIN

destination-pattern 9045..........

port 0/2/0:1

prefix 045

Limitations and Considerations

- This feature does not support any reporting or CDR insertion, which means that Call Detail Records won't display the account number used to place the call.

- If the authentication fails after three retries, the call drops without notification.

- Some features, such as transfer, call forward, etc. may not work.

manuel.giraldo Fri, 01/16/2009 - 10:18

Hi filiberto:

First of all, thanks a millions for your e-mail. I want to explain what i did after your advice.

1. I uploaded the two files which are enter_account.au and enter_pin.au to the flash memory.

2. I entered the following commands in the configuration mode:

application

service clid_authen_collect

param uid-len 6

param pin-len 6

3. I created the user: (configuration mode)

username 123456 password 123456

4.- I configured the following dial peer:

dial-peer voice 1 pots

corlist outgoing Servicios

description Conexion a PBX

service clid_authen_collect

destination-pattern 9... >>> ext with 3 dig

port 1/0/0

voice-port 1/0/0

description Conexion a PBX

station-id name PBX

Note:This port connects the CME to a PBX. port 1/0/0 is FXS.

dial-peer cor custom

name servicios

dial-peer cor list Servicios

member servicios

ephone-dn 1 dual-line

call-waiting ring

number 207

description Engineering

name Manuel Giraldo

corlist incoming Servicios

ephone 1

description Manuel Giraldo

video

mac-address 001E.4A5F.ED5C

paging-dn 6

type 7911

button 1:1

After those steps, i made a test call but the cme never asks me the key. Calls progress without problem.

Are there anything else i have fogetten?

By the way, maybe you are latinoamerican, if it is so, could you write in spanish?

Thanks in advanced.

Correct Answer
filiberto.aguirre Fri, 01/16/2009 - 13:46

hola manuel,

no te funciona porque primero necesitas que el CME verifique la marcación,una vez validada el CME lo manda por el puerto analógico. en el ejemplo que te envié aparecen 2 dial-peer , el primero es un voip que es el usa el CME para recebir los datos del PIN, el otro dial-peer es un pots.

haz la anologia con el ejemplo que te dí pero ahora, la diferencia es que yo te envie uno con un controllador e1 y tu usas una troncal analogica.

saludos

manuel.giraldo Fri, 01/16/2009 - 16:11

Estimado Filiberto:

Acabo de configurar los 2 dial peer y funcionó tal como indicaste. Cuando marco 9107, el cme busca un dial-peer y por jerarquia u orden ya establecido busca los incoming called number de estos(inbound dial peer), despues del match busca los destinattion pattern de los dial peer(outbound dial peer), y es por ellos que si funciona.

Nuevamente Muchisimas gracias Filiberto.

filiberto.aguirre Fri, 01/16/2009 - 17:19

Excelente Manuel,

yo tengo la version de CME 7.0 y en ocasiones no me pide el pin, si tienes una version diferente y te pide siempre el PIN que es como debe de ser me avisas.

yo tengo la 2800nm-adventerprisek9-mz.124-20.T.bin

saludos!

manuel.giraldo Fri, 01/16/2009 - 19:42

Filiberto,

Yo tengo el CME 4.0, También tengo el detallito de que a veces no pide la clave. Probaré con otros ios para ver si el prob persiste. Ahora me falta ver la integración entre el Microsoft Office Communicator y el CME, segun comentarios indican que se debe hacer un sip trunk pero debo leer porque del tema no se mucho, si tienes alguna info que me pudiera servir, te agradeceria mucho enviarmela. Quise preguntarle ese tema a tony pero encontre cerrado el foro.

Asimismo tengo por tarea configurar una conferencia pero con más de 3 usuarios dentro de ella. Esos 2 temas debo resolverlos, si te has cruzado ya con alguno de éste, please help me!!

Gracias de Antemano,

Manuel

andresfmg Wed, 03/23/2011 - 17:25

amigos, eso se resuelve colocandole preference 0 al dial-peer voip y preference 1

al dial-peer pots

saludos!!

filiberto.aguirre Tue, 05/22/2012 - 06:03

Hi,

CME 8.6 and later support FAC feature.

For previous version I found in this forum a solution that I have modified based on recommendations I received (check all the post). You can try if you wish.

Last modification I have to do was the preference option in dial peer (thanks to andresfmq for this tip).

dial-peer voice 50 voip
description Cellular Calls
service clid_authen_collect
destination-pattern 9044..........
session target ipv4:10.10.10.1
incoming called-number 9044..........
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 51 pots
PREDERENCE 1
description Cellular Calls
corlist outgoing  Cell
destination-pattern 9044..........
port 0/1/0:0
prefix 044

dial-peer voice 52 voip
description Cellular LD
service clid_authen_collect
destination-pattern 9045..........
session target ipv4:10.10.10.1
incoming called-number 9045..........
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad
!
dial-peer voice 53 pots
PREFERENCE 1
description Cellular LD
corlist outgoing LADA-cell
destination-pattern 9045..........
port 0/1/0:0
prefix 045

Seifeddine-Tlili Tue, 05/22/2012 - 09:39

Hi Filiberto

Thanks for the TIP, i`ve actually thought of it but i was afraid that it will cause a loop (looping on the same dialpeer)

The issue that i had was a weird random round robin between my pots dialpeer and voip dialpeer and what doesn`t make sense that in my voip dialpeer i have the incoming called number which should be the ASSET to have the voip dialpeer selected first

i`ll do a test with my customer and let you know

Thanks mate

Actions

Login or Register to take actions

This Discussion

Posted January 14, 2009 at 7:13 PM
Stats:
Replies:14 Avg. Rating:
Views:1172 Votes:0
Shares:0
Tags: No tags.

Discussions Leaderboard