Search results for query: *

Not sure if this will work, but just had a very similar issue with a client. I first tried deleting/saving and then recreated the user thinking something was corrupt with the user. That did not fix the issue. I then deleted (saved), then recreated the incoming call route to that user. That...

Haha! I came back to this thread after a call and only read the second half. Yeah, that won't work then.

What is your shortcode for dialing out? Is it 8N;? If so, remove the ; and make it just 8N as that will send the digits over as you are dialing them.

It's an issue with Partner systems and cable modem lines as budbyrd stated. I have had carriers that have been able to fix it with reliable disconnect/clear disconnect/whatever their carrier calls it, but I have had some systems where the client stopped forwarding because the carrier couldn't...

Janni78 is right. You need to point the system to the pc running manager or vmpro. Then, manager or vmpro needs to be open on that pc for the system to grab the time.

....Or just send the incoming call route to the auto-attendant and set the line appearances to no ring.

If you are just talking about ringing, go to ext 10 r 11 and press Feature 00, left intercom twice, right intercom once and then enter extension 10. Press line 2 and line 3 until they are a fast flutter (no ring). This takes the ringer off of line 2 and 3 for extension 10. Repeat for each...

I used to use good old fashioned excel since the legend is fairly modular in look. I unfortunately don't have a copy of what I used anymore though.

That ticking sound is usually related to power. You may have a failing power supply or you may have too many digital phones connected to a single cabinet. If you cannot busyout and restore the trunk port the next step (in my opinion) would be to power cycle the system with that port unplugged.

It is enabled by default. If you have a module that ends in EC (308EC, 206EC, 400EC) they have caller id. Only 206E and 400E modules do not. If you are receiving caller id, but it is not logging the caller id, that does need to be programmed per line. The system also needs to ring twice in...

Create an H323 extension for the phantom user.

I would recommend deleting all messages in the hunt group before rebooting the IPO. If it still doesn't work, I would look at the smtp settings (unless this is the only mailbox not working).

Looking through old posts it sounds like TLS 1.2 was only enforceable using Linux (not windows). Is that still the case with R11.0.4.33? Can anyone confirm this?

If you have analog lines, make sure Allow Analog Trunk to Trunk Connect is checked for each line. If you don't have analog lines, check under System-Telephony and make sure Inhibit Off-hook Transfer is not checked.

Check in System Status to see if the extension is plugged in. If the extension is not plugged in, there is your issue.

Go to Help and About and just verify it loaded the R11 software properly.

You do need a license card in the V1 for it to power properly. It can have no licenses on it, but it needs to be present. We keep one at the office for that very reason.

That's what I was talking about. I always set the inbound to a hunt group even if it's just one user answering it. That way, if others need to cover they can log into it and take those calls.

Since they are in SCN, just have the main site log into the remote sites hunt group that is answering incoming calls.

I agree with Budbryd. Reset the security settings and I bet you can get in.