Summary:	ASTERISK-06432: SetCallerID and SetCallerPres will be ignored if Caller Leg is a CAPI call
Reporter:	chotaire (chotaire)	Labels:
Date Opened:	2006-02-27 11:14:40.000-0600	Date Closed:	2011-06-07 14:03:23
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_local
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	This is not a chan_capi issue! SetCallerID and SetCallerPres will be completely ignored, even if doing a SIP call, if the Caller Leg is a CAPI call.. let me demonstrate.. caller id will not be displayed (as intended):    -- Executing SetCallerID("SIP/soft-f876", "Anonymous") in new stack    -- Executing Dial("SIP/soft-f876", "SIP/021xxxxxx@sip.xxxxxx.de|60|Tg") in new stack the isdn caller id (which is to be hidden) will be displayed (not intended):    -- Executing SetCallerID("CAPI/ISDN1/55xxxx-0", "Anonymous") in new stack    -- Executing SetCallerPres("CAPI/ISDN1/55xxxx-0", "prohib_not_screened") in new stack    -- Executing Dial("CAPI/ISDN1/55xxxx-0", "SIP/021xxxxxx@sip.xxxxxx.de|30|hHtr") in new stack I tried all different possibilities... with |a (override ANI), with new and old SetCallerID format, with and without SetCallerPres, it does not help at all. If calling a local SIP client, it will display the caller ID "Unknown", not even "Anonymous". No matter what I set, it will stay "Unknown". If calling a PSTN number over my SIP provider, it will display the SIP number (absolutely not intended). If calling over CAPI, it will display my CID (absolutely not intended and prohibited by SetCallerPres). All settings will be ignored. So I assume that the SetCallerID and SetCallerPres setting is completely ignored if the originating caller is coming over CAPI, which I consider an asterisk issue since chan_capi does not do sip calls ;) Happy testing and fixing.
Comments:	By: chotaire (chotaire) 2006-02-27 12:24:06.000-0600 Reported bug at chan_capi-cm project site too: http://sourceforge.net/tracker/index.php?func=detail&aid=1439841&group_id=140312&atid=746578 By: Russell Bryant (russell) 2006-02-27 12:38:19.000-0600 As I discussed with you on IRC, I am going to suspend this until you can demonstrate a problem that does *not* involve the use of chan_capi.  Thanks.