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!

H323 & SIP extension passw set on TSE v3 1

Status
Not open for further replies.

GFDANNHAUSER

Programmer
Aug 14, 2006
46
ML
Good day
I am running a Aastra TSE v3
When I do the ipexi:dir=****,passw="XXXX"; it comes back with too many parameters entered, if I do not put passw, then it executes, why wont it allow passw?
Anyone had this issue before?
 
For an ALL_SECURE system the SECEXC parameter should be set to NO. Use the command IPEXI or IPEXC:
For example, IPEXI:DIR=12345,SECEXC=NO;

When a security exception is allowed the SECEXC parameter should be YES. Use the command IPEXI or IPEXC:
For example, IPEXI:DIR=12345,SECEXC=YES;

Note:
A RAC is mandatory when SECEXC = NO.

\Satellite1900
 
Thank you Satellite, I am using V.3, and it should have passw to restrict login, still gives too many parameters entered.
I will look at the license.
 
What version of version 3?
The PASSW parameter of IPEXI was dropped for version 3.2 and RAC used instead.

from the migration document in Alex for 3.2-
"3.2.7 Set IP Extension PIN Codes

In MX-ONE 3.1 and earlier versions, the password for the IP extensions was initiated in the IPEXI command. In MX-ONE Version 3.2 a PIN is used instead, which is the same as the Regional (Individual) Authorization Code (RAC). The reason for doing this change is to make it possible for the end-user to change his PIN.

The Regional Authorization Code is initiated by using the command auth_code_init. Set the parameter -code to a valid value and set -cil to the directory number, which is also set in -dir . RAC is limited to use only (1 to 7) digits."

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top