Outgoing caller id number on magix

[Shermanchicken]

Customer has merlin magix. The service provider says the the outgoing number that is being sent on caller id from the customer is a number that was a test number that they provided when the PRI was turned up. They are wondering if the phone sysem is blocking or programmed to send out that test number instead of the customer's main number. All of this is new to me. The ciruit has been working since October. Any thoughts? Thank you.

 

[TouchToneTommy]

The Magix can be set to send a specific number or a "Base" number plus the extension number to form their DID.

The provider can also set themselves to ignore what the Magix sends and send something different, such as their main number or the billing number associated with the account.

First ascertain what the carrier is doing. If they want the Magix to control the outbound CID, you will have to program it on a per line basis. The Base plus extension number gets sticky if you have extensions that don't match the incoming DID numbers, and the carrier blocks outgoing calls if you try to send a number that isn't one of your DID's. In that case it's best to send the main number or just let the carrier control it.

 

[XrayboX]

What I ended up doing was get a large enough group of DID's so every extension could send a valid Base Number + Ext.
Then for the range of extensions that were NOT ALLOWED to receive incoming calls, under dial plan routing, I rerouted them to a phantom extension (covered by the main group, and night service).
now every extension sends a valid caller ID that rings back to the correct extension, or common group, controllable by me (Magix 4.0)

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

 

[CarGoSki]

print PRI and post

 

[SYQUEST]

[tt]XrayboX please explain your special configuration for non-DID stations for outgoing CID when using PRI for the Magix or Legend! This should be most revealing...

....JIM....
[/tt]

 

[XrayboX]

Every extension that will make outside calls HAS to have a VALID DID number
say your DID range is 6100 to 6199
you're going to use 6170 to 6199 as NON DID recipients (has DID but can't receive incoming direct calls)
Setup outgoing as base + extension
Every extension that needs to make outgoing calls has to be in one of these ranges (6100 to 6199) or (100 to 199)

Use table 0 to route the basic DID #
To reroute 6170 to 6199 will take 3 more routing tables
Patterns to match
table 1) 617
table 2) 618
table 3) 619

Route tables 1,2, & 3 to where ever you want,operator, group, where ever.

the only downside is it takes one table per 10 DID #

You want to make sure you get a large enough contiguous group of DID numbers to handle your future needs, put your unused DID extensions in a covered coverage group so if someone miss dials you'll still get the call.


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

 

[XrayboX]

After I posted, I realized you could separate the incoming DID calls group from non incoming group just by giving one group 4 digit extensions, and the other group 3 digit. Then you'd use a single routing table to send calls to incoming calls group.
Calls for the non incoming group would route to operator as DID#? or covered adjunct

All DID receiving extensions are 4 digit
All NON DID receiving extensions are 3 digit (with matching 4 digit adjunct to receive/route incoming calls)




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

 

[Shermanchicken]

Here is the print of the PRI info. Thank you.




----- Site: USDAG. Captured: 04/17/13 -----
PRI INFORMATION



Slot 6 Switch: DMS-100

System: By line

BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
1 6 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
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835

Network Selection Table

Entry Number: 0 1 2 3
Pattern to Match: 101**** 10***

Special Service Table

Entry Number: 0 1 2 3 4 5 6 7
Pattern to Match: 011 010 01 00 0 1
Operator: none none none none none none none none
Type of Number: I I I N N N N N
Digits to Delete: 0 0 0 0 0 0 0 0

Call-By-Call Service Table

Entry Number: 0 1 2 3 4
Pattern 0: 0
Pattern 1: 1
PRI INFORMATION


Pattern 2: 2
Pattern 3: 3
Pattern 4: 4
Pattern 5: 5
Pattern 6: 6
Pattern 7: 7
Pattern 8: 8
Pattern 9: 9
Call Type: BOTH BOTH BOTH BOTH BOTH
NtwkServ: No Service
DeleteDigits: 0 0 0 0 0

