Sometimes, the same UC500 and IP phone user site may serve different companies. It is therefore important, to be able to identify the inbound call based on the called number. There are several ways to do this:
1) Configure directory entries (under telephony service) for the DIDs and associate the entries with appropriate company name. In addition to this, the "service dnis dir-lookup" needs to be enabled under the telephony-service. Please note that this command is enabled in the default configuration files for UC500, so the only thing that is needed, is create directory entries.
2) Have each inbound number ring on different line buttons of the IP phone. This would give a quick visual indication of which company is being called, and each button can also be labeled with the appropriate company name. The idea is the to segregate the dialplan. See below:
- Create new Class of Restriction lists:
!
dial-peer cor custom
name IncomingRuleA
name IncomingRuleB
!
dial-peer cor list CompanyA
member IncomingRuleA
!
dial-peer cor list CompanyB
member IncomingRuleB
- Create POTS dial peers like these:
!
dial-peer voice 1 pots
incoming called-number AAAAA
direct-inward-dial
corlist incoming CompanyA
!
dial-peer voice 2 pots
incoming called-number BBBBB
direct-inward-dial
corlist incoming CompanyB
- Create Ephone DN’s like these:
!
ephone-dn 21 octo-line
number 1111
label Company A
corlist outgoing CompanyA
!
ephone-dn 22 octo-line
number 2222
label Company B
corlist outgoing CompanyB
- Assign to the phones like this:
!
ephone 5
button 1:21 2:22
!
3) If using FXO (no DID support), the following can be done:
- Organize the FXO POTS dial peers in groups
- Assign each corlist to each dial peer PAIR. Example:
!
dial-peer voice 50 pots
destination-pattern 9.T
voice-port 0/1/0
connection plar opx 201
corlist incoming CompanyA
!
!
dial-peer voice 51 pots
destination-pattern 9.T
voice-port 0/1/1
connection plar opx 201
corlist incoming CompanyA
!
!
dial-peer voice 52 pots
destination-pattern 9.T
voice-port 0/1/2
connection plar opx 202
corlist incoming CompanyB
!
!
dial-peer voice 53 pots
destination-pattern 9.T
voice-port 0/1/3
connection plar opx 202
corlist incoming CompanyB
.
.
.
- Assign a corlist to an octal ephone DN that is a shared line across phones. Something like this:
!
ephone-dn 21 octo-line
number 201
corlist outgoing CompanyA
!
ephone 5
button 1:21
!
ephone 6
button 1:21
!
ephone-dn 22 octo-line
number 202
corlist outgoing CompanyB
!
ephone 7
button 1:22
!
ephone 8
button 1:22
!
.
.
.
The idea is to segregate the dialplan. An incoming call on one of the FXO ports will trigger a connection plar to an octo dn that is part of that CORLIST ONLY. That octo DN will be shared by all phones in that group. If there is phone overlap (one phone belongs to more than one group) then you can map the octo DN to a different button on the same IP phone. That way, the user can visually differentiate calls between company A and company B.
Notice that the global commands to define the corlist members are not included here (previous example had instructions on how to add them).
Also, you may have many more POTS dial peers because of your dialplan. You will need to group them accordingly and map a corlist to each group.
