Search results for query: *

Did you adminster the converse data return code on the feature access code page of the switch and in the conversant?

I would suggest x porting the station and adding the same port back. This way the station will clear any remaining info that had not download and would retry again. Station downloads do not always retry when busied and released. -TJ

ASA will connect to the LX. However, there are a few caveats about connecting via port 23 on the LX. The only login that can connect via the telnet port to the command line is vm. Therefore, vm is the only login that can only be used with ASA/Provision. The login sa is reserved only for the web...

Do you have the TAPI kernel-mode service provider installed in the Phone and Modem Options? Did it install the Avaya IP Service Provider, iClarity?

Another good site is: http://jaymzworld.yafd.net/pages/linux/pages/ntp.html

Is US NI Delayed Calling Name Update set to yes? If so, set it no. It is on the second page of the trunk group form. If it is set to yes, it will update the display on the set after the delayed name timer times out. If no name is sent, by the network, during the timer interval the trunk name...

On the second page of the station form is data restriction is on? If it is turn it off. Also, are these digital sets? -TJ

NTP can only be set by using configure server. The options under server date/time have to be set. The OS needs to know what timezone it is in otherwise it uses GMT. The log to check for NTP errors would be syslog. Normally the way to set up NTP is to set the NTP server address. Then set the...

Depends on what you want these companies share. Normally, tenant partitioning is used. The best source of info about using this if it will solve your problem is the Definity Administrators Guide book number 555-233-506. Here an example from the book... Tenant partitioning examples The...

Is data privacy turned on for the cos of the phone you are testing with? If so, turn it off.

If you have a tie trunk you can call a FAC. It's as simple as using the TAC plus the FAC. However the best solution is to take a vdn in the switch with the paging and have it dial the FAC. So you can tweak issues like adding pauses using wait time. For example Switch 1 w/Paging VDN x2303...

All of my comments are in bold. I assume all of your numbers come in over a different VDN. Assuming your vector is setup like this: VDN 2320 -2323 – transfer connect vdns VDN 2324 -2327 – non transfer connect vdns 1. Do something 2. Do something 3. route to number *89041234567 with cov n if...

I would guess that the incorrect digits are being passed. Try using the TAC code on the tie trunk to Node 4 in Node 1. Then enter an extension in Node 3. You should ring the extension in Node 3. If it works it means there is a problem with the number being sent out of Node 1. If it does not then...

In node 4 and 1 there should be two processor channels on each link. For example, in node 1 there should be a processor for DCS between itself, node 3 and node 4. Both processor channels, 9 and the other processor channel, should have the same node name since they are going to the same endpoint...

Customizing announcement sets - http://www.avayadocs.com/elmodocs2/intuity/r5_1_aug01/a_cstann.htm To see a list of all the annocement fragment use document 585-310-593 or 585-310-594 found here: http://support.avaya.com/edoc/docs/defaudix/585310593_2.pdf and here...

I check both the administrator's guide for R11 and feature description for G3V3. Neither state an interaction between a PCOL and the Call Park feature. As a matter of fact the G3V3 book says a PCOL line can be transferred to station without a button for that PCOL. Since a Call Park is basically...

In order to use Holiday routing you need to have the following: * The Definity release must be release 9.1 or greater * In the customer options form Vectoring (Basic) or Attendant Vectoring needs to be set to y * In the customer options form Vectoring (Holiday) needs to be set to y If all of...

Yes, using DCS/UDP. Basically to use DCS/UDP then you would go in the udp table and add a three digit prefix to the range in question, 28xx. Doing that adds the three digit prefix automatically to the 4 digit dialed number. In the aar analysis table add a line to match the three digit prefix...

In node 4, the error message that you are getting: "local node number not unique for DCS across dial plan, sig group, and processor channel forms" means that in either your signaling group, processor channel, or dial plan form something has the machine id 3. Which you do because node 3...

In node 1 as long as there is a dcs channel setup to goto machine id 1 and the link is up then you should be ok. The reason you are getting feature not assigned from the processor interface form is because you probably don't have a PI board. The processor interface form contains the link number...