Search results for query: *

Is there a PCN/PSN for firmware release 36? I'm not able to one. The release notes don't seem to indicate anything either. I tried deploying firmware 36 on some of my IPSI, and indeed it set the port negotiation back to auto. When I tried to set it back, it gave the error, "Disable auto...

Is there any interest in possible group discussions on IPSI technical info, Control Network routing, and issues and possible fixes? There is much buzz about various IPSI sanity issues, and it might be good to get some live discussion of other folks' woes and ails. Would any one be interested...

This is actually a very common problem...You a likely having IPSI sanity issues. IPSIs are EXTREMELY sensitive to network blips...even blips lasting less than one second! I have been working the same problem for months now. Avaya has told me that the problem is in my network, but I am still...

This sounds like your DOS filter is doing this. I have noticed that if the DOS filter is set to 0xFFFFFFFF, then pinging can produce these types of results. Typically, you will want to leave it alone. However, if you set the DOS filter to 0x00000000, then it should respond to all ICMP...

The problem has been resolved...Here's the scoop: Firstly, I was able to determine that not all transfers would fail...only transfers to a "sub-menu" would fail. Since this is PVM PC, it does not give the ability to add sub-menus. I accomplished this by using a phantom station (18) and...

...either port), and I get the message "Your party is unavailable. To transfer to another extension...". If I try to do a manual transfer using *8, it fails as well. However, a manual transfer works if there is only one port active. It seems like the system is having trouble transfering out...

AvayaEng I have a trunk group setup between my CM3, and an Asterisk box that I am labbing. On the CM side, it's setup as a basic h.323 ISDN trunk group similar to whatsanavaya's post above. You will need to make sure you use a compatible codec in you h323.conf (or oh323.conf) file...I ended...

Vamosalavaya Can you elaborate on you H.323 integration between Asterisk and Avaya? In particular, how have you configured you trunks on each side? I'm working on brining up an Asterisk box, and I would like to connect it to my existing Avaya Communication Manager switch via h.323. Any info...

Here's how I see it; Avaya makes a product, which has flaws (bugs) requiring service patches, etc. Now they are going to effectively charge the customer to get those?! It is simply irresponsible and questionable business ethics to market a product like that! I'm not a Microsoft fan, but at...

I think ipsisession is a 3.x and later command. You might try telnetenable -p <ip address of ipsi>. I believe that was the pre 3.0 command to accomplish this.

After reading my last post, I need to clarify my statement. Avaya is not going to (as far as I am aware) charge for the firmware, or access to the site. However, you will have to have a sold-to number in order to get firmware. It is also unclear if you will get access to all the firmwares, or...

You can also hook up a sniffer such as Ethereal to Ext1 or Ext2 and monitor the hosts. This will give you the IP addresses of the 8300, P300, MGP, and VOIP module.

Simply put, this is Avaya's way of protecting the bottom line of there business partners. Restrict the access to critically needed patches and software, and the customer will have to pay for it. This is also going to hurt the freelance consultants who are not officially a business partner, but...

...current IP address of the ipsi. 3. At the prompt type in ipsilogin, etc...and set the control interface, reset the card 4. Verify the new address by pinging from CM 5. Administer the ipserver interface **Have someone on site that can physically reset the IPSI just in case. Hope this helps!

Since you are on-site, this makes things a little easier: ***You will definately need access to Communication Manager to complete the switch*** 1. Busy-out the ipserver interface 2. change the ipserver interface to the new ip-address 3. via the services port, change the ip-address of the...

That is really going to south! They are hearding toward the same limited-access documentation at Nortel and Cisco!

Are you changing the subnet? If you are just changing the address, but keeping on the same subnet, then this is not too complicated.

From my testing, I found that during a translation save to an ESS, the main server sends the following files: group.sat (group permission data) passwd.sat (password file for administered users) xln1_dif.txt.gz (tarball'd translation file...this probably isn't all the trans, just ones changed...

You will need to add IPSIs in you remote PNs in order to be eligible for ESS take-over. Are these sites connected via DS1-C? Do you have a CSS at your main site? The reason I ask is that during an outage, an ESS server cannot takeover a CSS switch-node carrier...probably because the SNC can't...

Thanks Dunstan, you get a star! I was afraid that they might say that...with that said, it's my hope to see the ESS product evolve to allow uninterrupted failover/interchange, and load-sharing between servers (ESS and main). Give them a few years, and that product will probably evolve to that...