<![CDATA[Caller ID on inbound calls shows destination, not source]]>Hi there,

I have installed FOP2 on Trixbox CE 1.8.

When there is an inbound call to my extension, I get a little popup on my screen. It also shows up in the extension button. The problem is, it doesn't display the Caller ID; rather it displays the destination of my call. If I do a Direct-Dial, it shows the extension that I am calling; if I call a Ring Group, it shows that ring group's number.

Once the call connects, the correct Caller ID is displayed.

Does anyone know how to make the correct Caller ID display before the call is connected?

Thanks,

]]>http://localhost:4567/topic/263/caller-id-on-inbound-calls-shows-destination-not-sourceRSS for NodeTue, 27 Oct 2026 07:01:57 GMTSun, 21 Feb 2010 07:41:23 GMT60<![CDATA[Reply to Caller ID on inbound calls shows destination, not source on Tue, 23 Feb 2010 10:29:04 GMT]]>Hi,

Callerid is totally uneven, behavior changed in Asterisk since version 0.5. Unfortunately it is not that easy to pick the callerid based on manager events. You saw it yourself when calling directly and not a ringroup.

From the capture you send, it seems that asterisk is informing 600 as the NewCallerid event for SIP/7427, right? So Asterisk is telling that the new callerid for SIP/7427 is 600.

There are certain events that set the callerid in a fop2 button. It is not fixed but contextual and changes if the button is a trunk or an extension. The basic rule of thumb is to set the callerid if it was not previously set or if was empty on a NEWSTATE event.

So you can run a full trace with debug level set to 1 for one of those calls and send it to me privately (it will be kind of log and with potential private data) with a description: call from trunk XXX to ring group YYY that rung extension ZZZ and displayed callerid 0000 instead of 1111.

Best regards,

]]>http://localhost:4567/post/1233http://localhost:4567/post/1233Tue, 23 Feb 2010 10:29:04 GMT<![CDATA[Reply to Caller ID on inbound calls shows destination, not source on Tue, 23 Feb 2010 07:14:26 GMT]]>Yes, I'm sorry, I actually mistyped the version number in my original post; it is 2.8.0.3; the most recent one (and based on Asterisk 1.6).

The odd thing is that I ran the fop2 server in debug/verbose mode and captured the following:

On the trunk:

127.0.0.1       <- Event: NewCallerid
127.0.0.1       <- Privilege: call,all
127.0.0.1       <- Channel: SIP/EMIS-ntt1-000000cc
127.0.0.1       <- CallerIDNum: 090xxxxxxxx
127.0.0.1       <- CallerIDName: awh Mobile
127.0.0.1       <- Uniqueid: 1266823128.213
127.0.0.1       <- CID-CallingPres: 0 (Presentation Allowed, Not Screened)
127.0.0.1       <- Server: 0

But on the extension:

127.0.0.1       <- Event: NewCallerid
127.0.0.1       <- Privilege: call,all
127.0.0.1       <- Channel: SIP/7427-000000ce
127.0.0.1       <- CallerIDNum: 600
127.0.0.1       <- CallerIDName:
127.0.0.1       <- Uniqueid: 1266823129.215
127.0.0.1       <- CID-CallingPres: 0 (Presentation Allowed, Not Screened)
127.0.0.1       <- Server: 0

"600" is the name of the ring group. If I call an extension directly (IE, a DID that does not use Ring Groups) it would say something like <- CallerIDNum: 7427

You can see that the right CallerIDNum and CallerIDName is on the trunk. Also, the actual CID displays on the handset show the correct thing; it's only FOP that is picking up this "600" from somewhere...

]]>http://localhost:4567/post/1232http://localhost:4567/post/1232Tue, 23 Feb 2010 07:14:26 GMT<![CDATA[Reply to Caller ID on inbound calls shows destination, not source on Mon, 22 Feb 2010 18:41:56 GMT]]>Hello,

Is that a recent trixbox version?

]]>http://localhost:4567/post/1231http://localhost:4567/post/1231Mon, 22 Feb 2010 18:41:56 GMT