Anonymous issue in SPA8000

[etxnreg100]

Hi,

Have an issue with Anonymous calls from SPA8000.

The client is configured with as:

Use Anonymous With RPID:=yes

SIP Remote-Party-ID:=yes

When we do an Anonymous call, the "from" field is also set to anonymous.

Our ITSP need to have  the real a-number in the "from" field, and they will still hide the a-number due to RPID=privacy=full.

Is there a parameter in the box that could fix this?

Please can someone explain how the anonymous call INVITE should look

INVITE sip:11111111111@sip.domain.com SIP/2.0
Via: SIP/2.0/UDP x.x.x.x:5261;branch=z9hG4bK-f496338e
From: "Anonymous" <sip:anonymous@localhost>;tag=5e293c54162d3e74o1
To: <sip:11111111111@sip.domain.com>
Remote-Party-ID: "22222222222" <sip:22222222222@sip.domain.com>;screen=yes;privacy=full;party=calling
Call-ID: 9ae1f9d4-c5cf9ef4@localhost
CSeq: 102 INVITE
Max-Forwards: 70
Proxy-Authorization: Digest username="22222222222",realm="domain.com",nonce="58f5cc0853b4736aa1d6c8065c1915628ded2",uri="sip:11111111111@sip.domain.com",algorithm=MD5,response="0f5cb8d75f04b1d5d2bb23aa83905626",qop=auth,nc=00000001,cnonce="694b8e4"
Contact: "Anonymous" <sip:anonymous@x.x.x.x:5261>
Expires: 240
User-Agent: Linksys/SPA8000-6.1.12(XU)
Allow-Events: talk, hold, conference
Content-Length: 454
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura, replaces
Content-Type: application/sdp
 
v=0
o=- 114441273 114441273 IN IP4 x.x.x.x
s=-
c=IN IP4 x.x.x.x
t=0 0
m=audio 18465 RTP/AVP 0 2 4 8 18 96 97 98 100 101
a=rtpmap:0 PCMU/8000
a=rtpmap:2 G726-32/8000
a=rtpmap:4 G723/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729a/8000
a=rtpmap:96 G726-40/8000
a=rtpmap:97 G726-24/8000
a=rtpmap:98 G726-16/8000
a=rtpmap:100 NSE/8000
a=fmtp:100 192-193
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:30
a=sendrecv

[Dan Lukes]

Unfortunatelly, your provider requests nonstandard behavior. The SPA8000 is unable to comply.

In the case of RPID/privacy=full, the From should not disclose the caller number. It is because:

1. RPID unaware server will use "anonymous" From field - thus caller number will not be disclosed (as expected)

2. RPID aware server will use RPID header, thus it know the caller number as well as privacy=full request

It's matter of backward compatibility.

Server in question seems to be semi-RPID-aware which is incompatible with either scenario.

Ask your provider for advice. Unless he will offer no solution to you, you have little chance to solve it.

Well, you may install your own intermediate SIP proxy (Asterisk, for example) in attempt to convert standard phone's behavior to the one requested by provider.

[etxnreg100]

Hi Dan,

Thanks for your answer.

The phone is not directly connected to the ITSP.

In the middle I have a Sipfoundery proxy.

Yesterday I got more information from my ITSP, I had misunderstood them.

If the number is included in the P-Asserted-Identity header it will work.

Unfortunately when I use RPID from the SPA8000 the sipx proxy adding following: P-Asserted-Identity: "Anonymous" <sip:anonymous@localhost>

Please can you advise me for any workarounds?

Is it possible adding PAI already in the client (probably a very stupide question)?

Thanks

[Dan Lukes]

You may modify/remove P-Asserted-Identity header if Sipfoundry can do something like it.

Is it possible adding PAI already in the client (probably a very stupide question)?

You may try to use PAI instead on RPID on SPA8000 . It may or may not help.

So sory for my vague advices - I have no SPA8000 near now, so I can't try. And I'm not fammiliar with Sipfoundry proxy at all.

[etxnreg100]

Hi Again,

After some missunderstanding again from me.

My ITSP has sent me an example of how they want the INVITE header.

The INVITE must have the Privacy: id to hide the A-number :

Is is possible to add in SPA8000?

example

From: <sip:+11111111115@x.x.x.x>;tag=00C4-204A-324B3ECB.
To: <sip:2222222222@sip.domain.com>.
Max-Forwards: 67.
Call-ID: 0078-1D9A-575D19D2-00000063@2B90F47F05AD072AC.
CSeq: 863648502 INVITE.
Contact: <sip:+11111111115@y.y.y.y:5060>.
Supported: replaces, norefersub.
Allow: INVITE,ACK,BYE,CANCEL,INFO,NOTIFY,OPTIONS,REFER,SUBSCRIBE,UPDATE.
Accept-Language: en.
Content-Type: application/sdp.
User-Agent: VEGA5000/12.02.08.7xS023.
Content-Length: 245.
Privacy: id.
P-Asserted-Identity: <sip:11111111111115@sip.domain.com>.
Remote-Party-ID: <sip:11111111111115@sip.domain.com>;party=caller;privacy=full;screen=yes.

Thanks

[Dan Lukes]

Privacy: id is construct from RFC3325. So your provider wish for privacy style know as PAI (it's from P-Asserted-Identity) in Cisco's world.

Unfortunatelly, even in PAI world is suggested to use From: "Anonymous" <sip:anonymous@anonymous.invalid>. See specification's examples. It's for the same reason I described for RPID - backward compatibility with RFC3325 unaware systems.

You can configure SPA8000 to use PAI privacy style instead of RPID, but it will folow standard's suggestion and will use Anonymous in From. Such behavior is not configurable.

Unless Sipfoundry can be configured to modify the From: you are out of luck.

Some providers recognize a special prefix as hide caller id supplemental service code. In such case no special handling (e.g. no PAI or RPID) is required on client's side. Just dedicated prefix needs to be dialed in front of called number. Providers from EMEA countries use #31# prefix most of time, NANPA operators often use *81 prefix.

So ask your provider for such supplementary service code. If there's any ...

[etxnreg100]

Hi Dan,

Thanks for your answer.

It should be intrested to test PAI style, do you know which paramter I should change in the client?

[Dan Lukes]

It has been wrong to claim "you can configure ...PAI ...". Remember I have no SPA8000 near now.

As far as I know, SPA8000 sends both headers (e.g. PAI and RPID) at the same time. Just capture SIP dialog and verify it's provided - I can't test it by self.