Session Manager SIP option responses

[mattKnight]

Gosh, I'm asking 2 questions inside a week... What is going on!

System Manager 6.3.17 and Session managers 6.3.17

When a LSP is inactive, any SIP trunk to it returns a "503 - Service Unavailable (LSP is Inactive)" response to a SIP options message. The SM/SMGR marks the entity link as conn status to "DENY" and the Link status also as "DENY". Crucially, when it does this, the SM dashboard doesn't display the link as down (red). I'd say this behaviour is, at least, understandable - other people may argue about it being correct - but that is an argument for another day!

I have another device that also gives a "503 - Service Unavailable" response to a SIP options message when the service is inactive (they are an active-standby pair so obviously 1 is always inactive!). Why does this Entity link get marked as conn and link status to "DOWN"?

Is there a way to remap "503 - Service Unavailable" to deny for this link?


Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[kyle555]

I don't think LSPs should have their own entity link.

ESSs should, and they should be in Local Host Name Resolution for your CM. Call CM the locally significant host "matts.pbx" where your core and ESS IP each map to "matts.pbx" with different priorities of which to see first - and there's some dispute/discussion to whether you'd want to hit the ESS first because its live, or keep hitting the core first to use it so long as it's alive. See "force phones and gateways to active survivable servers" in "display systemp-parameters ip-options" and there's whitepapers about how to plan that failover.

Anyway, that said. When a LSP with BSM goes live, that LSP over-writes the far end node name of all sip sig groups of which a SM is the far end with the IP of the BSM. In the BSM administration, when it goes live, it's baked in (either through the System Platform install, or through a config script in the CLI on R7) that the LSP should be the far end of it's CM SIP entities.

All to say, I don't think LSPs should have SIP entities built in normal administration. You would have entity links from the BSMs to "matts.pbx" but not from every LSP to the core or BSM.