The SGSN sends Location Update Request (BSSAP+LOCATION-UPDATE-REQUEST) over the Gs interface but does not receive a Location Update Accept (BSSAP+LOCATION_AREA_UPDATE_ACCEPT) from some MSC/VLRs as the SGSN includes the Originating Point Code (OPC) in the SCCP calling-party-address IE when the routing-indicator is set to 'ROUTE on GT'. The MSC/VLRs are unable to perform GT-based routing due to the presence of OPC in the calling-party-address generated by SGSN. The OPC has to be excluded from the SGSN generated SCCP Calling Party Address towards MSC/VLR on Gs interface. The OPC is not relevant in the SCCP Calling Party Address when routing indicator is set to "Route on GT". A new CLI-based control is introduced for the operators on Gs-service to include or exclude the OPC in the SCCP calling-party-address if the routing indicator is 'Route on gt'. By default the SGSN includes the OPC in SCCP calling party address when the routing-indicator is set to 'ROUTE on GT'. The operational benefit of this feature is that the MSCs/VLRs can perform GT-based routing easily. This feature is compliant with ITU Q.714 standard.