Thanks for that, it looks promising… It looks like I may need to upgrade to 15.4 (I’m on 15.3 right now, with CUBE 9.5.1). I guess I need to look into what this means for me, as I think going to 15.4 brings CUBE 10 if I’m not mistaken… I don’t want to have to go through A2Q again ☺
I’m probably pushing my luck here, but do you know of any “gotchas” when upgrading to 15.4 from 15.3.3m6? Right now, we use the cube for media forking (for UCCE QA) and PSTN ingress/egress with multiple carriers. From: Ryan Ratliff (rratliff) [mailto:[email protected]] Sent: Friday, November 06, 2015 1:06 PM To: Barnett, Nick Cc: cisco-voip voyp list Subject: Re: [cisco-voip] solution for multiple sip carriers? Nick, I’ve never done it myself but according to http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/inbound-hdr-for-outbound.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.cisco.com_c_en_us_td_docs_ios-2Dxml_ios_voice_cube_configuration_cube-2Dbook_inbound-2Dhdr-2Dfor-2Doutbound.html&d=BQMGaQ&c=M-KQspD_LQogCbR-BWCHOaeDEPOhF8vWqHZTaiwxT3c&r=T9uVLZucbHG2NKKKzOrp-o5cpdReHj02PkJJsCVkgfwcv7S0R5lDeFJg2VRbiNih&m=5AThMYFRQCRIgLIybeBxuza3NYKUcitqR1iVpcqbyDE&s=6hhkpEm01f2Chxka7LTw7atOKnxy-LrzHoq-0AmFGkM&e=> you can use inbound leg headers for outbound dial-peer matching. -Ryan On Nov 6, 2015, at 1:17 PM, Barnett, Nick <[email protected]<mailto:[email protected]>> wrote: 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 [email protected]<mailto:[email protected]> and [email protected]<mailto:[email protected]> 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 [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip<https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_cisco-2Dvoip&d=BQMGaQ&c=M-KQspD_LQogCbR-BWCHOaeDEPOhF8vWqHZTaiwxT3c&r=T9uVLZucbHG2NKKKzOrp-o5cpdReHj02PkJJsCVkgfwcv7S0R5lDeFJg2VRbiNih&m=5AThMYFRQCRIgLIybeBxuza3NYKUcitqR1iVpcqbyDE&s=kNdHPPGEpLBm2kkz_OI_Q0rapOwkR_Iv1QguiCsdm8Q&e=>
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
