Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Problem with anonymous caller id in spa8000

Hi,

We have started to migrate our customer from pap2t to spa8000.

Now we got an issue that we need help with.

If we activating CID block (*67) the sip server will deny the INVITE

I think it has to do with from and contact field.

All parts is now anonymous, in pap2t the real number is still in the <>.

Is it possible to change this?

Any Ideas?

My invite looks as following:

INVITE sip:11111111@sip.mydomain.com SIP/2.0

Via: SIP/2.0/UDP 2.2.2.2:5360;branch=z9hG4bK-ff7fa670

From: "Anonymous" <sip:anonymous@localhost>;tag=1fdbc659fb942988o0

To: <sip:11111111@sip.mydomain.com>

Remote-Party-Id: "33333333333" <sip:33333333333@sip.mydomain.com>;screen=yes;privacy=full;party=calling

Call-Id: 612a4f6d-18571384@localhost

Cseq: 101 INVITE

Max-Forwards: 70

Contact: "Anonymous" <sip:anonymous@2.2.2.2:5360>

Expires: 240

User-Agent: Linksys/SPA8000-6.1.12

Allow-Events: talk, hold, conference

Content-Length: 444

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER

Supported: x-sipura, replaces

Content-Type: application/sdp

Date: Mon, 02 Dec 2013 15:29:48 GMT

with pap2t is look like this:

INVITE sip:111111111@sip.mydomain.se SIP/2.0

Via: SIP/2.0/UDP 3.3.3.3:5061;branch=z9hG4bK-1ff53e0

From: Anonymous <sip:22222229@sip.mydomain.se>;tag=c0bc166c356c37ffo1

To: <sip:111111111@sip.mydomain.se>

Call-Id: 8d9cc4b0-68e7be8b@localhost

Cseq: 101 INVITE

Max-Forwards: 70

Contact: Anonymous <sip:22222229@3.3.3.3:5061>

Expires: 240

User-Agent: Linksys/PAP2T-5.1.6(LS)

Content-Length: 438

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER

Supported: x-sipura, replaces

Content-Type: application/sdp

Date: Mon, 02 Dec 2013 19:01:54 GMT

//N

  • ATAs Gateways and Accessories
Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
VIP Gold

Re: Problem with anonymous caller id in spa8000

Just to be sure - do you know you are replacing one end-of-life platform (PAP2T) with another end-of-life device (SPA8000) ?

But back your question.

Your's PAP2T's INVITE has no CLIR active. Caller number is present in both From: and Contact: header, there is no Privacy: Id nor Remote-Party-Id.

So, next-step exchanges know nothing about CLIR and caller's number is transferred to called phone with no restrictions.

On oposite side, SPA8000's invite claim CLIR using Remote-Party-Id method. But your's SIP gateway is rejecting such call.

You either have no right to use CLIR or particular SIP gateway is configured to use other way to request CLIR Remote-Party-Id. Or the CLIR CALL request is rejected somewhere on the path to destination.

Simplest solution ? It seems that CLIR did not worked on your's former network correctly and caller's number has been delivered to called user with no restriction. So disable CLIR service on SPA8000. No functionality will be lost.

Message was edited by: Dan Lukes (SPA8000 is not EOL)

5 REPLIES
VIP Gold

Re: Problem with anonymous caller id in spa8000

Just to be sure - do you know you are replacing one end-of-life platform (PAP2T) with another end-of-life device (SPA8000) ?

But back your question.

Your's PAP2T's INVITE has no CLIR active. Caller number is present in both From: and Contact: header, there is no Privacy: Id nor Remote-Party-Id.

So, next-step exchanges know nothing about CLIR and caller's number is transferred to called phone with no restrictions.

On oposite side, SPA8000's invite claim CLIR using Remote-Party-Id method. But your's SIP gateway is rejecting such call.

You either have no right to use CLIR or particular SIP gateway is configured to use other way to request CLIR Remote-Party-Id. Or the CLIR CALL request is rejected somewhere on the path to destination.

Simplest solution ? It seems that CLIR did not worked on your's former network correctly and caller's number has been delivered to called user with no restriction. So disable CLIR service on SPA8000. No functionality will be lost.

Message was edited by: Dan Lukes (SPA8000 is not EOL)

New Member

Problem with anonymous caller id in spa8000

After I diabled the "Remote-Party-Id" is work fine.

New Member

Problem with anonymous caller id in spa8000

Dan,

Where have you seen an EOL for the SPA8000?

I searched and have not found one.

http://www.cisco.com/en/US/products/ps10024/prod_eol_notices_list.html

Thanks

VIP Gold

Re: Problem with anonymous caller id in spa8000

You hit. My mistake, it's not true.

New Member

Re: Problem with anonymous caller id in spa8000

:-)

Just bought 8 of them, glad they are not EOL.

1124
Views
0
Helpful
5
Replies
This widget could not be displayed.