I should stop using speech to text ... TERMINATE calls through one carrier and 
accept origination from both.

-------- Original message --------
From: Ryan Huff
Date:11/06/2015 5:05 PM (GMT-05:00)
To: "Norton, Mike" ,"Barnett, Nick" ,cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] solution for multiple sip carriers?

I should probably further explain;  we would originate all calls through one 
carrier (the less expensive one) and terminate all calls from both carriers. We 
would use HSRP In cases where there were outages from the primary link.

Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: Ryan Huff
Date:11/06/2015 4:45 PM (GMT-05:00)
To: "Norton, Mike" ,"Barnett, Nick" ,cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] solution for multiple sip carriers?

Often times set providers Will allow you to mask caller ID however you choose. 
In cases where they do not, They should be able to remove the restriction If 
you ask. You may have to sign some forms in order for them to do that, If the 
provider services e911.

A few moons ago when I work for a regional service provider, We had a SBC that 
had a connection from level 3 And a connection from bandwidth.com.  We would 
prefer the level 3 connection for egress and failover to the bandwidth.com 
connection when the level 3 connection was down.

Basically we just sent all egress to the SBC and we let HSRP sort out Whether 
or not it was going out the primary connection or the failover connection.
Sent from my T-Mobile 4G LTE Device


-------- Original message --------
From: "Norton, Mike"
Date:11/06/2015 4:26 PM (GMT-05:00)
To: "Barnett, Nick" ,cisco-voip@puck.nether.net
Subject: Re: [cisco-voip] solution for multiple sip carriers?

Have you asked either carrier if they can remove the outbound caller ID 
restriction? With my carrier (PRI, not SIP, but same issue) it was basically 
just a matter of asking them.

-mn

From: cisco-voip [mailto:cisco-voip-boun...@puck.nether.net] On Behalf Of 
Barnett, Nick
Sent: November-06-15 11:17 AM
To: cisco-voip@puck.nether.net
Subject: [cisco-voip] solution for multiple sip carriers?

I’m looking for some advice on how people handle situations with multiple sip 
carriers. We have a mix throughout our company of DNs ported from 2 different 
sip providers. If only the first provider could have ported everything, but 
that didn’t happen. I’m trying to NOT use a proxy as I don’t want to maintain a 
giant list of DNs. Also of note is that the DNs are not in ranges…

I have a single CUCM 10.0 cluster and 2 CUBEs (one at each data center).  But 
since I’m just labbing this up, I’m just dealing with a testbed cube and test 
cluster.

I have 3 ideas on how to handle this. First was to use a CSS on the line that 
added sig/steering digits on the front… say… 000001 for carrier 1 and 00002 for 
carrier 2. Then I could peel them off and send them out to the correct SBCs for 
each provider. I don’t like this, it makes it confusing for support staff to 
see how a call SHOULD exit.

My other idea may be a pipe dream… I’ve added a URI to the DN, so, let’s say 
1...@carrier1.example.com<mailto:1...@carrier1.example.com> and 
1...@carrier2.example.com<mailto:1...@carrier2.example.com> on the 2nd carrier 
DN. Then I changed the sip trunk to the CUBE to pass this info to CUBE. I see 
the correct stuff flowing through, and it works with my standard incoming 
called number and destination pattern dial peers. Now, I’m trying to figure out 
how to write a URI dial peer that will do magic things for me. I need to be 
able to route based on calling party URI… is that even possible? I haven’t been 
able to find an example like this, so I’m beginning to grow skeptical.

The 3rd idea is to use CUSP, which I don’t want to do…

Incoming calls is not an issue. The problem arises when making sure that an 
outbound call placed from a number from carrier1 goes out a sip trunk to 
carrier1. If it doesn’t go to the same carrier that owns the TN, either the 
caller id will be overwritten with the sip trunks BTN, or I have to apply a 
diversion header and all calls show up as long distance (and no longer roll up 
into billing codes).

Is there some other preferred method that people use?

Thanks in advance,
Nick
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to