Search Order for Subscriber Addresses
A-2
The following figure shows an example of wildcard addressing.
Figure A-1 Wildcard Addressing Example
This configuration requires Port and Subscriber ID records in node 1 for:
Subscriber
00100
Subscriber
on LP 1, Port 3
123*
In node 2, LP, Port, and Subscriber records must be configured for:
Subscriber
12301
Subscriber
12302
Subscriber
12303
Subscriber
12304
If subscriber
sends a Call Request with any of called addresses
00100
, node 1 searches for a match, finds
12304
2, LP1, port 0, where node 2 reads the full called address in the packet and routes it
out the appropriate port.
A subscriber address that includes a wildcard potentially matches more addresses than
one with no wildcards. For example, the address
Without a checking mechanism an address with no wildcards could be read as a match
for an address with a wildcard, and sent to the wrong place. To avoid this, a search
order has been established for performing call routing:
Addresses with no wildcards will be searched first.
Addresses with only
Addresses with
*
Within each wildcard group, addresses with the most non-wildcard digits will be
checked first. For example,
P1
Node 1
P3 - Subscriber ID
123*
L1,P0
L0,P0
L0,P1
L0,P2
Node 2
L0,P3
on LP 0, Port 1
on LP0, port 0
on LP0, port 1
on LP0, port 2
on LP0, port 3
on Port 3, then routes the packet to node
123*
wildcards will be checked next.
?
will be checked last.
will be checked before
311012345678*
00100
12301
12302
12303
12304
12301
matches all other addresses.
*
3110*
FRX/FRM 3.3 User Guide, Rev 04
through
.
Need help?
Do you have a question about the SmartSwitch 6000 and is the answer not in the manual?