December 14, 2019, 03:47:35 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Setting up Circle of Trust # for aa  (Read 1584 times)
jazzy
Jr. Member
**
Posts: 55


« on: October 25, 2011, 12:48:46 pm »

When setting up a CoT number, in the inbound call route, what is the difference
when using these (2) call routes?

Voice Services -> SPx Service -> X_InboundCallRoute : {11231231234!:aa},{ph}
w/ exclamation point

Vs

Voice Services -> SPx Service -> X_InboundCallRoute : {12341234567:aa},{ph}
w/o exclamation point
Logged
RonR
Hero Member
*****
Posts: 4527


« Reply #1 on: October 25, 2011, 01:10:31 pm »

An exclamation point (!) is normally used in front of a rule in a DigitMap to bar (prevent) the calling of an outbound number by forcing the match to be false:

(!1900xx.|1xxxxxxxxxx|<1>xxxxxxxxxx)


In InboundCallRoutes:

{12341234567:aa},{ph} sends calls from 12341234567 to the Auto Attendant and all others to the PHONE Port.

{!12341234567:aa},{ph} is probably not very useful as it causes calls from 12341234567 to NOT go to the Auto Attendant, which is the same as the rule not being present at all.
Logged
jazzy
Jr. Member
**
Posts: 55


« Reply #2 on: October 25, 2011, 04:43:33 pm »

OK, so if I want (2) different numbers to be picked up by the aa, will this work?

{(12222222222|13333333333):aa},{ph}

where the 2's= number A, and the 3's= number B.
And all other incoming calls will ring the attached phone.


Logged
RonR
Hero Member
*****
Posts: 4527


« Reply #3 on: October 25, 2011, 04:49:35 pm »

OK, so if I want (2) different numbers to be picked up by the aa, will this work?

{(12222222222|13333333333):aa},{ph}

where the 2's= number A, and the 3's= number B.
And all other incoming calls will ring the attached phone.

You've got it!
Logged
jazzy
Jr. Member
**
Posts: 55


« Reply #4 on: October 25, 2011, 04:55:37 pm »

Thanks Ron, just wanted to run it by before making the changes in my OBI

Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC