We currently have a single CUCM and UCCX (HA) cluster. We purchased through cisco a NFR to add an additional CUCM and UCCX cluster strictly for in house testing. We integrated the 2 via a SIP trunk and would like to know the best way of routing call from our production cluster across the SIP trunk to the NFR system. For example we would like to route digits 800261XX to the trunk via a route pattern but when the NFR cluster recieved the call we would like it to strip 8002 and just see 61XX as we are using extension in this range on the NFR system. Our triggers in our UCCX NFR environment will be in the 61XX range. If a route pattern is not the best way to accomplish this then I am open for any other suggestions. Thanks!!
You can do all the digit manipulation you desire on either side, either you strip the digits on the calling side, or you do that in the inbound SIP trunk of the target CUCM.
Good information from both of you, my original thought was to do it on the remote cluster and simply did not have any reasoning for that decision. Is there any benefit from doing it on the source cluster vs. the remote cluster? Just trying to keep things simple and clean, thanks again for both you and Jaimes suggestions.
Really no difference one way or the other, comes down to personal choice. If you are going to do this on remote cluster then you will need to build separate translation pattern to match 8002.61XX and strip preDot there.
As Jaime points out (+5) CUCM provides flexibility to do it on either side. I would recommend doing it on the source cluster either on the Route partners or called party transformation applied to the SIP trunk. If doing it on RP, you can simple configure the pattern as 8002.61XX and them strip preDot, which would result in 61XX being passed to the other side.
Learn, share, save
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
