cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Walkthrough Wednesdays
10766
Views
85
Helpful
14
Replies

How to remove video sdp header SIP

I am searching for a solution to alter a SDP header to not send video capabilities to a SIP trunk provided by an ISP. The reason is that calls from a Cisco Jabber softphone fails for outbound calls, I receive a "media not acceptable here": inbound works fine. 

Cisco Jabber => CUCM => SIP TRUNK => CUBE => ISP SIP TRUNK

Settiing up calls inbound works fine, using a cisco hardware phone (with no video capabilities) works fine for outbound calls. According to the ISP they do not allow that there is video capabilities in the SDP header!!!???? I want to make the ISP ignoring these SDP settings but that seems for them to be difficult. So, question is, can i remove the capabilities in the SDP header on the CUBE and if; how is that possible? 

 

Received:

SIP/2.0 100 Trying

Via: SIP/2.0/TCP 213.XX.XXX.XXX:5060;branch=z9hG4bK62E317

From: "Jabber Windows" <sip:+45721XXXXX@213.83.148.132>;tag=5745F70-18E2

To: <sip:+45292XXXXX@62.121.XXX.XX>

Call-ID: E28CBEEB-3AF11E5-8D17E122-602BEEE3@213.XX.XXX.XXX

CSeq: 101 INVITE

Timestamp: 1432735365

Content-Length: 0

 

 

*May 27 14:02:45.990: //3186/3CA341800000/SIP/Msg/ccsipDisplayMsg:

Received:

SIP/2.0 488 Not Acceptable Here

Via: SIP/2.0/TCP 213.XX.XXX.XXX:5060;branch=z9hG4bK62E317

From: "Jabber Windows" <sip:+4572XXXXXX@213.XX.XXX.XXX>;tag=5745F70-18E2

To: <sip:+452XXXXXXX@62.121.XXX.XX>;tag=hjVZ_.7DBhf3h7cA

Call-ID: E28CBEEB-3AF11E5-8D17E122-602BEEE3@213.83.148.132

CSeq: 101 INVITE

Timestamp: 1432735365

Content-Length: 0

Reason: X.int ;reasoncode=0x0000032D;add-info=05CC.0001.0004

 

Best regards

Brian

 
 

1 ACCEPTED SOLUTION

Accepted Solutions
Terry Cheema
Advocate

Brian,

You haven't posted the complete SIP trace, not sure what video attributes you are sending in SDP, but try the below on your CUBE router:

1) Create a SIP Profile to modify the SDP headers in INVITE:

conf t

voice class sip-profiles 999
 request INVITE sdp-header Video-Attribute remove
 request INVITE sdp-header Video-Media modify "m=video(.*)" ""
 request INVITE sdp-header Video-Bandwidth-Info remove

2) Apply this sip-profile to your outgoing dial-peer to your provider

dial-peer voice 9 voip

voice-class sip profiles 999

3) Although I believe above should work but In case, any other attribute is being sent in SDP, you can remove other attribute as well by adding to your SIP profile, if you use question mark (under voice class sip) it will show you all video related attributes.

R01(config-class)#request inviTE sdp-header video-?

Video-Attribute
Video-Bandwidth-Info
Video-Connection-Info
Video-Encryption-Key
Video-Media
Video-Session-Info

 

Let me know how you go.

-Terry

Please rate all helpful posts and mark the thread as answered if you have no other queries.

View solution in original post

14 REPLIES 14
Terry Cheema
Advocate

Brian,

You haven't posted the complete SIP trace, not sure what video attributes you are sending in SDP, but try the below on your CUBE router:

1) Create a SIP Profile to modify the SDP headers in INVITE:

conf t

voice class sip-profiles 999
 request INVITE sdp-header Video-Attribute remove
 request INVITE sdp-header Video-Media modify "m=video(.*)" ""
 request INVITE sdp-header Video-Bandwidth-Info remove

2) Apply this sip-profile to your outgoing dial-peer to your provider

dial-peer voice 9 voip

voice-class sip profiles 999

3) Although I believe above should work but In case, any other attribute is being sent in SDP, you can remove other attribute as well by adding to your SIP profile, if you use question mark (under voice class sip) it will show you all video related attributes.

R01(config-class)#request inviTE sdp-header video-?

