[cisco-voip] Basic corlist question

[Lelio Fulgenzi]

This graphic really helps. From : https://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/42720-configuring-cor.html

So, yes, the call succeeds.

[cid:image001.png at 01D47067.6EF96ED0]

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of Ed Leatherman
Sent: Tuesday, October 30, 2018 3:11 PM
To: Cisco VOIP <cisco-voip at puck.nether.net>
Subject: [cisco-voip] Basic corlist question

At least - I think this is basic...

Can a call with an incoming corlist (based on the inbound dialpeer) match an outbound dialpeer that has no corlist? Basically, following the lock/key idea, the outbound dial-peer has no lock so anything can match it.

I'm trying to go through a vendor-provided IOS config for a SIP integration between a Cisco router and our public safety's dispatch system, and it keeps matching on a dialpeer we are not expecting, based on how we _think_ it is supposed to work. Essentially the scenario above.

Thanks!

--
Ed Leatherman
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20181030/d5416553/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 132801 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20181030/d5416553/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1297 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20181030/d5416553/attachment-0001.png>