Outgoing number on caller ID

[CommoGuy101]

Hi Everyone,
I have a merlin magix with a PRI installed.
They currently have two companies using this switch.
One company has 15 users and the other has 20 users.
Right now when outgoing calls are made the same caller ID information is outpulsed.
When customers see the number they call back.
Only the first 15 users want this number to be outpulsed.
The other 20 want a seperate number outpulsed so customers call back to the correct destination.
Can that be done on the Merlin with Only 1 PRI?


Thank you all,
CommoGuy101101

 

[XrayboX]

Legend/Magix sending outgoing caller id with a PRI is kinda limited.
your options are:
send Extension number
base with extension (overwriting last digits)
by channel
or nothing.
BUT you can't mix, and match.
So to answer you question , you can't send company A's main number, & company B's DID's.

If your provider is willing/can, see if they can capture/block company A's DID's and replace them with a fixed number.




When Linux is Free and Open, who needs Windows or Gates?

 

[merlinman]

Well, I've never done it, but I see no reason that you couldn't "split" the Main Pool into 2 separate ones so that each group of folks can only access their own out dial pool.

Then, you could, under Lines Trunks> Pri > Number to send, set the two groups of lines to send their own unique Caller ID number.

I have had found that if you send the leading number + the extension, unless an extension has a D-I-D, it can't call out.

But I believe the idea I just threw out should fly.

http://home.comcast.net/~merlinman

-merlinmansblog.blogspot.com

 

[XrayboX]

Merlinman, what I ended up doing to allow non DID extensions to call out, was get additional DID's (80 total), but use dial plan routing tables to grab their incoming call and route them to a single adjunct assigned to coverage group 1, covered by the main calling group (771)
Each table entry can reroute 10 DID's (XY0 to XY9).
Now per extension caller ID works, any extension can call out, but only authorised extensions can receive direct calls.

Merlinman am I correct in my understanding that you can't mix base+ext & fixed number by line(trunk)?



When Linux is Free and Open, who needs Windows or Gates?

 

[merlinman]

Yes, that's a correct statement. As you are programming the "Number to send" it states :FOR ENTIRE SYSTEM".

I guess I missed the part in your original post that stated how you were sending the "Number...."

http://home.comcast.net/~merlinman

-merlinmansblog.blogspot.com

 

[dagwoodsystems]

I think I have your answer. As you suggested, you want to break the PRI into two trunk groups as you see fit for demand. In this example, I'll put 'em in 70 and 890. Let's say it looks a little like this:

801 3/ 1 No Remote 70 Yes Long 4
802 3/ 2 No Remote 70 Yes Long 4
803 3/ 3 No Remote 70 Yes Long 4
804 3/ 4 No Remote 70 Yes Long 4

805 3/ 5 No Remote 890 Yes Long 4
806 3/ 6 No Remote 890 Yes Long 4
807 3/ 7 No Remote 890 Yes Long 4
808 3/ 8 No Remote 890 Yes Long 4


For all lines in Pool 70, program Number To Send as 555-1212 (or whatever) and all lines in 890 to 444-4444 (or whatever). Soooo....

Slot 3 Switch: DMS-100
System: By line
BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
1 3 CallbyCall By Dial Plan

Channel ID: 23 22 21 20 19 18 17 16 15 14
13 12 11 10 9 8 7 6 5 4
3 2 1

Line PhoneNumber NumberToSend
824 5551212
811 5551212
812 5551212

813 4444444
814 4444444
815 4444444


For ARS tables 25 and 26, set Pool 70 to have an FRL=3 and for Pool 890 an FRL=2. It should look something like this:


TABLE 25: Default Toll Output Table

Pool Absorb Other Digits FRL Call type Start Pattern
1)70-- 00 -------------------- 3 BOTH --:-- A
2)890- 00 -------------------- 2 BOTH --:-- A

TABLE 26: Default Local Output Table

Pool Absorb Other Digits FRL Call type Start Pattern
1)70-- 00 -------------------- 3 BOTH --:-- A
2)890- 00 -------------------- 2 BOTH --:-- A


Then the last thing is to assign ARS restrictions to specific extensions. In this case, stations with ARS Restriction set to 2 can only use 890 (and thus outpulse that trunks specified outbound ID) and stations with ARS set to 3 will use 70 (and the associated ID. Of course, those with ARS=3 will choose 890 secondarily...but I can't help ya on that part. Just break the pools wisely.

A station report will look something like this:

1/ 1 101 JACK M N N N N U 3 N 1/21 7300 N N N N U 3 N
1/ 2 102 TOM T N N Y N U 3 N 1/22 7301 N N N N U 3 N

1/ 3 103 PAUL C N N N N U 2 N 1/23 7302 N N N N U 3 N
1/ 4 104 TIM A N N N N U 2 N 1/24 7303 N N N N U 3 N


In this scenario, Jack Morgan and Tom Thiel will send 555-1212, while Paul Chudigian and Tim Alberstein send 444-4444.

Tim Alberstein

http://www.dagwoodsystems.com

 

[TouchToneTommy]

Of course, those with ARS=3 will choose 890 secondarily...but I can't help ya on that part. Just break the pools wisely.

What if you renumbered pool 890 to 6, gave those that should be using it a station FRL of 1, and also gave them pool dial out code access to pool 6. Then DON'T put pool 6 in the ARS tables as a secondary route.

You now have users that dial 9 for their outbound calls, and others that have to dial 6, sending their respective CID's

 

[dagwoodsystems]

True! So my my way presumes that we keep 'em all in the dark by advertising "just dial 9 to make an outside call". Specific extensions are associated with a specific company. Keeps it simple but isn't without a drawback or two. Your way covers the possibility that people don't always stay put. "If you work for Company A, dial 9 first to make an outside call. Company B? Dial 6 first...rule applies from any phone" which gives flexibility.

Tim Alberstein

http://www.dagwoodsystems.com

 

[Telecomboy]

I have a client set-up using ARS 3 and 4 using dial 9 for both companies and it is a bit of a hassle. Every time someone moves you have to make sure you also check their ARS and make sure it is correct. It's easier on the end-user though since everyone dials 9.

 

[XrayboX]

dagwoodsystems

What if you use three pools 70, 890, 891 with 70, and 891 being the "real" pools, add a couple open line ports (pots) into 890, when pool 70 runs out of lines, it'll roll over to 890.
couldn't you even set up 890 to strip all digits and jumper the lines over to T/R extensions that are in a group with a delayed announcement device, then the user can be told to try again ?


I still say if your service provider is willing to selectively substitute outgoing numbers, then sending Base+ext is the best (and easiest) solution.
If all the service provider can do is allow CID pass through, or force fixed CID info, then if they can do it per channel, than dagwoodsystems idea (minus number to send) would give the results CommoGuy101 is looking for.

If the service provider can't do anything, then your limited to two pools sending separate main numbers, or sending base+ext and setting up dial plan routing to grab company A's DID's and routing then to a common destination.

PS can one of the Merlin gurus confirm if my three pool Idea is doable , or am I
(I like to think I have a decent grasp of ARS/FRL ) but haven't needed to actually use more than pool 70 for everyone.

When Linux is Free and Open, who needs Windows or Gates?

 

[TouchToneTommy]

Tim, very true that one company has to dial 9, and the other has to dial 6, instead of just being uniform throughout the building. But by changing the FRL and assigning the pool dial out code, phones that use 9 will get wave off dialing 6, and vice versa (actually with a station FRL of 1, they could dial 9-911 but that's it). I kinda read it that there are 2 companies sharing one switch, instead of folks wearing two different hats at different times.