[Asterisk-Dev] Re: PATCH: Ability to override "From" for calls to a peer, also fix inaddrcmp sense

[James Dennis]

To add to my last mail. On the subject of SetCallerID, this works fine with
my service provider who do check the caller id information:

[fwd]
exten => _91NXXNXXXXXX,1,SetCallerID(12345678)
exten => _91NXXNXXXXXX,2,Dial(SIP/${EXTEN:1}@fwd)
exten => _91NXXNXXXXXX,3,Congestion

-----Original Message-----
From: asterisk-dev-admin at lists.digium.com
[mailto:asterisk-dev-admin at lists.digium.com] On Behalf Of Stephen Davies
Sent: 09 April 2003 5:52 PM
To: asterisk-dev at lists.digium.com
Subject: Re: [Asterisk-Dev] Re: PATCH: Ability to override "From" for calls
to a peer, also fix inaddrcmp sense




On Wed, 9 Apr 2003, Mark Spencer wrote:

> already fixed the sense problem this morning.  Does "setcallerid" and 
> "fromdomain" combined not set the ability to totally override on the 
> calls?

Thought you'd ask that - and no - or at least not as things are now.

Firstly - "callerid" is an attribute for a user, not a peer.

Secondly - "fromdomain" can only really be used for "synonyms" for the
Asterisk machine.  This is because the port part of the generated URI is
left the same.

IE, imagine Asterisk running on port 5062. When calling a peer with
fromdomain=packet8.net, Asterisk will make a URI
<sip:asterisk at fwd.pulver.com:5062>  Which isn't the desired effect.

Instead of adding the from= we could instead:

 - Add callerid as an attribute for a peer
 - Fix fromdomain so that "ourport" is no longer used when fromdomain is
   present

I wasn't sure why fromdomain= was added so didn't just want to change its
behaviour.

And adding callerid as an attribute for a peer causes trouble for
"type=friend" - the same callerid doesn't make sense as the call origin for
both inbound and outbound calls.

Steve


_______________________________________________
Asterisk-Dev mailing list
Asterisk-Dev at lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-dev