Paul,

I wish it was a configuration issue (I am crystal clear on how Caller ID is
supposed to work in sipXecs now).  I have tried EVERY possible configuration
I can think of.  I have deleted the Gateway, added it back... I can not get
the transform or user specific Caller ID to work, it always just spits out
the 4 digit extension.  Can one of the devs help me debug this so I can
submit a bug report?

Thanks,
Roy

On Tue, Jan 4, 2011 at 9:50 PM, Paul Herron <[email protected]> wrote:

> O.k. The only thing I would note is that user caller ID settings and
> transform rules are bypassed if you place your Caller ID string in the field
> indicated in the screen shot that you sent earlier.
>
> Its working on my system - default and user specified settings - with
> Vitelity just fine. Sounds like you may have a configuration issue
> somewhere.
>
>
> ------------------------------
> From: Roy Walker <[email protected]>
> Sent: January 04, 2011 10:06 PM
> To: Paul Herron <[email protected]>
> Cc: [email protected]
> Subject: Re: [sipx-users] Caller-id settings not working
>
> Paul,
>
> Yes the "Default Caller ID" option works.  It is any user or transform
> settings that do not work, which is what I am trying to get working...
>
> Thanks,
> Roy
>
> On Tue, Jan 4, 2011 at 8:55 PM, Paul Herron <[email protected]>wrote:
>
>> Roy –
>>
>>
>>
>> Try putting your caller ID in the “Default Caller ID” field for the
>> gateway and leave all others blank.  I do this on my 4.0.4 installation with
>> Vitelity as my ITSP and it works just fine.  Per line/user caller ID
>> specifications work just fine as well.  I have not used any transform rules.
>>
>>
>>
>>
>> I presume that you have the number you are listing in the caller ID field
>> hosted with/ported to Vitelity.
>>
>>
>>
>> Paul
>>
>>
>>
>> ____________________
>>
>>
>>
>> I was trying to show the relevant section of the log...
>>
>>
>>
>> I don't see how this COULD POSSIBLY be an issue with the ITSP (in this
>> case Vitelity).  I have turned off Caller ID settings on EVERYTHING but the
>> user account.  Which is set to 2148916102.  I got 16102 on the receiving
>> end... exactly what was sent to the ITSP.
>>
>>
>>
>> Attached is the segment of the sipxbridge.log from the moment before I
>> call to a few seconds after the call is hung up.
>>
>>
>>
>> Roy
>>
>>
>>
>>
>>
>
>
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to