Posted: Wed Apr 09, 2003 4:13 pm Post subject: [Asterisk-Dev] Re: PATCH: Ability to override "From" for cal
already fixed the sense problem this morning. Does "setcallerid" and
"fromdomain" combined not set the ability to totally override on the
calls?
Mark
On Wed, 9 Apr 2003, Stephen Davies wrote:
Quote:
Hi Mark,
With this patch I'm able to make PSTN calls via Packet8. The patch adds a
"from=" for SIP peers, allowing you to specifically set the From header to
be used on calls out to that peer.
When calls go out to Packet8 this is the From header that will be
used. Including the right magic number in the SIP URI seems to be enough
authentication for them. (so I'll keep my magic number to myself...)
I think this will be useful with other providers too. I'll test
iConnectHere this evening.
By the way - Packet8 advertises that it is G723.1 only - but in fact for
outgoing (to PSTN) calls it will do G711 too. For inbound (from
PSTN) calls their gateway wants only G723.1 from us.
This patch also fixes the sense of the inaddrcmp test, and adds what I
think are useful and important debug messages showing where users and
peers are matched for calls.
Posted: Wed Apr 09, 2003 4:52 pm Post subject: [Asterisk-Dev] Re: PATCH: Ability to override "From" for cal
On Wed, 9 Apr 2003, Mark Spencer wrote:
Quote:
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@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.
-----Original Message-----
From: asterisk-dev-admin@lists.digium.com
[mailto:asterisk-dev-admin@lists.digium.com] On Behalf Of Stephen Davies
Sent: 09 April 2003 5:52 PM
To: asterisk-dev@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:
Quote:
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@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.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum