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

[Gareth Palmer (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-13145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gareth Palmer updated ASTERISK-13145:
-------------------------------------

    Attachment: cisco-usecallmanager-18.6.0.patch
                cisco-usecallmanager-16.20.0.patch

Added patches for 18.6.0 and 16.20.0. Notable updates below:

1. These patches fix an interoperablility issues with firmware versions 12 and greater with the call-ui window not closing after an semi-attended transfer completes and an reorder tone playing. Asterisk usually sends a "603 Declined" for the replaced outgoing inging call-leg, Cisco's documentation says it should be a "487 Request Terminated". The actual response required is a "500 Internal Server Error".

2. Outbound calls that are CANCEL'ed in the ringing state would previously cause a retransmission error due to the phone not including a required To tag in the ACK. Asterisk will not try and expect a valid ACK for this phones.

3. The ActiveLoad and InactiveLoad (for phones that have dual-banks) is now shown in "sip show peer" output.

4. There is a new dial-plan variable CISCO_HUNTGROUP which can be set to contain a caller-ID like string for calls that were sent to the phone as part of a hunt-group. Similiar to setting REDIRECTING() information, that information will be shown in the call-bubble and phone history for phones that support it. Documentation: https://usecallmanager.nz/extensions-conf.html#cisco_huntpilot

Additional non-patch releated updates:

1. I have reverse-engineered the TVS protocol. TVS (Trust Verification Service) allows the phone to query the validity of a certif
icate without having to include that certificate in ITLFile.tlv. Documentation: https://usecallmanager.nz/trust-verification.html

2. I have also reverse-engineered the CAPF protocol. CAPF (Certificate Authentication Proxy Function) allows a service to issue client-side certificates for the phone which can then be used for SIP-TLS and VPN authentication as well as the phone's HTTPS web-server. Documentation: https://usecallmanager.nz/certificate-enrollment.html

3. And I have also, also reverse-engineered the file format of encrypted SEPMAC.cnf.xml.enc.sgn files. The enccnf utility as part of certutils can encrypt SEPMAC.cnf.xml. As it requires also switching to signed configuration files it is probably much easier to just used secure provisioning instead.

4. The /svc endpoint provided by the ocserv VPN patch now supports certificate authentication.


> [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
>            Severity: Major
>              Labels: patch, pjsip
>         Attachments: 00_READ_ME_FIRST.txt, AppDialRules.xml, cisco-usecallmanager-13.38.2.patch, cisco-usecallmanager-16.20.0.patch, cisco-usecallmanager-18.6.0.patch, DialTemplate.xml, FeaturePolicy.xml, SEPMAC.cnf.xml, SoftKeys.xml, usecallmanager-port.sh
>
>
> 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)