Thanks! nua_create() with NUTAG_URL("sip:192.168.15.115") certainly resolved
that scenario, but presents me with another challenge.
I want to receive SIP traffic on both of my Ethernet interfaces, eth0
(172.16.xx.xx) and eth1(192.168.xx.xx). I was using NUATAG_URL("0.0.0.0") in my
nua_create() believing that one instance of Sofia could receive SIP traffic
from any of my network interfaces, which I think it valid. However, my previous
transmit problem arose. Do you believe I need to create multiple instances of
Sofia to have the best of both worlds? Ie. nua_create(NUTAG_URL(172.16.xx.xx))
and nua_create(NUTAG_URL(192.168.xx.xx))? Will that work with Sofia?
-Dave R
-----Original Message-----
From: [email protected]
[mailto:[email protected]]
Sent: Thursday, February 05, 2009 12:57 PM
To: [email protected]
Subject: Sofia-sip-devel Digest, Vol 33, Issue 3
Send Sofia-sip-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Sofia-sip-devel digest..."
Today's Topics:
1. Re: Question on adding code to NTA for MS OCS SRV resolution
(Pekka Pessi)
2. Re: Question on adding code to NTA for MS OCS SRV resolution
(Andrew Rechenberg Lists)
3. Re: Multiple WWW-Authenticate headers and comparing au_scheme
(Andrew Rechenberg Lists)
4. Multiple ethernet interface support? (Rostowsky, David)
5. Re: Multiple WWW-Authenticate headers andcomparing au_scheme
(Andrew Rechenberg Lists)
6. Re: Multiple ethernet interface support? (Andrew Rechenberg Lists)
----------------------------------------------------------------------
Message: 1
Date: Thu, 5 Feb 2009 14:35:09 +0200
From: Pekka Pessi <[email protected]>
Subject: Re: [Sofia-sip-devel] Question on adding code to NTA for MS
OCS SRV resolution
To: Andrew Rechenberg Lists <[email protected]>
Cc: [email protected]
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
2009/1/29 Andrew Rechenberg Lists <[email protected]>:
> I'm wondering how I should add this code to Sofia. I think I should be
> adding it to nta.c in const sip_dnstports[] and possibly in
> tports_sips[].
>
> Anywhere else I need to add code? Any suggestions on what I should add?
> Can I add things like:
>
> { "tls-ms-i", "5061", "_sipinternaltls._tcp.", "SIPS+D2T" }
>
> Or should I just add another "tls" entry with the _sipinternaltls
> portion?
I think another "tls" entry is fine. Unless MS has embraced and
extended TLS, too? Do they use different transport parameter in URLs
or is it just "tls"?
--
Pekka.Pessi mail at nokia.com
------------------------------
Message: 2
Date: Thu, 5 Feb 2009 09:09:18 -0500
From: "Andrew Rechenberg Lists" <[email protected]>
Subject: Re: [Sofia-sip-devel] Question on adding code to NTA for MS
OCS SRV resolution
To: "Pekka Pessi" <[email protected]>
Cc: [email protected]
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
> > I'm wondering how I should add this code to Sofia. I think I should
> be
> > adding it to nta.c in const sip_dnstports[] and possibly in
> > tports_sips[].
> >
> > Anywhere else I need to add code? Any suggestions on what I should
> add?
> > Can I add things like:
> >
> > { "tls-ms-i", "5061", "_sipinternaltls._tcp.", "SIPS+D2T" }
> >
> > Or should I just add another "tls" entry with the _sipinternaltls
> > portion?
>
> I think another "tls" entry is fine. Unless MS has embraced and
> extended TLS, too? Do they use different transport parameter in URLs
> or is it just "tls"?
>
No embracing and extending as far as I know :).
Here are some typical Via and Contact headers in a SIP conversation
between Office Communicator client and OCS 2007 server:
Via: SIP/2.0/tls 192.168.43.1:39150;branch=z9hG4bK92232418F3D1B52C6E08
Contact:
<sip:192.168.43.1:39150;transport=tls;ms-opaque=d3470f2e1d>;methods="INV
ITE, MESSAGE, INFO, SUBSCRIBE, BYE, CANCEL, NOTIFY, ACK,
BENOTIFY";proxy=replace;+sip.instance="<urn:uuid:2e4b7961-5c1e-5b47-b623
-cf6988aa37b3>"
Here is an SRV resolution for an OCS server:
[arechenb...@cybertron ~]$ dig srv _sipinternaltls._tcp.flux.local
[...snip...]
;; ANSWER SECTION:
_sipinternaltls._tcp.flux.local. 3600 IN SRV 0 0 5061
ocs1.flux.local.
;; ADDITIONAL SECTION:
ocs1.flux.local. 1200 IN A 192.168.43.20
Confidentiality Notice: This e-mail message including attachments, if any, is
intended only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies of
the original message. If you are the intended recipient, but do not wish to
receive communications through this medium, please so advise the sender
immediately.
------------------------------
Message: 3
Date: Thu, 5 Feb 2009 11:51:37 -0500
From: "Andrew Rechenberg Lists" <[email protected]>
Subject: Re: [Sofia-sip-devel] Multiple WWW-Authenticate headers and
comparing au_scheme
To: "Pekka Pessi" <[email protected]>
Cc: [email protected]
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
> > Any word on the sub_alloc() question I posted on Friday?
>
> It looks like you have not allocated enough memory for gssapi
response..
>
I'm still having an issue with sub_alloc called from msg_header_format()
but the problem only occurs when I use the ipt base64_e function. If I
use my own base64 function based on the one in libpurple util.c, then
everything works and my authentication works as expected.
If I enable Guard Malloc I get a bad access in base64_e when trying to
encode the authentication response.
Any ideas?
Confidentiality Notice: This e-mail message including attachments, if any, is
intended only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies of
the original message. If you are the intended recipient, but do not wish to
receive communications through this medium, please so advise the sender
immediately.
------------------------------
Message: 4
Date: Thu, 5 Feb 2009 10:20:08 -0800
From: "Rostowsky, David" <[email protected]>
Subject: [Sofia-sip-devel] Multiple ethernet interface support?
To: "[email protected]"
<[email protected]>
Message-ID:
<606988f0c1c9cc4f9126bbcd7868def707e89b8...@air-sea7.airbiquity.com>
Content-Type: text/plain; charset="us-ascii"
Hi,
How does Sofia SIP handle multiple Ethernet interface support? I'm having a
problem where my linux box has eth0=172.16.1.1, and eth1=192.168.15.115. When
Sofia sends an INVITE out to the destination 192.168.15.13, my expectation was
that the source IP address should be 192.168.15.115. However, Ethereal captures
show the source IP address is actually 172.16.1.1. The INVITE is actually being
sent out eth1 as I have physically unplugged 172.16.1.1. How does Sofia's SIP
socket determine to use eth0's source IP address? It should be using eth1 as
the source IP address.
This is obviously causing the receiver of the INVITE issues as the 100-Trying,
etc are being sent to 172.16.1.1 which of course never reaches my linux box
since that cable is unplugged.
Thanks in advance!
-Dave R.
PS: As an aside, I wrote a simple UDP SIP socket socket program that sent my
own INVITE out to 192.168.15.13, and the source IP address in Ethereal is
correctly shown as eth1's (192.168.15.115). Therefore, I know this probably has
nothing to do with Linux OS routing tables, networking, etc. Its more to my
lack of understanding on Sofia. :)
________________________________
The information contained in this message, including attachments, may contain
privileged and/or confidential information that is intended to be delivered
only to the person(s) identified above. If you are not the intended
recipient(s), or the person responsible for delivering this message to the
intended recipient(s), Airbiquity Inc. requests that you immediately notify the
sender and asks that you do not read the message or its attachments and that
you delete them without copying or sending them to anyone else. Any review,
reliance or distribution by others not intended as recipients or forwarding
without express permission is strictly prohibited. Replies to this message may
be received by other Airbiquity personnel in addition to the intended
recipient(s).
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
Message: 5
Date: Thu, 5 Feb 2009 14:48:23 -0500
From: "Andrew Rechenberg Lists" <[email protected]>
Subject: Re: [Sofia-sip-devel] Multiple WWW-Authenticate headers
andcomparing au_scheme
To: "Pekka Pessi" <[email protected]>
Cc: [email protected]
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
>
> > > Any word on the sub_alloc() question I posted on Friday?
> >
> > It looks like you have not allocated enough memory for gssapi
> response..
> >
You are correct and I'm answering my own question once again :)
>
> I'm still having an issue with sub_alloc called from
msg_header_format()
> but the problem only occurs when I use the ipt base64_e function. If
I
> use my own base64 function based on the one in libpurple util.c, then
> everything works and my authentication works as expected.
>
> If I enable Guard Malloc I get a bad access in base64_e when trying to
> encode the authentication response.
>
> Any ideas?
>
I wasn't allocating the memory properly and Guard Malloc showed me.
Once I calloc(1, 256) for the gssapi response everything started working
with the ipt base64_e().
I'll get this going eventually :)
Thanks,
Andy.
Confidentiality Notice: This e-mail message including attachments, if any, is
intended only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies of
the original message. If you are the intended recipient, but do not wish to
receive communications through this medium, please so advise the sender
immediately.
------------------------------
Message: 6
Date: Thu, 5 Feb 2009 15:56:36 -0500
From: "Andrew Rechenberg Lists" <[email protected]>
Subject: Re: [Sofia-sip-devel] Multiple ethernet interface support?
To: "Rostowsky, David" <[email protected]>,
<[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="utf-8"
I'm not exactly sure how Sofia chooses which interface to use in the header,
but you can specify that Sofia only binds to a specific IP when you call
nua_create() with NUTAG_URL("sip:192.168.15.115").
PS Sorry about top-posting. Outlook doesn't add the > to replies when I
convert to plain text.
HTH,
Andy.
From: Rostowsky, David [mailto:[email protected]]
Sent: Thursday, February 05, 2009 1:20 PM
To: [email protected]
Subject: [Sofia-sip-devel] Multiple ethernet interface support?
Hi,
How does Sofia SIP handle multiple Ethernet interface support? I?m having a
problem where my linux box has eth0=172.16.1.1, and eth1=192.168.15.115. When
Sofia sends an INVITE out to the destination 192.168.15.13, my expectation was
that the source IP address should be 192.168.15.115. However, Ethereal captures
show the source IP address is actually 172.16.1.1. The INVITE is actually being
sent out eth1 as I have physically unplugged 172.16.1.1. How does Sofia?s SIP
socket determine to use eth0?s source IP address? It should be using eth1 as
the source IP address. ?
This is obviously causing the receiver of the INVITE issues as the 100-Trying,
etc are being sent to 172.16.1.1 which of course never reaches my linux box
since that cable is unplugged.
Thanks in advance!
-Dave R.
PS: As an aside, I wrote a simple UDP SIP socket socket program that sent my
own INVITE out to 192.168.15.13, and the source IP address in Ethereal is
correctly shown as eth1?s (192.168.15.115). Therefore, I know this probably has
nothing to do with Linux OS routing tables, networking, etc. ?Its more to my
lack of understanding on Sofia. ?
________________________________________
The information contained in this message, including attachments, may contain
privileged and/or confidential information that is intended to be delivered
only to the person(s) identified above. If you are not the intended
recipient(s), or the person responsible for delivering this message to the
intended recipient(s), Airbiquity Inc. requests that you immediately notify the
sender and asks that you do not read the message or its attachments and that
you delete them without copying or sending them to anyone else. Any review,
reliance or distribution by others not intended as recipients or forwarding
without express permission is strictly prohibited. Replies to this message may
be received by other Airbiquity personnel in addition to the intended
recipient(s).
Confidentiality Notice: This e-mail message including attachments, if any, is
intended only for the person or entity to which it is addressed and may contain
confidential and/or privileged material. Any unauthorized review, use,
disclosure or distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies of
the original message. If you are the intended recipient, but do not wish to
receive communications through this medium, please so advise the sender
immediately.
------------------------------
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
------------------------------
_______________________________________________
Sofia-sip-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
End of Sofia-sip-devel Digest, Vol 33, Issue 3
**********************************************
The information contained in this message, including attachments, may contain
privileged and/or confidential information that is intended to be delivered
only to the person(s) identified above. If you are not the intended
recipient(s), or the person responsible for delivering this message to the
intended recipient(s), Airbiquity Inc. requests that you immediately notify the
sender and asks that you do not read the message or its attachments and that
you delete them without copying or sending them to anyone else. Any review,
reliance or distribution by others not intended as recipients or forwarding
without express permission is strictly prohibited. Replies to this message may
be received by other Airbiquity personnel in addition to the intended
recipient(s).
------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Sofia-sip-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