Entry Number: 5 6 7 8 9
Call Type: BOTH BOTH BOTH BOTH BOTH
NtwkServ:
DeleteDigits: 0 0 0 0 0

Dial Plan Routing Table

Entry Number: 0 1 2 3
NtwkServ: Any service
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:

Entry Number: 4 5 6 7
NtwkServ:
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:

Entry Number: 8 9 10 11
NtwkServ:
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:

Entry Number: 12 13 14 15
NtwkServ:
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:



----------------------------------- ANNOTATION -----------------------------------

 

[CarGoSki]

You are not sending any number. If you were then you would see one number entry per bchannel.

Line PhoneNumber NumberToSend
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835



PRI Telephone Number
The PRI telephone number is a string of up to 12 digits (any combination of digits 0–9) assigned to
each PRI line. This string is matched to the Called Party Number sent by the network to indicate
the number dialed by the outside caller. The system uses this number to send the call to the
correct Personal Line button.

Copy Telephone Number to Send
This option specifies whether or not the telephone number to send to the network for outgoing
calls made on PRI lines assigned to a B-channel group is copied from the PRI telephone number
assigned to that PRI line. Select the Copy Telephone Number to Send option when the telephone
number sent to the network should match the number received from the network, indicating the
number dialed by the outside caller. Select the Do Not Copy Telephone Number option either when
a telephone number to send is assigned to each PRI line in the B-channel group or when no
telephone number is to be sent to the network. (This can be used to block outgoing Caller ID,
system-wide.)

Telephone Number to Send
This option assigns the telephone number to send to the network when outgoing calls are made on
PRI lines. If the person being called subscribes to a PRI caller identification service, the number
indicates who is calling.
Test Telephone Number
This option assigns a test line telephone number for each 100D, 100R INA, or 100DCD module
installed in the control unit that provides ISDN PRI service.

Station Identification-Automatic Number Identification (SID-ANI) as Calling Party Number.
Facility-based information is used by the network for sending the Calling Party Number. If the
SID-ANI option is programmed (and the service subscribed to), the system sends a system-wide
base number of up to 12 digits, of which the final digits (up to 4 digits) are replaced with the
number of the extension from which the call was made. For example, a call made from extension
7104 with a system-wide base number of 908-555-7000 sends the number 908-572-7104. For
facility-to-facility calls where there is no call-originating extension (for example, Remote Call
Forwarded calls), the system-wide base number is substituted. Trunk-to-trunk transfer, however,
results in a CPN that consists of a base number in which the last digits are replaced by the number
of the transferring extension.
In some instances, the system-wide base number is not sufficient to cover all extension numbers
in the system. For example, the base number might be 908-555-7000 and there might be a group
of extensions, 7000 through 7099, that correspond to telephone numbers from 908-555-7000 to
908-555-7099; there might be another group of extensions numbered 300 through 399 whose
telephone numbers are 908-555-0300 through 908-555-0399. In a case like this, there is no base
number that can cover all of the extensions so that the number sent is the correct number for the
extension.
The MERLIN MAGIX Integrated System’s PRI support for calling party identification extends to
MCI and local exchange (DMS-100) subscription services.

