- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2024 04:22 AM - edited 09-12-2024 04:31 AM
I have experienced, that the correct inbound dial-peer is not selected, and the call not sent to an outbound dial-peer.
I'm using are rather long list, that seems to kick in, even though there is no match there but a match in another list with a wildcard.
Adding an excact match solves the problem
Config snip (pattern maps attached) :
Wrong dial-peer:
dial-peer voice 34114 voip
description *** VK156451 TDC to Cube for Voice ***
huntstop
session protocol sipv2
destination dpg 3411
incoming called e164-pattern-map 3411
Correct dial-peer:
dial-peer voice 34194 voip
description *** VK156451 TDC to Cube ***
session protocol sipv2
incoming called e164-pattern-map 3419
Solved! Go to Solution.
- Labels:
-
Voice Gateways
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2024 05:21 AM - edited 09-12-2024 06:33 AM
There actually is a match in map 3411:
e164 +45384881[058]
This doesn’t have the leading carrot and trailing dollar sign to denote start/end of line, so it allows partial marches. This is a closer match than the wildcard pattern you have in map 3419.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2024 05:21 AM - edited 09-12-2024 06:33 AM
There actually is a match in map 3411:
e164 +45384881[058]
This doesn’t have the leading carrot and trailing dollar sign to denote start/end of line, so it allows partial marches. This is a closer match than the wildcard pattern you have in map 3419.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2024 01:16 AM
Thanks, I missed that typo.
