Alright, lets start at the beginning...can't help much with the last question, since I've never worked with SIP, but let's see if we can get your routing straightened out to your SIP trunk.
Also, forget the Translation Pattern for now, and let's go back to Route Patterns.
First, you have your SIP trunk added as a trunk in CCM, not a gateway, correct? And there's no caller ID DN set on it...? I know with gateways, a great deal of the time, any caller ID DN or transformation on the gateway will override any other pattern you have set in a TP/RP/RL. Also, check your settings on your SIP trunk in CCMAdmin - do you have a CSS assigned to your trunk containing the partition that contains the RP (95.XXX or whatever you're using) that is pointed at the SIP gateway?
Second, where are your outbound calls going - are your outbound patterns (e.g. 9.@, 9.1XXXXXXXXXX, 9.XXXXXXX, if you use explicit patterns) pointed to a separate gateway?
Third, route patterns - create a route pattern with the pattern of 95.XXX. For this example's sake, say you assign it a partition of SIPTrunkPT. Make sure you assign the SIPTrunk, if you can, in the Gateway or Route List Field. Make sure Route This Pattern is selected, and select the call classification as OffNet, since you're using outbound dial prefix (9). Question: Are these calls all within the same location, or two different ones? Why use a dial prefix if these calls are staying within the same company?
Now, when you get down the bottom of the RP configuration, enter in the following in the Called Party Transformations section:
Discard Digits: PreDot
Called Party Transforma Mask: 4611115XXX
Don't use the Prefix Digits field also, one or the other.
This should work, provided that you don't have anything else overriding the outbound digit Caller ID.
There's one more thing we can try, but give this a shot first, and let me know.
TMH