Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

VMPRo and use of $CLI_NAME variable 1

Status
Not open for further replies.

hibroth

Technical User
Oct 27, 2005
825
IT
Is there a way to capture the caller name (stored in the system directory) and pass it somewhere? (CP registers)

I tried both with the $NAM and $CLI_NAM but no result, VMpro R9 SP5.

Thank you
 
May I ask for what the purpose?

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

2cnvimggcac8ua2fg.jpg
 
Of course yes, Gunnaro, the purpose is to send the caller name (present in the system directory) to the end user email.
No problem about the $CLI option, the caller number is correctly shown, but the user needs the caller name
 
You need a separate d-base for it VMpro cannot do it for you.


Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
Yes, Bas, this is what I supposed but now I wonder that $CLI_NAME is made for
 
That is for 9.1

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool )
______________________________________
 
Bas is right, it's for R9.1, but it's visible in R9.0 as well. (Not working).
A DB lookup is your only option for the next 5 days:)

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

2cnvimggcac8ua2fg.jpg
 
I have the feeling I will wait the 22nd....

thank you all
 
Did you solve this issue ?
I was trying to use $CLI_NAME in WMPRO but I don't get what I expected ...
 
What do you get then, and what did you expect?

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

2cnvimggcac8ua2fg.jpg
 
I get "XXXX_Name" where XXXX is extension of my user instead of having the real name of the user.
 
Are you making an internal call to the module?

How does it look on an incoming external call that has it's CLI in the Directory, although as described in the manual it shouldn't include the CLI

$CLI_NAME
The name, if available, of the caller.

"Trying is the first step to failure..." - Homer
 
I don't try with external call but in my case I need to get the internal name of the user who was the original called party.

I've created a VMPRO Module that forward calls to a specific user and I want to add a description to the call with the name of the internal user who was the original called party.
 
Remember that "Full Name" is not a mandatory field in Manager, so it will only look at "Name"

For internal calls $NAM is your best choice.

For the forwarding, you can use a Transfer-action:
- Source of Transfer: (test the available choices, like $NAM, $TARGET, etc)
- Description: "Call forwarded from $TARGET" (or other variables)

Kind regards

Gunnar
______________________________________
Mille viae ducunt homines per saecula Romam

2cnvimggcac8ua2fg.jpg
 
What are you trying to achive?
Are you doing a blind transfer and therefore you wanna see the transfering internal user?
If you do a supervised tranfser the internal user is showed on the phone with the CLI of the caller.

"Trying is the first step to failure..." - Homer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top