SIP IP-network-region

[LambMan]

Hello,

Trying to get a definitive answer here.

Where does a SIP endpoint registering via an SM to an evolution CM gets it's IP-network-region / IP-codec to use ?

I do not believe it is from the IP-network-map as I have SIP users with IP addresses that are not in the map but they still function
in their correct IP-network-region and the status on the CM station created when adding the SIP user on SMGR shows the following:

GENERAL STATUS
Administered Type: 9608SIP Service State: out-of-service
Connected Type: N/A TCP Signal Status: not connected
Extension: xxxxxxxxxxx Network Region: 22
Port: S04713 Parameter Download: pending
Call Parked? no SAC Activated? no
Ring Cut Off Act? no
Active Coverage Option: 1 one-X Server Status: N/A

EC500 Status: enabled Off-PBX Service State: in-service/idle
Message Waiting:
Connected Ports:


Limit Incoming Calls? no

User Cntrl Restr: none HOSPITALITY STATUS
Group Cntrl Restr: none Awaken at:
User DND: not activated
Group DND: not activated
Room Status: non-guest room


Where does it gets it's assignment to Network-region 22 above ?????

 

[kyle555]

Release 7.1?

CM always does it the way you've outlined. SM gauges location based on the oldest/last via header in the invite. So, if you happened to have 10 regions go out 1 trunk to SM, SM can still parse out subnet/location of each phone. Same idea with CM - you can have 10 locations/subnets worth of h323 and SIP phones and 1 trunk between CM and SM and still have CM and SM be able to parse it all out.

There is a new feature that I haven't tinkered with that could possibly achieve that, but I doubt it would leave you with a half populated network map. Basically, you can have SM 'Locations' with the same name as CM Network Regions and sorta duct tape them together. It helps consolidate call admission control.