Well, a couple things here:
#1 - I recommend looking at using SIP domain based routing. You should not need multiple ports on the SM<->CM connections. You can create more than one signal/trunk group in CM to one or more SMs and use different far-end domains in the signal group, then route on the domain in SMGR. For example, we have multiple signal/trunk groups with <vendor>.trk.<company.domain> (just needs to be a build-up on your normal base SIP domain, does NOT need to exist in DNS). Add that domain in SMGR under routing \ domains and you can build a dial pattern entry that routes the outbound call via the domain. You just need to make sure that calls coming from those ITSPs have their FROM domain changed to match that far-end domain so inbound calls land back in that same signal/trunk group. You can do that in the SBC via topology hiding or within SM via adaptation.
#2 If you really must use separate ports, the issue you're having is fixed in 10.2 (just released today). Look for ASM-90555 in the Aura 10.2 release notes.
DM me if you want to have a discussion about domain-based routing.
------------------------------
Sam Osheroff
UC Engineer
University of Washington
Seattle WA
------------------------------
Original Message:
Sent: 12-15-2023 11:56 AM
From: Arslan Ali
Subject: Session Manager Routing with multiple
Hello to all,
We have a 10.1 System/Session, 10.1 SBC and 10.1 CM. With multiple LSP/BSM locations consisting of Analog, ISDN & SIP trunks for PSTN breakout.
Majority of endpoints on the system are H.323.
For location with SIP trunk from ITSP, We have configured separate SIP trunk between CM & SM for each location and this is done by using different port number on CM and SM side.
For example,
- Site A, SIP trunk number 100 from CM to SM with TCP pot 5070.
- Site B, SIP trunk number 200 from CM to SM with TCP pot 5071 & so on.
similarly on SM, separate SIP entities are created for same CM IP address to match port numbers.
Everything is working fine when LSP & BSM are not active and services are running from Main CM and SM.
When there is an outage on main site & survivable servers are activated, incoming calls are working fine but outgoing calls are not working as BSM is sending "407 Proxy Authentication Request" to LSP and then call gets terminated.
Data synch and replication status for BSM are fine and in green state without any errors on SMGR dashboard.
LSP location with Analog or ISDN trunks are working as expected in fail over mode.
Is this a design flaw or there is configuration issue ?
Please suggest / advise.
------------------------------
Arslan Ali
UC Consultant
Vodafone
------------------------------