Ticket #4145 (closed Bugs: invalid)

Opened 2 years ago

Last modified 2 years ago

Outbound CallerID gets lost on calls originating from Asterisk Call Manager

Reported by: dsdee Assigned to: p_lindheimer
Priority: minor Milestone: 2.8
Component: Core Version: 2.6-branch
Keywords: callerid, call manager Cc:
Confirmation: Unreviewed SVN Revision (if applicable):
Backend Engine: Asterisk 1.6 Backend Engine Version:

Description

For some reason, I thought this was going to be covered under the #4100 ticket, so I didn't press-ahead with saying something about it last week... But looking back, I'm not sure where I got that idea.

I have a web gui that uses an Asterisk Call Manager connection to my PBX to initiate a call from my desk-phone to an outside line. The call first initiates a connection to my desk-phone, x200, and then dials the destination phone, which i'll reference below as 303-222-2222, with the caller-ID showing up on the far-side as 303-111-1111. At least it used to show up that way; it no longer shows up that way though. My VOIP provider also shows no caller-id data being passed to them for the call.

This was working fine, up through I believe core 2.7.0.1, but it may've only been working thru 2.7.0.0.

The Call Manager call is as follows: 

Sending:
Action: Originate
Channel: SIP/200
Exten: 3032222222
Context: from-internal
Priority: 1
CallerID: 3031111111
Async: yes

I'm also seeing the same behavior if I use DISA to dial out on my main line, using that to change the source caller-id: 

extensions_custom.conf:exten => 1111,1,Answer
extensions_custom.conf:exten => 1111,n,DISA(no-password,from-internal,3031111111)

I will attach the log output in a few minutes.

Freepbx is up to date as of this morning. Asterisk is v1.6.2

Attachments

asterisk-logs.txt (30.3 kB) - added by dsdee on 03/17/10 08:55:59.
Log file demonstrating two calls with OB-CID disappearing

Change History

03/17/10 08:55:59 changed by dsdee

  • attachment asterisk-logs.txt added.

Log file demonstrating two calls with OB-CID disappearing

(follow-up: ↓ 2 ) 03/17/10 09:29:33 changed by p_lindheimer

  • status changed from new to closed.
  • resolution set to invalid.

looks like you have no trunk CID set and in the case of DISA no DISA cid set. If that is not the case with DISA then file a separate bug for DISA but this bug I'm closing as invalid as it is a "custom" case and not FreePBX.

You problem is related to the fact that you have no fallback CID set for your trunk. If you want the extension's outbound CID used then you should set the CID in your manager call to the extension's CID to pick it up. If you want to "spoof" the CID, you need to set KEEPCID=YES (I think, would have to go check that).

(in reply to: ↑ 1 ) 03/17/10 23:00:15 changed by dsdee

Replying to p_lindheimer:

looks like you have no trunk CID set and in the case of DISA no DISA cid set. If that is not the case with DISA then file a separate bug for DISA but this bug I'm closing as invalid as it is a "custom" case and not FreePBX. You problem is related to the fact that you have no fallback CID set for your trunk. If you want the extension's outbound CID used then you should set the CID in your manager call to the extension's CID to pick it up. If you want to "spoof" the CID, you need to set KEEPCID=YES (I think, would have to go check that).

Hello;

You are correct in that I had no trunk CID set for the trunk. However, when I set a CID for the trunk, and have the "CID Options" set to "Any", (corresponds to OUTKEEPCID_6="off"), macro-outbound-callerid still jumps, on line 3, to the "normcid" target because KEEPCID is not set to TRUE.

I am able to get around this on on my DISA calls, because it is a dialplan that kicks off the DISA() call, and I can put a Set(KEEPCID=TRUE) before it in order to prevent this from happening.

BUT, for the Asterisk Call Manager call, there is no dialplan executed (other than the dialing), so there is nowhere to stick a Set(KEEPCID=TRUE) in there... or am I approaching the call manager method incorrect for Asterisk 1.6.2.

Or, with this version of Asterisk/Freepbx, is it more "appropriate" for me to set up a different Trunk for each DID that I have (and therefore would want as outbound CIDs) and set the outbound CID on the Trunk? Or a different Outbound Route for each CID I might want to appear on outbound calls?? -- I don't think so, because the config would get too excessive, too quickly.

You said that this was an invalid request as it was a "custom" case, but, I guess I would want to ask why Originating a call through the Call Manager would fall under not-FreePBX, since it goes thru the FreePBX dialplans??

Thanks in advance,

03/18/10 01:43:06 changed by p_lindheimer

It's marked invalid because it is not a broken FreePBX feature. I guess I could mark it as worksforme as it works like it is suppose to (and has not changed).

concerning:

BUT, for the Asterisk Call Manager call, there is no dialplan executed (other than the dialing), so there is nowhere to stick a Set(KEEPCID=TRUE) in there... or am I approaching the call manager method incorrect for Asterisk 1.6.2.

try setting the variable in your originate command, I assume 1.6.2 still supports that:

http://www.voip-info.org/wiki/view/Asterisk+Manager+API+Action+Originate