We checked the phone settings , there is no withholding your number on external calls . The number is showing for external calls. Issue is only for inbound call
We have IPO 500 v2 on R11.1 with PRI trunk . Inbound calls are directed from ICR to extension . Once the call lands on extension is it displayed as external and we cant see the telephone number of the person calling . I can see the number on system status but not on Avaya phone . What might be...
We have an expansion system on R11.1 with PRI line which is in service idle . We are unable to make outbound calls from this expansion server . We created a shortcode 9N; to line id 13 but not working
Attached is the trace from the control unit .
Can you advise what i am not getting right ?
Thanks everyone , the web-socket is working now . We changed the port of the web-socket client port from 80 to 443 and the line became in service . Thanks everyone .
There is no conflict on the system the web-socket server and client is showing out of service . Attached is the screenshot and monitor logs for your reference . I will appreciate your help.
Yes i can see that the websocket trunk is out of service on system status . I set the security level to unsecured . I can ping the IP address of both sites in system status lines page . Can you advise on what i can check ?.
We have SE primary and secondary on R11.1.3 on Remote site A and B .Phones in site A are registered to primary while phones in site B are registered to secondary server . I noticed We cant make calls from site A to B if we make it a websocket server /client but if works if we change the...
We have a couple of AVAYA J169 phones connected to ip office R11.1 . This is an on premise setup . We recently noticed that whenever we reboot the IP office the phones will ask users to enter enrolment codes . We have to press cancel so that the phone can work . This is becoming embarrassing...
@ IamaSherpa your method worked . I believe this forum is an asset to AVAYA .I really appreciate everyone that takes time out to help others on this forum .You guys are the real champions .
@megaa ACCS IP is already added to AMS as trusted node . Should i also add this as a SIP Route too ?. If yes which protocol should i use and should i select Proxy,Registrar or IM Proxy.
@westi , i made these changes on two users but it is not working . I removed the two users from the directory and put the shortcode on the user which i called from. Surprisingly, the call still went through to the called extension despite pointing to ars . Do i need to do remove all users...
I tried the auto dial option suggested by @ westi but it did not work . I just want to find a way to do this even if its not officially documented by AVAYA .
We have an ACCS R7.0.3 i keep getting this error while trying to upload announcement via Prompts management (MessageError An error occurred. Please contact your Administrator) . I got this alarms on D:/AVAYA/LOGS/CCMA promtmanagement log
UploadContent...
Yes we figured that call center agents are cheating the system in reports . Although we can see this information in report we want to totally prevent agent from doing it in first place .
Its a call center and we noticed agents make calls to themselves to prevent answering external calls . We want agent to be only able to call supervisor extension 5015 .Please help.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.