CLID as "anonymous"

[hebegb41]

I have a CM/SM SIP system 10.2 we recently converted carriers from my post from a week ago and the only issue we are now having is that when a call comes in from the outside we are not getting the CLID (#) of the caller. When we traceSBC & SM we see the "from" as the number. But when we trace in CM we see odd numbers as CLID and on the display of the J139 SIP phone we see "anonymous". We do get the "NAME" but no #. So we appear to be seeing the CLID in the SBC, then in the SM, but when we trace the phone in the CM, we see a bunch of garbage #s that come up as CLID. So we suspect the break is between the Session mgr. SM and the CM.....but where....

All of our dial patterns look good and are no different than the previous carrier. All calls are working and our OUTBOUND CLID is fine. It's just the inbound.

Any thoughts are greatly appreciated

 

[Instructor of Avaya]

Here are some thoughts that might point you in the right direction.

I know of two reasons why the FROM header would show sip:anonymous@anonymous.invalid.

1) The first is that somehow "privacy" was invoked. In the traces, look for the SIP header & value: Privacy: ID

2) The more frequent reason is a misconfiguration of Communication Manager. Typically, the problem is found in the Private Numbering table or sometimes the Public-Unknown tables. All of your SIP extension numbers need to be accounted for within the table.

Almost always in the SIP world the "Caller-Id" is taken from the P-Asserted-Identity (PAI) header, not the FROM header. I believe it is on the SIP trunk-group form (page 3?) where you can choose which one CM uses (FROM or P-Asserted-Identity) for caller-id.

I hope that helps.