[cisco-voip] [EXTERNAL] Re: CUBE Config Dial Peers

Anthony Holloway avholloway+cisco-voip at gmail.com
Sat Jun 13 18:25:10 EDT 2020


It's not wrong to do digit manipulation on the CUBE, I just chose not to,
since it didn't make sense to me to make the CUBE configuration any more
complex, and CUCM is perfectly suited for digit manipulations.

Consider posting your config for review.  :)

On Sat, Jun 13, 2020 at 8:26 AM JASON BURWELL <JASON.BURWELL at foundersfcu.com>
wrote:

> Thanks Brian an Anthony for all the great information and examples. My
> config does not look anything like this so it looks like I’ve got some work
> ahead of me. I’m glad to see no digit manipulation is needed in the
> example. I’ve been told that we have to do digit manipulation on the CUBE
> which I questioned and part of what led me to ask here.
>
>
>
> Jason
>
>
>
>
>
> *From:* Anthony Holloway <avholloway+cisco-voip at gmail.com>
> *Sent:* Friday, June 12, 2020 8:53 PM
> *To:* Brian Meade <bmeade90 at vt.edu>
> *Cc:* JASON BURWELL <JASON.BURWELL at foundersfcu.com>;
> cisco-voip at puck.nether.net
> *Subject:* [EXTERNAL] Re: [cisco-voip] CUBE Config Dial Peers
>
>
>
> *CAUTION: This email originated outside of Founders Federal Credit Union.
> Do not click links or open attachments unless you recognize the sender and
> know the content is safe.*
> * ------------------------------ *
>
> All great points, thanks for taking the time to respond.
>
>
>
> The only one I think that I need to reply to is the DPG and
> destination-pattern one.  I was actually troubleshooting a customer CUBE
> wherein this exact scenario was in place and the only negative was getting
> options to work.  Otherwise, it was routing the call just fine.  Granted, I
> couldn't tell you what version that was, as it was like a year or so ago,
> but either way, I always put a destination-pattern on because you need one
> for options to function.
>
>
>
> I guess I could reply to one more, and that has to do with tweaking
> retries from 6 to 2 AND using options.  Why stick to one, when you can do
> both?
>
>
>
> Here's the one I use which I said was very similar to yours.
>
>
>
> The first thing to note is the numeric structure of my tags.
>
>
>
> 1000 series numbers are the ITSP side
>
> 2000 series numbers are the CUCM side
>
>
>
> I would expand this to 3000, 4000, etc., for additional integrations like
> PRIs, FXO, second ITSP, second PBX, etc.  Most I ever had was 6
> integrations into a single CUBE i think.
>
>
>
> The second digit is 1 for incoming and 2 for outgoing.
>
>
>
> The 4rd and fourth digit are generally not used, unless I need additional
> dial-peers for the same peer and direction, but doing something slightly
> different.  Most I ever used was like 15 i think.  E.g., 2215  But that was
> not using IP addresses in the matching and DPGs, that was using phone
> number matching, and I was using steering codes.
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200613/7c9fc083/attachment.htm>


More information about the cisco-voip mailing list