Video-Attribute
Video-Bandwidth-Info
Video-Connection-Info
Video-Encryption-Key
Video-Media
Video-Session-Info

 

Let me know how you go.

-Terry

Please rate all helpful posts and mark the thread as answered if you have no other queries.

View solution in original post

Second (and I guess much simpler) way is to use CUCM Regions:

1) CUCM Region:

Create a new region with same Audio configs as per existing one.

In the Region setting, for video calls select the bandwidth "None".

2) Apply this Region to your SIP Trunk (through the Device Pool applied to SIP Trunk)

This was all calls going out via this SIP Trunk will have video disabled. (internal calls will not affected by this)

-Terry

Please rate all helpful posts.
 

Hi,

 

nice idea but so my cube blocks the call.

I removed all video sdp-headers but one line I can not remove:

m=application 18258 RTP/SAVP 125

my itsp always send me "message too large".

I do not want to disable video for all csf's.

Unfurtunately I can not find a forum thread where someone used a script on a dial-peer. Can some tell me how I can implement this:

M = {}


function M.inbound_INVITE(msg)

    local sdp = msg:getSdp()


    if sdp

    then

        sdp = sdp:removeLine("m=", "application")

        msg:setSdp(sdp)

    end

end

I hope this should remove the last line.

this works for me any instate of invite

conf t

voice class sip-profiles 999
 request ANY sdp-header Video-Attribute remove
 request ANY sdp-header Video-Media modify "m=video(.*)" ""
 request ANY sdp-header Video-Bandwidth-Info remove
!


2) Apply this sip-profile to your outgoing dial-peer to your provider and inbound diral-peer which is coming form the carrier

dial-peer voice 9 voip

voice-class sip profiles 999

Hey Terry

 

Thanks this worked for me, I did however need to set the new regions relationship to all other regions in the system to no video.

 

Perfect as the CUBE config did not work for me and my calls still failed.

Hey Mate - Thanks for the update and I am glad that helped you.

-Terry

Please rate all helpful posts
 

Thanks Terry, in our case 911 calls were not going through.  I got the trace from the AT&T tech and looked at the entire call flow.  According to AT&T the video offering in the early offer INVITE SDP was causing the size of the header to increase, and at the distant end the INVITE was being rejected and I was getting a 400 back.  On one of the call legs in the cloud I noticed that the DF bit changed from 0 to 1 on the INVITE which I'm sure is by design but may explain a few things.  Anyway your fix worked and we appreciate it!

Thanks Terry this was very helpful as we faced few issues calling specifically Mitel customers over AT&T SIP trunk.

 

It's worth noting that on my case the  request INVITE sdp-header Video-Media modify "m=video(.*)" "" caused an unexpected outbound calling on one of our voice gateways (2911) with CUCM  getting a 488 Not Acceptable Media, I had to remove it from the config that seems to have helped with both issues.

 

Thanks again.

 

Aomar.

Thanks Terry!

II just applied the commands in the CUBE and it works perfectly!

Thanks a lot for your contribution, that is much appreciated.

Not a problem mate - Glad that helped !!

See you around.

-Terry

Please rate all helpful posts.

CUBE running IOS 15.6(2)T / IOS-XE Denali 16.3.1 or higher supports "Video Suppression" which is a more elegant solution than the previous responses (although was at the time probably not available).

 

This can be enabled globally:

 

voice service voip
 sip
  audio forced

 

Or per Dial-Peer:

dial-peer voice 1 voip
 voice-class sip audio forced
opintainho
Beginner

I think is easier to remove the video options directly from the phone config in CUCM.

The video capability is enabled by default to Jabber phones.

Phone Configuration -> Product Specific Configuration Layout -> Video Calling = Disabled.Video Capability Jabber Phones.png

 

No that would not be the best solution. This will remove the capabilities of the endpoints to do video internally. Using audio forced is the most efficient solution here

Please rate all useful posts

Yah, you're right. Good point of view.

But in my country we usually don't use video at all. And we usually have problems with the carriers because that. So the faster solution is to remove it directaly from devices.

But the best manner to workaround it, is certanly forcing audio to the dial-peers as you sugest, and leave the video capabilities to others options.

We already have here many options and workarounds depending what is better for each cenarium and the needs of each situation.

Good work. Congratulations to everyone!

Content for Community-Ad

Spotlight Awards 2021

This widget could not be displayed.