asterisk users - Sep 2008 - sip forking needed for ekiga 3.0

So, I have been testing ekiga 3.0 with Asterisk, and sadly, it don't
work.  I am told by the ekiga devs in
http://bugzilla.gnome.org/show_bug.cgi?id=553595 and
http://bugzilla.gnome.org/show_bug.cgi?id=553810 that the problem is
that Asterisk does not support SIP forking.

The issue is that I have multiple addresses on my workstation:

2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
    inet 10.75.22.1/24 brd 10.75.22.255 scope global eth0
    inet 10.75.22.101/24 brd 10.75.22.255 scope global secondary eth0:1

So when ekiga (3.0) tries to place a call through Asterisk it in fact
does parallel requests from all addresses.  This is what appears to
confuse Asterisk.  Please see the above tickets for more details.

Thots?

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20080925/461ed71d/attachment.pgp

My thoughts are that to do parallel requests from every IP address on
the machine is extremely weird behaviour.

How would any server know which to respond to?

SIP forking is supposed to send requests to multiple different
destinations (or fork mid-stream to send to different destinations). 
Sending from multiple different points of origin doesn't make any sense
at all in either a logical or rational fashion. What's it supposed to
accomplish?

N.

Brian J. Murrell wrote:
> So, I have been testing ekiga 3.0 with Asterisk, and sadly, it don't
> work.  I am told by the ekiga devs in
> http://bugzilla.gnome.org/show_bug.cgi?id=553595 and
> http://bugzilla.gnome.org/show_bug.cgi?id=553810 that the problem is
> that Asterisk does not support SIP forking.
>
> The issue is that I have multiple addresses on my workstation:
>
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
qlen 1000
>     link/ether xx:xx:xx:xx:xx:xx brd ff:ff:ff:ff:ff:ff
>     inet 10.75.22.1/24 brd 10.75.22.255 scope global eth0
>     inet 10.75.22.101/24 brd 10.75.22.255 scope global secondary eth0:1
>
> So when ekiga (3.0) tries to place a call through Asterisk it in fact
> does parallel requests from all addresses.  This is what appears to
> confuse Asterisk.  Please see the above tickets for more details.
>
> Thots?
>
> b.
>
>   
> ------------------------------------------------------------------------
>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> AstriCon 2008 - September 22 - 25 Phoenix, Arizona
> Register Now: http://www.astricon.net
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users

Brian J. Murrell wrote:
> On Fri, 2008-09-26 at 10:16 -0400, SIP wrote:
>> The RFCs are there for a reason. All SIP forking is UAS territory. Not
>> UAC territory.
> 
> From http://bugzilla.gnome.org/show_bug.cgi?id=553810 Damien Sandras
> asks:
> 
>         I repeat, Ekiga is doing something perfectly legal.
>         
>         The real question is why does Asterisk think it is the same request
when the
>         from tag is different ?
> 
> b.
> 
Asterisk ignores tags in To and From headers unless you have
"pedantic=yes" set
in sip.conf.

Mark Michelson