Search results for query: *

IPO Server Edition 11.1.2.2.0 build 20 Saw last night that my disk space was at 90% full. Rooted in to see that the /var/log/audit/ folder was 57 gigs. Onex logging is off, and Onex is disabled. Besides, that log folder is /opt/avaya/onexportal/11.1.2200_30/apache-tomcat/logs. That folder is...

Sending the PRI call Incoming callroute to a VMPro Module that transferred with $CLI_NAME in Source of Transfer worked.... but get this... for only the first call. I tested calling the 212-555-4000 number and they got my CID and CNAM. While on the call, I called from another cell phone and nope...

IPOTS, this is not an incoming SIP call. We are taking an incoming call from a PRI, then forwarding out to SIP. The Invite to the SIP from the IPO is missing the CID NAME. If you forward a call from a SIP trunk to another SIP trunk, the CID and CID NAME are pushed out the forwarded SIP trunk...

The problem is it needs to show the name of the caller calling on the PRI, putting a static name in wouldn't help. The client is a Police Station and when they get a non emergency call to the Avaya PRI, they want it to come to their dispatch via SIP. This works. It's just the CID Name doesnt...

Internal didnt work either. It's like the IPO is refusing to "see" the Caller ID Name from the PRI call.

With or without all these checked, the invite to the SIP trunk always shows FROM "number" sip:number. Instead of "NAME" sip:number.

IPO 11.1.2.2 Control unit is part of server edition. Calls come into the Control Unit from PSTN on a PRI from carrier. Calls to one number on the PRI are being forwarded to a dispatch SIP trunk. Incoming number is 212-555-4000. Incoming call route points to "4000". 4000 is a short code...