Importing Inbound Routes

Status
Not open for further replies.

FWH

Customer
Advanced Certified
Joined
Aug 20, 2019
Messages
10
Reaction score
2
Using a new install of V16 to Import DID's. https://www.3cx.com/blog/docs/importing-dids/ references the following:


INSERT THE PORTS that you want to create DID’s for in [ ]
[10000][10013]][PORT NUMBER aka VIRTUAL EXTENSION NUMBER

Notice the plural usage of PORTS. Yet, when importing, I get an error for that field.

If I wanted to add the number to Ports 10000, 10001, 10002, 10003, and 10004, I would think it'd need to look like this:

[10000][10001][10002][10003][10004]] (based on the linked page) or [[10000][10001][10002][10003][10004]] but neither are working.

I also noticed that the PRIORITY field seems to be ignored.

Any thoughts?
 
  • Like
Reactions: Evolute IT
[10000][10001][10002][10003][10004]]
have you tried like this? does it work ?
[10000][10001][10002][10003][10004]]]]]
 
  • Like
Reactions: Evolute IT
AWS2P, That produces the same error.

SweetAction, PRIORITY isn't being respected. 1 vs 4 puts the rule in the same place, ironically at the very bottom of all of the other rules for that PORT (trunk).

My point in this thread is that the documentation on this topic might need refinement, but now I see there's possibly a bug or some configuration interfering with PRIORITY.

For the sake of this instance, there's over 100 DID's across 5 PORTS, so I'm just going to import them 5 times, doing a replace command in Excel each time for the Port Number.
 
  • Like
Reactions: AWS2P
Status
Not open for further replies.

Forum statistics

Threads
111,933
Messages
589,813
Members
164,808
Latest member
jsbjsb