[Asterisk-Dev] Potential bug in caller ID setting; comments requested

[John Todd]

I've perhaps found a 'bug' in the routines that set outbound caller 
ID, but I'd like to get comments before I submit an official bug note.

I've slimmed down this demonstration to prove a point; there are 
missing parts of this config that are not relevant.  Just take my 
word on it that calls from my desk phone get to the [fwd] context. 
:-)

----sip.conf----
[fwd]
type=friend
username=123456
secret=nosecretshere
fromdomain=foocorp.com
host=fwd.pulver.com
canreinvite=no
context=default


----extensions.conf-----

[stuff in here deleted for brevity]

[fwd]
exten => _7XX.,1,SetCallerID(John Todd <jtodd>)
exten => _7XX.,3,Dial(SIP/${EXTEN:1}@fwd,,o)
exten => _7XX.,4,Playback(invalid)
exten => _7XX.,5,Hangup
exten => _7XX.,103,Busy
exten => _7XX.,104,Hangup


When I create an outbound call with the above configuration, the 
caller ID that shows up at the other end (and what is placed in the 
SIP INVITE in the From: field) is incorrect, showing "asterisk" as

   From: "John Todd" <sip:asterisk at foocorp.com>;tag=as6dafff3c

However, when I change the SetCallerID line in [fwd] to look like this:

exten => _7XX.,1,SetCallerID(John Todd <2005>)

...then the caller ID (with "jtodd at foocorp.com") shows up correctly 
in the SIP INVITE and on the remote caller ID:

    From: "John Todd" <sip:2005 at foocorp.com>;tag=as26aad33b

The bug?  It seems that SetCallerID will only accept a NUMBER in 
between the <> identifiers.  To follow the spec, it should be 
possible to set a STRING (not just a number) as this value.  I'd like 
to have my caller ID show "John Todd <jtodd at foocorp.com>" as the 
remote caller ID, which is the correct external return path, instead 
of the internal extension number or whatever the other internal 
identifier is inside this particular ITAD.

Am I missing something obvious?  I've been staring at this problem 
too long, so perhaps I'm missing an otherwise obvious solution.  I 
can't change this in sip.conf on the FWD peer, since multiple 
outbound identities are using the same authentication number.  It 
would seem that this is a limitation of the way that caller ID 
numbers are expressed in the routines that set those values.

The tests I've performed are using CVS-HEAD-02/18/05-15:06:57.

JT