The ars route gets a cor group value, the user gets a cor value. Example route 10 has a cor 10, in cor group for anyone listed in 10 cannot use this route
That makes sense, group vs value.
Phrase to help here... "If you're not in, you're out."
Meaning if your COR is not in the COR Group, then your call goes out.
Phrase to help here... "If you're not in, you're out."
Meaning if your COR is not in the COR Group, then your call goes out.
Funny, I was told the opposite saying.
"If you're in, you're out" meaning if you're in the COR Group you're out of the call (i.e. bugger off, you can't make the call)
Haha yeah I can see how both are correct but best to settle on one or could get confusing
This may or not be the "correct" answer [aka "I don't understand CoR either"] but I usually use Interconnect Restriction to do this. Restrict one of the interconnect numbers from using one of the SIP trunks and everyone who you don't want to use that SIP trunk, put them in that interconnect number.
Hmmm, I'll have to do some further reading on that one as I've only seen interconnects as a setting which I have never touched before.
What I ended up doing which worked insofar as it has chosen the correct trunk:
Sip trunk A (Trunk attribute COR 3):
Routes 1 - 7, with COR's 1 - 7
Sip trunk B (Trunk attribute COR 30):
Routes 10 - 17, with COR's 10 - 17
COR group 3: 10-17
COR group 30: 1-7
Digits dialed points to route list 1 which has route 1 as first choice and 10 as second choice
Phones with COR 3 can only use routes 1-7 and phones with COR 30 can use routes 10-17
(In traces I can see it trying to go out the correct trunk but phone still saying invalid but I suspect that might be another issue with the trunk itself which I ran out of time today to investigate further)