IP Office -- Caller ID 2

[danielwestendorf]

Hey everyone,

Good news, we've finally gotten caller-id here in Idaho, which is pretty good considering we just got running water last week.

My question is, does anyone have any ideas of what can be done with caller-id and the IP Office/VM Pro system? I want to make our phone system better, but I'm not quite sure what can be done with caller-id. Any ideas or what you've done in the past that was cool would be great!

Thanks!

Daniel

 

[jamie77]

only just got caller ID?!?!?!?!? Did they take the arrows from the Indians out of the telephone pole over there yet????????!!!!!!!

You will know who is ringing so you can ignore them!!!!

Clever things like CLI routing can be done but few and far between.

At least now when you have a missed call you will know who it was!!!!

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[djuplift]

FSKD for Analog phones

 

[Bas1234]

When do you get Sip trunks over there then...in 2026?

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________

 

[sizbut]

So much and not just VMPro.

Route calls based on the CLI using IP Office Incoming Call Routes or VMPro Route by CLI actions.

DND Exception lists.

Trusted sources for remote access to mailboxes.

Call logs in apps and on your phones that can be used for return calls.

Fax server pass through of CLI.

Matching namees to CLI's using the Directory.

Scripts in Phone Manager.

 

[danielwestendorf]

Thanks for the ideas guys!

We're in Sun Valley, a pretty remote ski resort, so it was kind of a unique situation!

 

[danielwestendorf]

I do have another question concerning Caller ID. When a call comes in, it shows up as 13215551234 on the phone, which is how it should look. But if I go into the call log and try to call the number back, it doesn't go through because we have to dial 9 to route to an outbound line. Is there any way to automatically add that prefix? I have resorted to setting the line prefix to 91, but then the users get confused thinking there are too many digits. There has to be a solution for this, right?

Daniel

 

[Bas1234]

In the line options

Prefix: Default = Blank.
Enter the number to prefix to any ICLID received with incoming calls. If the IP Office has been configured, using short codes, to require users to dial a prefix to make external calls, adding the same prefix to incoming ICLID numbers allows those numbers to be used for return calls.

For outgoing calls: For IP Office 3.2 and lower, when a outgoing call is presented to the line with a leading digit to dial that matches the Prefix, that digit is stripped from the number. IP Office 4.0 and higher does not strip the prefix, therefore any prefixes not suitable for external line presentation should be stripped using short codes.


Greetzz..Bas

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________

 

[sizbut]

You went to the right field but you should only have to put 9 as the prefix (I'm not US based so others will may be better placed to confirm the prefixes needed). Thats just the way it is with IP Office*.

[*Unfortunately the IP Office was designed not to use prefixes at all. Just dial the number and if it didn't match an internal number then the IP Office would assume it must be external. Works fine in the UK (IP Office birthplace) but others are wed to the must use a prefix view]

 

[danielwestendorf]

Thanks for the info!