Search results for query: *

I don't see the full 0123456789@xxx.xxx.xxx.xxx in the display I am on the latest 4.1 build, I do get the 10 digits only but my problem is with how it is represented internally and sent out when send CID of incoming call is checked in the twinning tab. Calls coming in via analog are twinned...

When i get an incoming call on a SIP trunk the outgoing twinning call isn't passing the CID corectly. I get a garbled CID, now it works ok on an incoming analog call. When looking at monitor traces I think the problem lies in the fact that the IP address is appended to the phone number so when...

I too had all kinds of problems with getting the SIP Line to register, until I check the Run STUN on Restart for the Lan network configuration. It would have been nice if Avaya had put that in the documentation somewhere!

I do have the gatekeeper enabled on lan2 where the connection comes in from the H.323 provider. The connection is made fine and the call will stay up with good voice both directions for as long as we are connected, until it is put on hold. After being on hold the call disconnects after about...

It is a VOIP h.323 trunk to outside POTs lines and incoming calls. Not to another Ip Office.

I am seeing my H.323 Trunk calls being dropped after about 1-2 minutes when picked up from being put on hold on an 4621sw handset. This also happens on a 5410 Handset so it must be something with the protocol. The Monitor trace that happens when it drops is: note: dst and source addresses...

I've been having this issue as many but discovered just recently if the call is incoming on the H.323 line you can hear DTMF on the calling side, so outside. But if you call back from IP Office to same number no DTMF is heard. Odd very odd, hopefully the Maint Rel will solve this issue.

I have been having trouble with a 406V2 and 4.0.5 sending DTMF over a H.323 trunk. Same kind of issue as above. See the following post: http://www.tek-tips.com/viewthread.cfm?qid=1351426&page=1

So everyone that has upgraded to 4.0 and is using Gen local tones over an IP line is getting DTMF out the other end?

When we try to transmit DTMF tones from and IP 4621sw over and IP H.323 line we aren't getting any tones generated. We do have local tones set on the IP line and 4621. We are running on 406 V2 with 4.0.5 loaded. This did work under 3.2.55 Any Ideas?

So I finally had time to take my 406 offline and see if I could get the 4.0 release to work. Here is what I found out. The first thing I did was to default my config and start with a basic system, this worked fine with my H.323 line setup and my 4621 and needed routes in the system. So I...

So has anyone heard anything else about support for H.323 in 4.0? Is it just buggy in the release so far or is this Avaya's official position on the functionality of H.323 trunks. Just recently testing the H.323 trunk with the IP Office directly connected to the Internet with Public IP...

I would have to agree with your assessment that the H.323 trunks are crippled, I downgraded to 3.2(55) to test and see if I was nuts or if they didn't work under 3.2 and I didn't test. They work fine under 3.2(55) and the version prior to that. As for reliability, I haven't had much experience...

We have H.323 Trunking setup to an Asterisk endpoint providing VoIP into our IP Office 406v2 and it is working fine. After upgrading to 4.0 (5) the following problems started to occur: When a call comes in over an analog line and is forwarded out via forwarding on the extension to the VoIP...

Dial Delay count doesn't seem to be working. I set it to 3 from 0 and I would have to press # to get the call to complete no matter how long I waited for the call to be dialed. Set it back to 0 and it works with the timout delay of 3 seconds. Anyone else been able to change these...

I had this problem before under 3.2 and just removed the manifest file and it worked fine. Not sure if I broke anything by doing that but it did work...

You could use LCR and make the short codes like: Code: 1847N Telephone Number: N Feature: Dial Line Group: 1 (or whatever yours are) Do this for each Local Area code to strip off the 1 and Area Code. This will strip off the 1847 from the begining of the number, and send the rest to line...

Well fortunately our unit is still under warranty, so Avaya said we had to RMA it and send it in to be repaired. So off it goes for 4 weeks... They should have some hard reset capability on the systems to zero out the ram or at least default the password.

I am having the same type of problem with a P334T with SW Version 4.0.17 on it. I tried the root and password above but no luck. Does anyone know of a backdoor into this switch so we can reset the passwords etc?

Great that worked, it did reset all the passwords to the defaults. So had to go and set them back to what they should be. It kind of doesn't make sense that they require the current password to set a new one. If I know the old one probably wouldn't need to set a new one. So if you forget the...