Outgoing Calls
PRI
When placing a call using a PRI facility, you may want to append a # to the dialed number. This
signals the facility that the number is complete and causes the call to be placed immediately.
The outgoing telephone number that matches the digit pattern in the Network Selection Table is
deleted automatically. This is not programmable. The common carrier ID is sent to the foreign
exchange.
In systems that are programmed using a non-uniform extension dialing plan, one base number
may not be able to represent all telephones.
To specify that no telephone number is sent to the network, choose the Do Not Copy Telephone
Number programming option and use the Telephone Number to Send procedure to ensure that
telephone numbers are not assigned to each channel in the B-channel group. A network option to
block presentation of CPN is also available.
If ARS identifies a call as applying to a call-by-call B-channel group but the Call-by-Call Services
Table does not show a matching digit pattern and bearer capability, the call is rejected.
Outgoing calls using call-by-call service selection can be made by pressing a line button, pressing
a Pool button, dialing a pool number, or using ARS.
The Call-by-Call Services Table must be programmed for the Call-by-Call Service Selection
feature to take effect. If a service is not specified in the table, the entry is ignored.
An SMDR record is not recorded for any call on a PRI facility that is shorter than the programmed
SMDR Call Length. Usually, the SMDR Call Length is programmed to compensate for connection
and ringing time of calls on non-PRI facilities before they are answered. For systems where most
lines are PRI lines, the call length should be programmed for one (1) second.

 

[SYQUEST]

[tt]XrayboX,

Please elaborate on your explanation. I don't see the connection for non-DID stations to use the main DID as default for outgoing CID in the Magix when using BASE + NUMBER. Where are tables 0,1,2,3? How do those relate to assigning outgoing CID to a non-DID station? For example, if my DID number block is 680-2400-2499, and I receive a 3-digit feed, I assigned my DID stations 400 thru 499, but I have some non-DID stations 500 thru 520. How are you going to assign 680-2400 as outgoing CID when calls are originated on stations 500 thru 520 using BASE + NUMBER? To my knowledge there is NO WAY to do this! Avaya never completed the software to handle this correctly! Instead, they discontinued the Legend/Magix and started pushing the IPO!

....JIM....
[/tt]

 

[XrayboX]

SYSQUEST in order for base + ext to work, any extension that needs the ability to call out HAS TO HAVE A DID, but if you capture the incoming call before it hits the extensions, those who aren't allowed to receive calls, won't.
You are correct when you say base + ext can't handle non DID compatible extensions (other than remote call forwarding)

if your DID's are 2400-2499
and you're receiving 3 digits (400-499)
You have to assign something in the 400-499 range to the non Direct inward extensions, you originally used 500 thru 520, so I'd use 480-499 to give you twenty contiguous extension numbers to reroute on incoming calls.
Lets say you want group 771 to handle your main number/Unassigned extensions (you could just as easily substitute the operator, or any extension)

so your dial plan routing would look like

[tt]table|-match-|delete digit|add digit
__0__|{blank}|___{blank___|_{blank}
__1__|___48__|_____3______|___771
__2__|___49__|_____3______|___771[/tt]

The order doesn't matter, it uses best match,
so
400-479 would match table 0
480-481 would match table 1
490-491 would match table 2

Now all your extensions (that need to be able to call out) are in the DID range of 2400-2499, but 2480-2499 get routed to group 771, so extensions 480-499 never receive a direct call.
It isn't ideal, but it works around the Legend/Magix limitation for unique outgoing caller ID.


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

 

[TouchToneTommy]

So really, you need to burn a DID number for every extension, it's just that extensions in a certain range will have their incoming calls redirected. Not much help if you only have a handful of DIDs

 

[SYQUEST]

[tt]That might be practical for your situation, but not mine. For my application the non-DID stations need to have the CID of the main number applied for outgoing calls, which in my example is 680-2400, not a bunch of other numbers! Outgoing calls are the problem, not incoming! So the original Avaya issue stands! Nothing new here...

....JIM....[/tt]

 

[XrayboX]

SYQUEST In my first post in this thread I said

What I ended up doing was get a large enough group of DID's so every extension could send a valid Base Number + Ext.

I never said anything about base number only.

TouchToneTommy
In a perfect world, Avaya would have fixed PRI outgoing CID back in the Legend.
This is simply a hack, like chopping up a spare phone to get group & loudspeaker paging together (before Avaya added it to Magix).
It isn't a perfect solution for everyone, but if most extensions have a DID going to them, and more and more people rely on their "recent call list" to return calls, I consider the cost of extra DID's cheap.



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