CUBE, UCM and anonymous calls

[fhk-cseifert]

Hi folks,

I have a problem with my CUBE (IOS 15.2.3.T2) and forwarded anonymous calls...

At 1st call leg from UCM to CUBE, UCM sends the INVITE msg including "privacy=uri" flag at Remote-Party-ID:

--snip--

INVITE sip:0049176xxxx@xxxx:5060 SIP/2.0

Via: SIP/2.0/TCP 139.6.232.18:5060;branch=z9hG4bK2566e3febe67d

From: "Anonymous" <sip:anonymous@anonymous.invalid>;tag=3787129~9ca825f5-016d-4c82-abfb-dc0513225884-50837057

To: <sip:0049176xxxx@1xxxx>

Date: Thu, 08 Nov 2012 10:03:23 GMT

Call-ID: 8693ad00-9b1836b-b55e-12e8068b@xxxx

Supported: timer,resource-priority,replaces

Min-SE:  1800

User-Agent: Cisco-CUCM8.6

Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY

CSeq: 101 INVITE

Expires: 180

Allow-Events: presence

Supported: X-cisco-srtp-fallback

Supported: Geolocation

Cisco-Guid: 2257825024-0000065536-0000001001-0317195915

Session-Expires:  1800

P-Asserted-Identity: "xxxx" <sip:xxxx>

Privacy: id

Remote-Party-ID: "xxxx" <sip:xxxx>;party=calling;screen=yes;privacy=uri

Contact: <sip:xxxx:5060;transport=tcp>

Max-Forwards: 70

Content-Type: application/sdp

Content-Length: 386

--snap--

But at 2nd call leg from CUBE to provider, the CUBE sends only "privacy=off":

--snip--

Nov  8 10:03:23.295: //9066/8693AD000000/SIP/Msg/ccsipDisplayMsg:

Sent:

INVITE sip:0049176xxxx@xxxx:5060 SIP/2.0

Via: SIP/2.0/UDP xxxx:5060;branch=z9hG4bK1484F8

Remote-Party-ID: "xxxx" <sip:0049xxxx@xxxx>;party=calling;screen=yes;privacy=off

From: "anonymous" <sip:anonymous@139.6.232.5>;tag=341992AC-1FD7

To: <sip:0049176xxxx@xxxx>

Date: Thu, 08 Nov 2012 10:03:23 GMT

Call-ID: 5D8E5E34-28C211E2-A4D7F907-95917214@139.6.232.5

Supported: 100rel,timer,resource-priority,replaces,sdp-anat

Min-SE:  1800

Cisco-Guid: 2257825024-0000065536-0000001001-0317195915

User-Agent: Cisco-SIPGateway/IOS-15.2.3.T2

Allow: INVITE, OPTIONS, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY, INFO, REGISTER

CSeq: 101 INVITE

Timestamp: 1352369003

Contact: <sip:anonymous@xxxx:5060>

Expires: 120

Allow-Events: telephone-event

Max-Forwards: 69

Session-Expires:  1800

Content-Type: application/sdp

Content-Disposition: session;handling=required

Content-Length: 443

--snap--

At the dial-peer, the "voice-class sip privacy-policy passthru" is already configured...

Following the ucm-settings of the sip-trunk:

Thanks very much for any hints!

Greetings, Chris

[Ayodeji Okanlawon]

Chris,

So what problem is this creating for you? How would you like it to work

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

[fhk-cseifert]

...aehmm, sorry.

CUBE should passthrough the privacy-flag from ucm-call leg.

Now, the provider will screen our main-phone number at the called phone in pstn, because privacy=full or privacy=uri is missing.

Thanks, Chris.

[Ayodeji Okanlawon]

Why dont you use a sip profile to address this..If you configure a sip profile  and apply it to the dial-peer pointing to the provider, ti should apply the privacy setting configured on it.

Do you need help with the sip profile?

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

[fhk-cseifert]

Yes, i tried that before:

voice class sip-profiles 1

request INVITE sip-header Remote-Party-ID modify "privacy=off" "privacy=full"

...but after that, every call will be sent to the provider anonymous. :-(

[Roger Kallberg]

Christian Seifert wrote:
Yes, i tried that before:
voice class sip-profiles 1
 request INVITE sip-header Remote-Party-ID modify "privacy=off" "privacy=full"
...but after that, every call will be sent to the provider anonymous. :-(

You could use a set of different dial peer so get around that problem. That would of course require some change in CUCM so that the call can be routed out via the right dial peer, for example add a prefix to the called number, let’s say 790 for calls that shouldn't hide the caller ID and 890 for calls that should. Then in the VGW you can use these prefixes to route the call out via the correct dial peer. Just remeber to remove the prefix from the called number before the call is sent to the ITSP.

Please remember to rate helpful responses and identify helpful or correct answers.

[fhk-cseifert]

Hi Roger,

I think that would be a choice, if our internal users only dial anonymous or not... but in our case, the incoming calls (f.ex. from anonymous cell phone) to cisco phone which is forwarded to an external phone (an other cell phone).

pstn =E1=> cucm =sip=> cube =sip=> pstn

[Roger Kallberg]

You might be able to use the solution in this post, https://supportforums.cisco.com/message/3055028

Please remember to rate helpful responses and identify helpful or correct answers.

[Ayodeji Okanlawon]

I see the problem with this, the other thing you can do is to configure sip profiles to match the numbers that you only want to screen their numbers. This will work assuming the numbers are in a range etc and are not disparsed.

The other option is to do what Roger suggested or you could raise a TAC case to know why this is happening..What IOS are you running, this may be a defect

Please rate all useful posts

"'Nature is too thin a screen, the glory of the omnipresent God bursts through it everywhere"-Ralph Waldo Emerson

[fhk-cseifert]

Hi all,

I would just give you an update about my problem above... It was a (stupid) wrong configuration myself... default dial-peer 0 was matched at incoming calls from ucm to cube. (I should look more to debug voip ccapi inout logs... ) So in this case, cube does not forward the privacy flag and the command voice-class sip privacy-policy passthru is not working. After correcting the dial-peer (adding correct incoming called-number command) it works as it should.

So thanks again for our hints.

Regards, Chris