callerid passed to Asterisk PBX via IAX

[cbsys]

Hi,
we are running go-autodial 64-bit on centos 5.8
VERSION: 2.4-309a
BUILD: 110430-1642

The dialler has an IAX trunk, which links it to an Asterisk 1.8 PBX
This enables us to forward calls from the dialler over to a queue on the Asterisk PBX, and this works very well.

However, the callerID doesnt seem to go across
The callerID displayed on the Asterisk PBX is not the CLI of the person called, it is the caller code as appears in the call_log Mysql table.
For example, if 9442085680271 is called on the dialler, when the call is passed through to the asterisk box, the CLI appears there as V9290927520000516915

How do we ensure that the correct number is being passed to the Asterisk PBX, rather than the caller code??

[striker]

try the below in the iax peer settings in both the server
callerid=asreceived
hidecallerid=no

[cbsys]

Unfortunately that has no effect whatsoever!

[williamconley]

the path of the call is very important and the way the call was generated.

there are several types of calls possible: Inbound and outbound, of course, are treated differently. And both of these have their own paths and subgroups: Inbound can go through a DID to an external extension or through an IVR to an Ingroup to a remote agent which may be an extension. Outbound can be an autodialed campaign call or a manually dialed call or a 3rd party transfer.

So it would be very helpful if you were to describe in a bit more detail what the path/type of call is being sent to the other system.

Also: In many cases it works to simply NOT use a Vicidial-enabled dialplan to transfer the call to the other asterisk machine. Basically just leaving off the line with the agi script may cause the CID to remain unchanged. (But based on the scenarios above, the call may not yet have the information you want ... in which case you must use a method that will cause Vicidial to add this information ... in which case we'll need to know that pathway ...).