[asterisk-bugs] [JIRA] (ASTERISK-13145) [patch] Presence subscription on Cisco SIP phone needs special Cisco-styled XML

Wed May 23 02:11:59 CDT 2018

    [ https://issues.asterisk.org/jira/browse/ASTERISK-13145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243505#comment-243505 ] 

Akh edited comment on ASTERISK-13145 at 5/23/18 2:11 AM:
---------------------------------------------------------

Hi to All
about video resolution 
after version 13.18.0 we see that it is no fixed parameter of video resolution between phone,

as result, 89xx phone send 4:3 resolution, and 99xx send wide resolution (default for them)

side effect of this when two 99xx phone establish video connection - both show video with black stripes

this (video agreement between phone and CUM) described here

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/9_1_1/ccmsys/CUCM_BK_C5565591_00_cucm-system-guide-91/CUCM_BK_C5565591_00_cucm-system-guide-91_chapter_0101100.html

"
Video Resolution Support for SIP Phones
Cisco Unified Communications Manager supports the imageattr line in the SDP portion of the SIP header for higher resolution video calls. Cisco SIP phones that support w360p (640 x 360), such as the 9951, 9971, and 8961, automatically select the best resolution for video calls depending on the following criteria:

   - If the session level bandwidth is greater than 800Kb/s and the imageattr[640 x 480] line in the SDP exists, then VGA is used.

  -  If the session level bandwidth is greater than 800Kb/s and the imageattr[640 x 480] line in the SDP does not exist, then w360p is used.

  -  If the session level bandwidth is less than 800Kb/s but greater than 480 bits per second and the imageattr[640 x 480] line exists, then VGA 15 frames per second is used.

Note	

If you currently have a Cisco IP Phone model 9951, 9971, or 8961 that supports w360p (640 x 360) video resolution and are upgrading to Cisco Unified Communications Manager release 8.5(1) or later, you may notice changes in the resolution of video calls. The w360p resolution was introduced at phone load 9.2(1).
The following video call flow is between two 9951 phones (Phone A and Phone B) without imageattr line support (for example, using Cisco Unified Communications Manager releases 8.0(1) and earlier):

  -  Phone A sends a SIP message with an imageattr line in the SDP.

   - Cisco Unified Communications Manager deletes the imageattr line in the SDP and then sends the modified SIP message to Phone B.

   - Phone B attempts to send video with the w360p resolution because there is no imageattr line in the SDP portion of the SIP header.

The following video call flow is between two 9951 phones (Phone A and Phone B) with imageattr line support (for example, using Cisco Unified Communications Manager releases 8.5(1) and later):

   - Phone A sends a SIP message with the imageattr line in the SDP.

   - Cisco Unified Communications Manager does not delete the imageattr line and sends the SIP message to Phone B unchanged.

   - Phone B attempts to send video with the VGA resolution.
"

=====
i can't comment why this was done after 13.18.0 
but we made small patch to return back "a=imageattr:%d recv [x=640,y=480,q=0.50]\r\n"
after - no black stripes

( over-cisco-usecallmanager-13.20.0.patch.diff) in files...

may be will be good idea to have a possibility to control somehow video resolution behavior in next release

was (Author: akh1):
Hi to All
about video resolution 
after version 13.18.0 we see that it is no fixed parameter of video resolution between phone,

as result, 89xx phone send 4:3 resolution, and 99xx send wide resolution (default for them)

side effect of this when two 99xx phone establish video connection - both show video with black stripes

this (video agreement between phone and CUM) described here

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/9_1_1/ccmsys/CUCM_BK_C5565591_00_cucm-system-guide-91/CUCM_BK_C5565591_00_cucm-system-guide-91_chapter_0101100.html

"
Video Resolution Support for SIP Phones
Cisco Unified Communications Manager supports the imageattr line in the SDP portion of the SIP header for higher resolution video calls. Cisco SIP phones that support w360p (640 x 360), such as the 9951, 9971, and 8961, automatically select the best resolution for video calls depending on the following criteria:

   - If the session level bandwidth is greater than 800Kb/s and the imageattr[640 x 480] line in the SDP exists, then VGA is used.

  -  If the session level bandwidth is greater than 800Kb/s and the imageattr[640 x 480] line in the SDP does not exist, then w360p is used.

  -  If the session level bandwidth is less than 800Kb/s but greater than 480 bits per second and the imageattr[640 x 480] line exists, then VGA 15 frames per second is used.

Note	

If you currently have a Cisco IP Phone model 9951, 9971, or 8961 that supports w360p (640 x 360) video resolution and are upgrading to Cisco Unified Communications Manager release 8.5(1) or later, you may notice changes in the resolution of video calls. The w360p resolution was introduced at phone load 9.2(1).
The following video call flow is between two 9951 phones (Phone A and Phone B) without imageattr line support (for example, using Cisco Unified Communications Manager releases 8.0(1) and earlier):

  -  Phone A sends a SIP message with an imageattr line in the SDP.

   - Cisco Unified Communications Manager deletes the imageattr line in the SDP and then sends the modified SIP message to Phone B.

   - Phone B attempts to send video with the w360p resolution because there is no imageattr line in the SDP portion of the SIP header.

The following video call flow is between two 9951 phones (Phone A and Phone B) with imageattr line support (for example, using Cisco Unified Communications Manager releases 8.5(1) and later):

   - Phone A sends a SIP message with the imageattr line in the SDP.

   - Cisco Unified Communications Manager does not delete the imageattr line and sends the SIP message to Phone B unchanged.

   - Phone B attempts to send video with the VGA resolution.
"

=====
i can't comment why this was done after 13.18.0 
but we made small patch to return back "a=imageattr:%d recv [x=640,y=480,q=0.50]\r\n"
after - no black stripes

may be will be good idea to have a possibility to control somehow video resolution behavior in next release

> [patch] Presence subscription on Cisco SIP phone needs special Cisco-styled XML
> -------------------------------------------------------------------------------
>
>                 Key: ASTERISK-13145
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-13145
>             Project: Asterisk
>          Issue Type: New Feature
>          Components: Channels/chan_sip/NewFeature
>            Reporter: Gareth Palmer
>            Assignee: Gareth Palmer
>              Labels: patch, pjsip
>         Attachments: 00_READ_ME_FIRST.txt, AppDialRules.xml, cisco-usecallmanager-13.17.0.patch, cisco-usecallmanager-13.18.0.patch, cisco-usecallmanager-13.19.0.patch, cisco-usecallmanager-13.20.0.patch, DialTemplate.xml, FeaturePolicy.xml, over-cisco-usecallmanager-13.20.0.patch.diff, SEPMAC.cnf.xml, SoftKeys.xml
>
>
> This patch provides support for Cisco 6900, 7900, 8800 and 9900 series phones using the SIP firmware.
> Available features are: Busy Lamp Field, Off Hook Notification, Call Forward, Do Not Disturb, Huntgroup Login, Call Park (Notify and Monitor), Server-Side Ad-Hoc Conference, Conference List, Kick and Mute/Unmute, Multi-Admin Conference, Multiple Lines via Bulk Register, Immediate Divert, Call Recording, Restart or Reset via CLI, Call Pickup Notification, Call Back, Join Calls, Mallicious Call ID, Quality Reporting Tool and Fail-over/Fail-back.
> Also included is Application Server Events used by non-USECALLMANAGER phones (Call Forward and Do Not Disturb only).
> *Important:* Read the documentation at [http://usecallmanager.nz] to see the additional configuration options required for the phones to operate correctly.

--
This message was sent by Atlassian JIRA
(v6.2#6252)