A-2 FRX/FRM 3.3 User Guide, Rev 04The following figure shows an example of wildcard addressing.Figure A-1 Wildcard Addressing ExampleThis configuration requires Port and Subscriber ID records in node 1 for:l Subscriber 00100 on LP 0, Port 1l Subscriber 123* on LP 1, Port 3In node 2, LP, Port, and Subscriber records must be configured for:l Subscriber 12301 on LP0, port 0l Subscriber 12302 on LP0, port 1l Subscriber 12303 on LP0, port 2l Subscriber 12304 on LP0, port 3If subscriber 00100 sends a Call Request with any of called addresses 12301 through12304, node 1 searches for a match, finds 123* on Port 3, then routes the packet to node2, LP1, port 0, where node 2 reads the full called address in the packet and routes itout the appropriate port.Search Order for Subscriber AddressesA subscriber address that includes a wildcard potentially matches more addresses thanone with no wildcards. For example, the address * matches all other addresses.Without a checking mechanism an address with no wildcards could be read as a matchfor an address with a wildcard, and sent to the wrong place. To avoid this, a searchorder has been established for performing call routing:l Addresses with no wildcards will be searched first.l Addresses with only ? wildcards will be checked next.l Addresses with * will be checked last.Within each wildcard group, addresses with the most non-wildcard digits will bechecked first. For example, 311012345678* will be checked before 3110*.Node 1Node 20010012301123021230312304P1P3 - Subscriber ID 123*L1,P0 L0,P0L0,P1L0,P2L0,P3
