@Mohammed al Baqari wrote: Digit manipulation can be classified as:     a. Implicit: As part of routing process         ○ Translation Pattern         ○ Route Pattern         ○ Route Lists     a. Explicit: Transformation after routing decision         ○ Incoming Calling/Called Party Settings on gateways, trunks (or device pools)         ○ Calling/Called Party Transformation CSS on gateways, trunks (or device pools)         ○ Calling Party Transformation CSS on phones (or device pools)   As the call is being processed, the order by which digit manipulation applied is as follow: You can see that the closer to the gateway, the higher the precedence of the manipulations. It is important to remember that if you manipulate on RP without modifying RL-RG manipulations (left them as default values), RP manipulations will take effect. If you modify any parameter in RL-RG manipulations (even if one), RP manipulations will be fully ignored. Same is applicable with Xformation Patterns and RL-RG manipulations.   Example#1   Let's assume that you changed 'Calling Party Transform Mask' under RP > Calling Party Transformations and changed 'Called Party Number Type' under RL-RG > Calling Party Transformations, in this case all settings under RP > Calling Party Transformations will be ignore including 'Calling Party Transform Mask'. The settings  under RL-RG > Calling Party Transformations will be used even the empty one for 'Calling Party Transform Mask'.   Example#2   Let's assume that you changed 'Calling Party Transform Mask' under RP > Calling Party Transformations and changed 'Called Party Number Type' under RL-RG > Called Party Transformations, in this case all settings under RP > Calling Party Transformations will be used and all settings under RL-RG > Called Party Transformations will be used. Thanks Mohammed. Definitely cleared some issues for me. Very helpful. Want to confirm the rule again (Even I see that you have explained). Called party xformation on Gateway ports (MGCP) will also follow the same rule.  e.g Called 1.212-234-5567 (RP with Pre Dot & +1) --> (RL / RG1 without DM ) --> SIP Gateway -- SP to Get +E164. (+1 from RP) Called 1.212-234-5567 (RP with Pre Dot & +1) --> (RL / RG2 with DM of Pre Dot & 1 ) --> MGCP VG --> SP to get 1212-234-5567 (1 from RG2) Called 1.212-234-5567 (RP with Pre Dot & +1) --> (RL / RG3 without DM ) --> MGCP VG (called Xform to append 123--> SP to get 123-212-234-5567 (123 from called xform) Thanks for assistance.  Nasir ... View more

For my setup the CUCM authenticates the user properly shows "login successful" message. and stuck on Phone registration.  I think the next TFTP pull is not working.   note: EM inside LAN setup is working fine. I am able to login with same username and password. The UDP and user association is proper.  ... View more

thanks for quick reply. I will check that out. ... View more

@sean Riley wrote: I figured it out.  Port on ASA was being blocked.  Got it working now. Hi Can you let me know which port specifically?  Doing POC and hitting the same issue.  Nasir ... View more

Thanks for reply Rath. for Non CUCM Apps. the last steps you mentioned "Make sure all the services are getting up and running, Initiate a Database replication and make sure the replications are Good" Once the IP address is changed and new publisher is online. How the sub will sync with new server instead of old server? Looking for some detail if i have to do anything on the Sub for CUC / CER / IM&P to point to new Pub. thanks ... View more