2 Years? ? whoa.

Can you give us any more info?

Do you have a sysmon trace of a failed call attempt? I assume this is over SIP lines.

You need to provide way more information. I am assuming this is an IPO but you didn't even state that... What version is it running? What firmware are the phones running? Does this happen on internal calls (say internal call to voicemail) or only external calls? What kind of trunks do you have? What have you actually tried to do and ruled out?

The more information you can provide the more likely you are to get helpful posts.

The truth is just an excuse for lack of imagination.

I saw issues in the past where button the digits are sent multiple times to IPO when a button is pressed. Worth to have a look into sysmon.

IP Office remote service
IP Office certificate check
CLI based call blocking
SCN fallback over PSTN

Hi

Thanks for all the replies/responses.

How to find whether we are using SIP lines, IPO, trunks? Please guide me.

This issue is for every outgoing call, also for international calls. Internal Extension calls are working fine.

We are using the following:

AVAYA IP Office R8.1 Manager
AVAYA IP Office 500 Control Unit

Sorry but if you do not even know what kind of trunks you have I think your current issue is beyond the scope of help in this forum. I suggest you hire a competent BP to help you.

The truth is just an excuse for lack of imagination.

OK

But if anyone does not know, there should be some method of knowing about the kind of trunks.

If you know that method, let me know please. I will check and let you know what type of trunks we are using.

No,

Like Critchey said. That is not what this forum is about.

This forum is meant for proffesionals. And sorry, but if you don't know how even to find out what trunks you have, then no we're not wiling to help you.

Most of the people here spend lot's of time learning in order to make a living.

Please get yourself a proper Avaya certified businness partner on site.

Het probaplly will fix this in 1 or 2 hours.

Quote (Okie26)

Het probaplly will fix this in 1 or 2 hours.

What, Im pretty certain that a quick look & the config & possibly a check of the traces will explain the probllem in less than 30 min (including a 15min coffee break)

Do things on the cheap & it will cost you dear

Avaya Remote Support Engineer (A.R.S.E)