Disable the session-ID field in SIP header (cucm + cube)

[KevinA]

Hello there,

We have a trouble where some phone number can't be reached. It only concerns few number, like 3 or 4 identified atm, but regularly, a new number is identified which seems to have the same behavior.

After some exchange with the provider, it seems our system (CUCM 11.5 and a 2901 CUBE) sends a "session-ID" field in the SIP header. The provider told us to get rid of this field as others customers with a similar configuration doesn't send this field, and it works perfectly for them when they try to reach the same number. That's the only differences they found at the moment.

Some research on this session-ID helped me understand the meaning of this field, but not how to set-it up, and even less to disable it. So here I am, trying to find a solution to disable this field in the header we're sending to the provider.

Here's the cube configuration for the voice service voip if that can help :

voice service voip
ip address trusted list
ipv4 XXX.XXX.XXX.XXX (address of the provider)
ipv4 XXX.XXX.XXX.XXX (address of the cucm)
ipv4 XXX.XXX.XXX.XXX (other addresses that I don't recognize)
ipv4 XXX.XXX.XXX.XXX (other addresses that I don't recognize)
ipv4 XXX.XXX.XXX.XXX (other addresses that I don't recognize)
allow-connections sip to sip
supplementary-service h450.12
no supplementary-service sip moved-temporarily
no supplementary-service sip refer
redirect ip2ip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback pass-through g711ulaw
sip
bind control source-interface GigabitEthernet0/0
bind media source-interface GigabitEthernet0/0
header-passing
error-passthru
registrar server expires max 120 min 60
localhost dns:provideradress.domain
midcall-signaling passthru

Let me know if you need some others information.

Regards,

[KevinA]

Hi guys,

A quick update to see if someone has an idea on this subject. I'm still looking how to modify this sip header.

Regards

[Anthony Holloway · Accepted solution]

I'm not sure you can disable, though, maybe...

Assuming not though, you'd want to implement a SIP Profile on your Outgoing dial-peers to the provider to remove the header.

Read about the feature here:
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/cube/configuration/cube-book/voi-sip-param-mod.html

Do some validation testing here:
https://cway.cisco.com/tools/SipProfileTest/

[KevinA]

Thanks for this reply, as it was exactly what I was looking for !

I managed to create a voice class sip-profile to be applied on a dial-peer, and it's working fine.

The line added are the following one :

voice class sip-profiles 10
request INVITE sip-header Max-Forwards modify "Max-Forwards: 12" "Max-Forwards: 68"
request INVITE sip-header Session-ID remove 


dial-peer voice 201 voip
 voice-class sip profiles 10

After applying these commands, the calls could be placed properly, and it seems to be working fine now.

The "Max-Forwards" modification was also suggested by the provider, so I don't know if only one of these commands could have worked, but I guess I won't be able to do much more tests now it's working.

I still don't know how or why these field were sended in the header, but I least I can remove them before going out of the CUBE.

Thanks a lot for your help !