External Routing between M1 & G3

[dan]

I am tring to route calls from a Meridian 1 and a Lucent G3. I am getting the following error in the G3 TServer log.

extrouter: cannot process request attribute TrackingNumber is missing

My guess is I need a parameter in the Meridian TServer to add the TrackingNumber to the the route request.

I found in the release notes that the TrackingNumber is .. instead of relying on call_id, TServer marks each call (using UUI field) with a Tracking Number (generated by TServer as serverid shifted 16 bits left, plus a sequential number).

Anybody run across this before?

[James]

What links do you have between the switches?