You have not provided the RL/RG details. Please open the route list details on each of the route groups that are included in the route lists and add that information to your document.
What is clear so far is this, on the route pattern used for sending calls to the PRI, ie *9.! you have a discard digit set to PreDot for the called number and your prefixing +226925 to the calling number. So this is what you need to put on the RL/RG level in the route list where you have the RG which holds your MGCP PRI as the second option so that your sending called and calling numbers in the format as your service provider expects it. Also on the other route pattern, the one used primarily for the SIP trunk, you are prefixing the calling number with +91224303. This as well needs to be put on the RL/RG level on the RG used for the SIP trunk as you cannot use the settings on the RP level if you want to achieve what you ask about.
On the MGCP PRI you’re using a CSS for called and calling number transformation named css-ISD. You need to look at what partition(s) that you have in that CSS and what transformation(s) that you have in these partition(s) as that would as well influence how you send these numbers to your service provider.
Sorry to say, but you need help with this as it’s evident that you don’t have the necessary skill set for this and without hands on assistance this would drag on for about forever. Please reach out to a reputable Cisco system integrator to acquire assistance with this.
Glad to hear that! However what you’re describing doesn’t make any sense at all as if the problem was caused by missing partition(s) in a calling search space calls via the route pattern that goes via the SIP trunk, ie the first option in the route list, would not have worked either.
Another thing, although not directly related to the problem you’ve been working on, by what you shared in the documents you have a CSS set for calling/called/redirecting number transformation. As that CSS, named “css-ISD”, doesn’t include any partition(s) used for transformation there is no need to have that set for transformation CSS’s on the MGCP PRIs. Recommend you to clear those settings and reset the MGCP trunks.
Add on bonus information, you should never ever mix call routing with transformations as that will lead to undesirable results. Any partition(s) and CSS(s) used for transformation should not include any selected partition(s) that holds configuration elements used for call routing, such as translation pattern(s), route pattern(s) or directory number(s).
Please use the correct terminology. A SIP trunk is not a PRI. That is an ISDN terminology and stands for Private Rate Interface. This has nothing to do with a SIP circuit.
