Search results for query: *

Has anyone else noticed that the help section of the new manager is completely useless? Anyone aware of plans to fix this in future releases?

Got it. Thanks to all for helping.

yeah I got that. Seemed easy enough. I guess I need to jump on monitor and see if I can see the pbx trying to send data to the ip.

I decided to go with Kiwi at the guidance of Jenne. But I guess I don't have something right. No data is being sent to the program. Anybody have simple instructions for getting call data to show up on kiwi? Not much to the pbx side, just enter the IP and port number.

Ooops, not smtp , that should have been smdr. any helpful guidance would be appreciated.

So all I have to do is configure the IP address / port of the machine running the 3rd party smtp software and that's it? I thought there was some kind of Avaya program that had to put call data into a .csv first.

Can anyone tell me where this file is? Everything I've read says its on the Admin CD, but I am not seeing it. Why does everything have to be so complicated with IPO? I've got a 8.1 pbx that needs SMDR out, and I have the 2 dvd set that came with it, but I am not seeing SMDR folder anywhere on...

Can anyone tell me, based on this trace, why calls across SCN are failing with error code 17? Any help as always much appreciated. 0:58:45 2506273mS PRN: 421: Digit Pressed 2 10:58:45 2506274mS CMCallEvt: 0.1039.0 -1 BaseEP: NEW CMEndpoint f4f4b604 TOTAL NOW=1 CALL_LIST=0 10:58:45...

Upgraded a system from 8.1 (63) to 8.1 (81) All the phones display "Upgrade File Access Error" Any suggestions? This is a new one to me. I've done this same upgrade on several before without a hitch.

Is there a way to have VMPro save recorded calls to a specific file location not on the VM server or contact store? One of my clients already has a call recorder server that saves all calls from their analog 911 system. Can I setup VMPro to save pbx calls to that server as well?

I had a customer with an IP50 8.0 system. Started having network problems, and I assured them it wasn't the IPO, but the ISP refused to work with us until we swapped out every possible point of failure. So I put a new chassis in, put all the cards in it. Did not solve the problem. Now I have...

Is that what Reason 3 means? I see places throughout the traces that say phone unregistering because of reason 3.

...Monitor=2 SSA=0 TCP=31 TAPI=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034 11486423mS RES4: XML MemObjs=45 PoolMem=2097152(1) FreeMem=2082064(1) ********** SysMonitor v10.1 (67) [connected to 10.1.1.50 (Diamond C)] ********** 11492292mS PRN: Monitor Status IP 500 V2 8.1(63) 11492292mS PRN...

Good Call. Thanks.

Can anybody tell me at first glance what's wrong with the registration syntax for this handset? ********** Warning: Logging to Screen Started ********** 14:39:02 619875mS SIP Rx: UDP 11.11.11.40:5060 -> 11.11.11.4:5060 REGISTER sip:sip2.ipdialog.com SIP/2.0...

Wow I was not even close. Thanks. Still getting 403s in monitor for some reason.

I have the privilege of installing a 3rd party IP dect system. Its an RTX. Handset comes with a IPUI # of 1188705A85 I am thinking this would convert to an IPEI of 7181500231738 Would somebody mind checking my translation to ensure I have that right?

Using 1416 and 1408 phones on IPO 8 and 9

This is what the customer bought.

This is the latest and greatest, 9. But after my customers discovered it for me, I tried it at my office on my ver 8. Same thing happened. Very strange, but very bad too.