[asterisk-bugs] [Asterisk 0008824]: [patch] Remote (called) Party Identification - chan_sip & chan_skinny implementation
noreply at bugs.digium.com
noreply at bugs.digium.com
Wed Jan 16 04:49:57 CST 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=8824
======================================================================
Reported By: gareth
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 8824
Category: Core/General
Reproducibility: N/A
Severity: feature
Priority: normal
Status: ready for testing
Asterisk Version: SVN
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 59043
Disclaimer on File?: Yes
Request Review:
======================================================================
Date Submitted: 01-15-2007 18:18 CST
Last Modified: 01-16-2008 04:49 CST
======================================================================
Summary: [patch] Remote (called) Party Identification -
chan_sip & chan_skinny implementation
Description:
Overview:
This patch provides the ability to rewrite the called party information
on
channel types that support it. Implementations for the SIP (see note
http://bugs.digium.com/view.php?id=1)
and Skinny (see note http://bugs.digium.com/view.php?id=2) channels have been
provided.
Current features are:
1. Make changes whilst the call is progessing though the dial plan, ie:
exten => s,1,RemoteParty("Voicemail" <123>)
exten => s,n,Answer()
exten => s,n,VoiceMailMain()
2. When using call pickup it will rewrite the caller information showing
the caller that was picked up.
3. When unparking a call it will show the caller*id of the parked call.
The ability to rewrite the calling party identification on semi-attended
transfer is planned but doesn't work yet.
Implementation:
Transmission of the remote party data is done using indications with a
new
subtype of AST_CONTROL_REMOTEPARTY, format of the data is:
"name" <number>|presentation
Any channel specific code is kept in it's _indicate() handler. Once the
channel driver has received the indication it uses the method specific to
it; in the case of SIP it sends a 180/183 response if possible and with
Skinny it uses transmit_callinfo().
Note http://bugs.digium.com/view.php?id=1: The SIP implemenation is only able to
update the remote party
before the call has been answered as there is no re-invite support yet.
Note http://bugs.digium.com/view.php?id=2: I don't have any Skinny phones so no
testing has been done on
that part.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0006643 [patch] Implement Called Party Identifi...
has duplicate 0008990 Transfer and Variables
related to 0011036 Crush at unknown place
======================================================================
----------------------------------------------------------------------
gareth - 01-16-08 04:49
----------------------------------------------------------------------
billhackensack: Please submit a patch to remove all video support from
asterisk as it won't work with my Zap/FXS analogue phone.
The bulk of the patch is device independent, however that does not
guarantee that every channel type can be supported.
As asinine as your comments are, they have prompted me to produce the list
of other channel types I investigated:
chan_alsa & chan_oss: Trivial to have it print a message.
chan_mgcp: Was not able to get a Cisco 7940 running 7.7.0 MGCP load.
chan_unistim: Send_Text() function could be used. Don't have UNISTIM
phone to test.
chan_zap: PRI interfaces might be able to use FACILITY messages as a
transport.
Patches have been updated for 1.4.17 and SVN/98603.
Issue History
Date Modified Username Field Change
======================================================================
01-16-08 04:49 gareth Note Added: 0080746
======================================================================
More information about the asterisk-bugs
mailing list