jgibson wrote:
Can you see the cid info being sent from your elastix box when you make a call? I think you need to ssh into you box and then get to the asterisk cli using "asterisk -rvvvv". There is a macro called outbound-callerid. Can you post what information is next to those lines?

sure



it looks as if it is being sent.

Here is a incoming call:



Here it looks like asterisk isnt getting the caller id sent to it...

-bump-

I believe that replacing your CID

<262-384-4903>
with
<2623844903>
might help
or
<12623844903>
as your provider seems to be sending you all 11 digits

I've been on vacation for a week and I've gotten a little confused about what you need. Do you need everyone to use the same outbound CID or do you want each extension to have there own.

I also agree with dicko that changing your number to get rid of the - may help.

dicko wrote:
I believe that replacing your CID

<262-384-4903>
with
<2623844903>
might help

thanx ill give it a try!

jgibson wrote:
Do you need everyone to use the same outbound CID or do you want each extension to have there own.

yeah every one should be using the same CID.

ok and it goes on. After hours of looking around and searching for little signs of things going wrong i have found this. i have line 1 "line1" and line 2 "line2". When someone calls in they get the irv from which you goto what ever extension, you only get the ivr when you dial into line1. if you call in to line2 you go right to me. now when i have callerid set in the PEER details of trunk line2 any call coming into line1 displays line2 cid. cid dont work at all for calls coming into line2. In the cdr reports i see each phone is getting two calls, one is the real call then a second one shows up for 0 seconds and dont get answered:



not sure where to go from here.

to fix the cdr issues, go to /etc/asterisk/extensions.conf

and find the following section:






and edit it, so it will look like this:


as you will see, that will comment the first two lines of the context, and the next line will have the priority 1, instead of n

save the file and exit, the on the sheel execute the following command:

asterisk -rx "reload"

jgutierrez wrote:
to fix the cdr issues, go to /etc/asterisk/extensions.conf

and find the following section:

Código:

[macro-hangupcall] exten => s,1,ResetCDR(w) exten => s,n,NoCDR() ; Cleanup any remaining RG flag ; exten => s,n,GotoIf($[ "x${USE_CONFIRMATION}" = "x" | "x${RINGGROUP_INDEX}" = "x" | "${CHANNEL}" != "${UNIQCHAN}"]?skiprg) exten => s,n,Noop(Cleaning Up Confirmation Flag: RG/${RINGGROUP_INDEX}/${CHANNEL}) exten => s,n,DBDel(RG/${RINGGROUP_INDEX}/${CHANNEL})

and edit it, so it will look like this:

Código:

[macro-hangupcall] ;exten => s,1,ResetCDR(w) ;exten => s,n,NoCDR() ; Cleanup any remaining RG flag ; exten => s,1,GotoIf($[ "x${USE_CONFIRMATION}" = "x" | "x${RINGGROUP_INDEX}" = "x" | "${CHANNEL}" != "${UNIQCHAN}"]?skiprg) exten => s,n,Noop(Cleaning Up Confirmation Flag: RG/${RINGGROUP_INDEX}/${CHANNEL}) exten => s,n,DBDel(RG/${RINGGROUP_INDEX}/${CHANNEL})

as you will see, that will comment the first two lines of the context, and the next line will have the priority 1, instead of n

save the file and exit, the on the sheel execute the following command:

asterisk -rx "reload"

thanx man, that did fix the CDR reports issue, now i just have to figer out this damned caller id thing!

Ok here is more info on my issue. Something i didnt notice, it seems that calls coming in on line1 "the line that IVR picks up", are getting displayed as source channel line2 in CDR reports. It should be showing line1, line1 was the one being called.