What is COR normally used 100 ??

[tech1302]

Hi


I have this strange issues on a clustered system when an ext on system B try to dial out on system A`s trunks

SIP Resilient + circuit is in place.
2 SIP Peers are programmed on both systems.

For some reason COR 100 is blocking system B trying to dial out on systems A`s trunks.
When i remove COR 100 on COR Group 3 on system A it works perfectly fine.
System A can dial out on system B`s trunks without any issues.

I cannot understand what is using COR 100 on both systems. None of the stations or trunks use COR 100.

Thanks

 

[tech1302]

COR 100 is not reserved for anything is it ?

 

[Mitel_specialist]

Are you using Direct IP Route between the systems? Direct IP route is using COS 100. Maybe you should check this COS

 

[tech1302]

@MitelAppie Yes, i`m using direct IP routes.
I can dial between sites even when COR 100 is in COR Group 3
Not sure how COS 100 is related to COR 100 ?

 

[Mitel_specialist]

I know nothing about COR 100. Never used it. This what the manual says:

COR Group 65 should be reserved for use by ARS for routing calls over Direct IP Routes (see ARS Routes form). Its use for other applications is allowed but not recommended. COR Groups 66 and up are reserved for future use.

 

[tech1302]

@MitelAppie Cheers mate
you guided me to the correct path


Default COS, COR, Interconnect, and Intercept Numbers Used by Direct IP Route
IP Trunk calls that use the Direct IP Route Routing Medium in the ARS Routes Form use:
 COR 100
 COS 100
 Interconnect 65
 Intercept 35
 COR Group 65
 Digit Modification Number 805
You can select different values, but typically should not need to. You can change COS 100 parameters, restrictions for COR Group

 

[kwbMitel]

It would not surprise me if COR 100 is related to DirectIP routing
I know COS 101 and COR 101 are related to auto-generated DN's for example

The fact of the matter is you assign a COR to Direct IP Trunks so that shouldn't matter (But maybe...)

 

[kwbMitel]

Looks like COR 100 is related somehow

Using the Direct IP Route method

The Direct IP Route is used to provision IP trunks between MiVoice Business systems. Trunks seized via the Direct IP Route medium use Interconnect Restriction 65 and the same fixed trunk attributes at both the originating (local) and destination (remote) end. The attributes are as follows:

Release Link Trunk is “No”
Call Recognition Serivce is “Off”
Class of Service is “100”
[highlight #FCE94F]Class of Restriction is “100”[/highlight]
Baud Rate is “300”
Intercept Number is “35”
Non-dial In Trunks Answer Point(s) are all blank
Dial In Trunks Incoming Digit Modification – Absorb is “0”
Dial In Trunks Incoming Digit Modification – Insert is blank
Trunk Label is blank

The IP trunk calls originated via the “Direct IP Route” ARS routing medium default to use COR Group 65 and Digit Modification number 805. You can select different values, but typically should not have to.

You can change COS 100 parameters, restrictions for COR Group 65, restrictions for Interconnect 65 and define intercept handling for Intercept 35.

 

[Valamagules]

Travelling Class Mask in System Options will keep your CoS and CoR tidy between cluster, best enable this when routing between systems.
This way CoS and CoR is retained between systems especially when you are doing SDS and sharing these forms.
In other words, your CoR for trunks and interconnect routing can be the same as your user CoR and CoS are carried through.

I always find this helpful


Clever men learns what Wise men shares!