Hi! This is the ezmlm program. I'm managing the
dev sip-communicator.dev.java.net mailing list.
Messages to you from the dev mailing list seem to
have been bouncing. I sent you a warning message, but it
bounced.
I've attached a copy of the bounce message.
This is a probe to check whether your address is reachable.
If this
probe bounces, I will remove your address from the
dev sip-communicator.dev.java.net mailing list, without
further notice. You can re-subscribe
by sending an empty message to the following address:
<dev-subscribe sip-communicator.dev.java.net>
--- Enclosed is a copy of the bounce message I received.
Return-Path: <>
Received: (qmail 13493 invoked from network); 4 Feb 2008
07:22:03 -0000
Received: from cylon2.sjc.collab.net (204.16.104.18)
by s015.sjc.collab.net with SMTP; 4 Feb 2008 07:22:03
-0000
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result:
Ao8CACRMpkdFOYmUeWdsb2JhbACQKQEBCQoZEJls
X-IronPort-AV: E=Sophos;i="4.25,300,1199692800";
d="scan'208";a="974590"
X-IRONPORT: SCANNED
Received: from starfire.sharedlog.com ([69.57.137.148])
by cylon2.sjc.collab.net with ESMTP; 03 Feb 2008 23:22:02
-0800
Received: by starfire.sharedlog.com (Postfix)
id E7B0050937A; Mon, 4 Feb 2008 01:22:00 -0600 (CST)
Date: Mon, 4 Feb 2008 01:22:00 -0600 (CST)
From: MAILER-DAEMON sharedlog.com (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To:
dev-return-warn-1202109711.fhlofkgdkaeileojoecc-nessto=share
dlog.com sip-communicator.dev.java.net
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report;
report-type=delivery-status;
boundary="AE570509372.1202109720/starfire.sharedlog.co
m"
Content-Transfer-Encoding: 8bit
Message-Id: <20080204072200.E7B0050937A starfire.sharedlog.com>
This is a MIME-encapsulated message.
--AE570509372.1202109720/starfire.sharedlog.com
Content-Description: Notification
Content-Type: text/plain; charset=us-ascii
This is the mail system at host starfire.sharedlog.com.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached
below.
For further assistance, please send mail to
<postmaster>
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<message sharedlog.com>: cannot update mailbox
/var/mail/message for user
message. error writing message: File too large
--AE570509372.1202109720/starfire.sharedlog.com
Content-Description: Delivery report
Content-Type: message/delivery-status
Reporting-MTA: dns; starfire.sharedlog.com
X-Postfix-Queue-ID: AE570509372
X-Postfix-Sender: rfc822;
dev-return-warn-1202109711.fhlofkgdkaeileojoecc-nessto=share
dlog.com sip-communicator.dev.java.net
Arrival-Date: Mon, 4 Feb 2008 01:22:00 -0600 (CST)
Final-Recipient: rfc822; message sharedlog.com
Original-Recipient: rfc822;message sharedlog.com
Action: failed
Status: 5.2.2
Diagnostic-Code: x-unix; input/output error
--AE570509372.1202109720/starfire.sharedlog.com
Content-Description: Undelivered Message
Content-Type: message/rfc822
Content-Transfer-Encoding: 8bit
Received: from localhost (localhost.domain [127.0.0.1])
by av.sharedlog.com (Postfix) with ESMTP id AE570509372
for <message sharedlog.com>; Mon, 4 Feb 2008
01:22:00 -0600 (CST)
X-Virus-Scanned: amavisd-new at sharedlog.com
Received: from starfire.sharedlog.com ([127.0.0.1])
by localhost (starfire.sharedlog.com [127.0.0.1])
(amavisd-new, port 10024)
with ESMTP id mnGeAIYyZGKU for <message sharedlog.com>;
Mon, 4 Feb 2008 01:21:56 -0600 (CST)
Received: from dev.java.net (s015.sjc.collab.net
[204.16.104.198])
by starfire.sharedlog.com (Postfix) with SMTP id
EC8145080A2
for <nessto sharedlog.com>; Mon, 4 Feb 2008
01:21:53 -0600 (CST)
Received: (qmail 13229 invoked by uid 5000); 4 Feb 2008
07:21:51 -0000
Mailing-List: contact dev-help sip-communicator.dev.java.net; run by ezmlm
Date: 4 Feb 2008 07:21:51 -0000
Message-ID: <1202109711.13179.ezmlm-warn sip-communicator.dev.java.net>
From: dev-help sip-communicator.dev.java.net
To: nessto sharedlog.com
Content-type: text/plain; charset=iso-8859-1
Subject: ezmlm warning
Hi! This is the ezmlm program. I'm managing the
dev sip-communicator.dev.java.net mailing list.
Messages to you from the dev mailing list seem to
have been bouncing. I've attached a copy of the first
bounce
message I received.
If this message bounces too, I will send you a probe. If the
probe bounces,
I will remove your address from the dev mailing list,
without further notice.
I've kept a list of which messages from the dev mailing list
have
bounced from your address.
Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per
request),
send an empty message to:
<dev-get.123_145 sip-communicator.dev.java.net>
To receive a subject and author list for the last 100 or so
messages,
send an empty message to:
<dev-index sip-communicator.dev.java.net>
Here are the message numbers:
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
--- Enclosed is a copy of the bounce message I received.
Return-Path: <>
Received: (qmail 21448 invoked from network); 23 Jan 2008
09:01:36 -0000
Received: from cylon2.sjc.collab.net (204.16.104.18)
by s015.sjc.collab.net with SMTP; 23 Jan 2008 09:01:36
-0000
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result:
AgAAAN6QlkdFOYmUeWdsb2JhbACQFwEBCQoZEJx/
X-IronPort-AV: E=Sophos;i="4.25,237,1199692800";
d="scan'208";a="80155004"
X-IRONPORT: SCANNED
Received: from starfire.sharedlog.com ([69.57.137.148])
by cylon2.sjc.collab.net with ESMTP; 23 Jan 2008 01:01:35
-0800
Received: by starfire.sharedlog.com (Postfix)
id D540F508A5D; Wed, 23 Jan 2008 03:01:34 -0600 (CST)
Date: Wed, 23 Jan 2008 03:01:34 -0600 (CST)
From: MAILER-DAEMON sharedlog.com (Mail Delivery System)
Subject: Undelivered Mail Returned to Sender
To: dev-return-2950-nessto=sharedlog.com sip-communicator.dev.java.net
Auto-Submitted: auto-replied
MIME-Version: 1.0
Content-Type: multipart/report;
report-type=delivery-status;
boundary="ADC2A50869A.1201078894/starfire.sharedlog.co
m"
Content-Transfer-Encoding: 8bit
Message-Id: <20080123090134.D540F508A5D starfire.sharedlog.com>
This is a MIME-encapsulated message.
--ADC2A50869A.1201078894/starfire.sharedlog.com
Content-Description: Notification
Content-Type: text/plain; charset=us-ascii
This is the mail system at host starfire.sharedlog.com.
I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached
below.
For further assistance, please send mail to
<postmaster>
If you do so, please include this problem report. You can
delete your own text from the attached returned message.
The mail system
<message sharedlog.com>: cannot update mailbox
/var/mail/message for user
message. error writing message: File too large
--ADC2A50869A.1201078894/starfire.sharedlog.com
Content-Description: Delivery report
Content-Type: message/delivery-status
Reporting-MTA: dns; starfire.sharedlog.com
X-Postfix-Queue-ID: ADC2A50869A
X-Postfix-Sender: rfc822;
dev-return-2950-nessto=sharedlog.com sip-communicator.dev.java.net
Arrival-Date: Wed, 23 Jan 2008 03:01:34 -0600 (CST)
Final-Recipient: rfc822; message sharedlog.com
Original-Recipient: rfc822;message sharedlog.com
Action: failed
Status: 5.2.2
Diagnostic-Code: x-unix; input/output error
--ADC2A50869A.1201078894/starfire.sharedlog.com
Content-Description: Undelivered Message
Content-Type: message/rfc822
Content-Transfer-Encoding: 8bit
Received: from localhost (localhost.domain [127.0.0.1])
by av.sharedlog.com (Postfix) with ESMTP id ADC2A50869A
for <message sharedlog.com>; Wed, 23 Jan 2008
03:01:34 -0600 (CST)
X-Virus-Scanned: amavisd-new at sharedlog.com
Received: from starfire.sharedlog.com ([127.0.0.1])
by localhost (starfire.sharedlog.com [127.0.0.1])
(amavisd-new, port 10024)
with ESMTP id VtVqPsNvjuTa for <message sharedlog.com>;
Wed, 23 Jan 2008 03:01:31 -0600 (CST)
Received: from dev.java.net (s015.sjc.collab.net
[204.16.104.198])
by starfire.sharedlog.com (Postfix) with SMTP id
E68F45080B3
for <nessto sharedlog.com>; Wed, 23 Jan 2008
03:01:27 -0600 (CST)
Received: (qmail 20947 invoked by uid 5000); 23 Jan 2008
09:01:23 -0000
Mailing-List: contact dev-help sip-communicator.dev.java.net; run by ezmlm
Precedence: bulk
X-No-Archive: yes
list-help: <mailto:dev-help sip-communicator.dev.java.net>
list-unsubscribe: <mailto:dev-unsubscribe sip-communicator.dev.java.net>
list-post: <mailto:dev sip-communicator.dev.java.net>
Reply-To: dev sip-communicator.dev.java.net
Delivered-To: mailing list dev sip-communicator.dev.java.net
Received: (qmail 20895 invoked from network); 23 Jan 2008
09:01:22 -0000
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ao8CAN6QlkfZTId0/2dsb2JhbACtVA
X-IronPort-AV: E=Sophos;i="4.25,237,1199692800";
d="scan'208";a="97192419"
X-IRONPORT: SCANNED
Message-ID: <47970258.10202 isyc.com>
Date: Wed, 23 Jan 2008 10:01:12 +0100
From: Alex Moros Marco <amoros isyc.com>
User-Agent: Thunderbird 2.0.0.9 (Windows/20071031)
MIME-Version: 1.0
To: dev sip-communicator.dev.java.net, damencho damencho.com
References: <47861384.40505 isyc.com>
<47861741.5080408 damencho.com> <47863B0A.9040306 isyc.com> <47863D5D.6010606 damencho.com> <4786429D.5050703 isyc.com> <47864503.9080904 damencho.com> <478646B7.4030404 isyc.com> <47864958.5000905 damencho.com> <47864C84.4020100 isyc.com> <478B2808.9020201 isyc.com> <478B815B.5060200 damencho.com>
In-Reply-To: <478B815B.5060200 damencho.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [sip-comm-dev] how to set a STUN
Hi Damian, did you solve the problem with the STUN? If you
do, let me
know. Thanks a lot.
Damian Minkov escribió:
> Hi,
>
> I've just tested it, it doesn't work. Your config is
ok. Actually the
> problem is somewhere in the stun support.
> In the thread running stun address discovery the
StunAdrress is null.
> StunAddress stunAddress
> =
detector.getMappingFor(randomSocket);
> I will try to find the problem and will reported here
on the list
>
> damencho
>
>
> Alex Moros Marco wrote:
>> Hi Damian, and everybody. I'd like to keep with the
dialog about
>> setting a STUN in the xml file, cause i didn't
succeed. You can find
>> below, the sippet code of my xml and its
explanation, can you try it
>> and then if works, send me the xml file? or the
snippet code, i don't
>> mind.
>>
>> Thanks!
>>
>>
>> Alex Moros Marco escribió:
>>> Yes, you are right, I've just checked it also.
I guess that is the
>>> structure where it looks for a stun name in the
xml file.
>>>
>>> I also tryed setting the stun port (3478):
>>>
>>> <?xml version="1.0"
encoding="UTF-8" standalone="no"?>
>>> <sip-communicator>
>>> <net>
>>> <java>
>>> <sip>
>>> <communicator>
>>> <SC_HOME_DIR_NAME
value=".sip-communicator"/>
>>> <SC_HOME_DIR_LOCATION
value="C:Documents and
>>> SettingsAlejandro"/>
>>> <impl>
>>> <netaddr>
>>>
<STUN_SERVER_ADDRESS
>>> value="stun.zoiper.com"/>
>>> <STUN_SERVER_PORT
value="3478"/>
>>> </netaddr>
>>> <notifications>
>>>
>>>
>>> But doesn't work either and deletes the code
line of the port. This
>>> STUN already works in a softphone, i don't get
why it doesn't work
>>> in sip-communicator.
>>>
>>> Thanks.
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Damian Minkov escribió:
>>>> Hi,
>>>>
>>>> yes I've checked it here is the code :
>>>>
>>>> /**
>>>> * The name of the property containing
the stun server address.
>>>> */
>>>> private static final String
PROP_STUN_SERVER_ADDRESS
>>>> =
>>>>
"net.java.sip.communicator.impl.netaddr.STUN_SERVER_ADD
RESS";
>>>>
>>>> damencho
>>>>
>>>>
>>>>
>>>> Alex Moros Marco wrote:
>>>>> Thanks but doesn't work, did you check
the name
>>>>> "STUN_SERVER_ADDRESS"?
>>>>>
>>>>> I just found some close names but not
exactly that one.
>>>>>
>>>>> thanks
>>>>>
>>>>>
>>>>>
>>>>> Damian Minkov escribió:
>>>>>> Hi,
>>>>>>
>>>>>> I have just saw that the java doc
and the implementation are
>>>>>> different.
>>>>>>
>>>>>> Can you try this :
>>>>>>
>>>>>> <?xml version="1.0"
encoding="UTF-8" standalone="no"?>
>>>>>> <sip-communicator>
>>>>>> <net>
>>>>>> <java>
>>>>>> <sip>
>>>>>> <communicator>
>>>>>>
<SC_HOME_DIR_NAME
value=".sip-communicator"/>
>>>>>>
<SC_HOME_DIR_LOCATION value="C:Documents and
>>>>>> SettingsAlejandro"/>
>>>>>> <impl>
>>>>>>
<netaddr>
>>>>>>
<STUN_SERVER_ADDRESS
>>>>>>
value="stun.zoiper.com"/>
>>>>>>
>>>>>> damencho
>>>>>>
>>>>>>
>>>>>> Alex Moros Marco wrote:
>>>>>>> This is the beginning of my xml
file:
>>>>>>>
>>>>>>> <?xml
version="1.0" encoding="UTF-8"
standalone="no"?>
>>>>>>> <sip-communicator>
>>>>>>> <net>
>>>>>>> <java>
>>>>>>> <sip>
>>>>>>>
<communicator>
>>>>>>>
<SC_HOME_DIR_NAME
value=".sip-communicator"/>
>>>>>>>
<SC_HOME_DIR_LOCATION value="C:Documents and
>>>>>>> SettingsAlejandro"/>
>>>>>>>
<STUN_SERVER_ADDRESS
value="stun.zoiper.com"/>
>>>>>>>
<impl>
>>>>>>>
<notifications>
>>>>>>>
>>>>>>>
>>>>>>> Are you sure that name of the
variable 'STUN_SERVER_ADDRESS' is
>>>>>>> correct? Cause in the website
you linked me before, there is not
>>>>>>> a variable with that name, just
some really close names.
>>>>>>>
>>>>>>> Should i put that code line
inside the part of my account, maybe?
>>>>>>>
>>>>>>> Just looking for solutions...
>>>>>>>
>>>>>>> Thanks a lot.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Damian Minkov escribió:
>>>>>>>> Hi,
>>>>>>>>
>>>>>>>> Alex Moros Marco wrote:
>>>>>>>>> Thanks, Damian, so
introducing that snippet of XML code in the
>>>>>>>>> 'sip-communicator.xml'
would work?
>>>>>>>> Yes.
>>>>>>>>>
>>>>>>>>> I had a look to the
code, and found that there is a boolean
>>>>>>>>> variable like below:
>>>>>>>>>
>>>>>>>>> /**
>>>>>>>>> * Specifies whether
or not STUN should be used for NAT
>>>>>>>>> traversal
>>>>>>>>> */
>>>>>>>>> private boolean
useStun = false;
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Don't I need to set the
boolean variable to true in the xml file?
>>>>>>>> No.
>>>>>>>>>
>>>>>>>>> Is there anyway where I
can see the configuration options of
>>>>>>>>> the
'sip-communicator.xml'? So that i can see in a easy way
>>>>>>>>> how to add
configuration settings to the xml file.
>>>>>>>> No there is now such
document right now.
>>>>>>>>
>>>>>>>> damencho
>>>>>>>>
>>>>>>>>
------------------------------------------------------------
---------
>>>>>>>>
>>>>>>>> To unsubscribe, e-mail:
>>>>>>>> dev-unsubscribe sip-communicator.dev.java.net
>>>>>>>> For additional commands,
e-mail:
>>>>>>>> dev-help sip-communicator.dev.java.net
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> __________ Información de
NOD32, revisión 2759 (20080101)
>>>>>>>> __________
>>>>>>>>
>>>>>>>> Este mensaje ha sido
analizado con NOD32 antivirus system
>>>>>>>> http://www.nod32.com
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
------------------------------------------------------------
---------
>>>>>>>
>>>>>>> To unsubscribe, e-mail:
>>>>>>> dev-unsubscribe sip-communicator.dev.java.net
>>>>>>> For additional commands,
e-mail:
>>>>>>> dev-help sip-communicator.dev.java.net
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
------------------------------------------------------------
---------
>>>>>>
>>>>>> To unsubscribe, e-mail:
>>>>>> dev-unsubscribe sip-communicator.dev.java.net
>>>>>> For additional commands, e-mail:
>>>>>> dev-help sip-communicator.dev.java.net
>>>>>>
>>>>>>
>>>>>>
>>>>>> __________ Información de NOD32,
revisión 2759 (20080101) __________
>>>>>>
>>>>>> Este mensaje ha sido analizado con
NOD32 antivirus system
>>>>>> http://www.nod32.com
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
------------------------------------------------------------
---------
>>>>> To unsubscribe, e-mail:
dev-unsubscribe sip-communicator.dev.java.net
>>>>> For additional commands, e-mail:
>>>>> dev-help sip-communicator.dev.java.net
>>>>>
>>>>>
>>>>
>>>>
------------------------------------------------------------
---------
>>>> To unsubscribe, e-mail: dev-unsubscribe sip-communicator.dev.java.net
>>>> For additional commands, e-mail:
>>>> dev-help sip-communicator.dev.java.net
>>>>
>>>>
>>>>
>>>> __________ Información de NOD32, revisión
2759 (20080101) __________
>>>>
>>>> Este mensaje ha sido analizado con NOD32
antivirus system
>>>> http://www.nod32.com
>>>>
>>>>
>>>>
>>>
>>>
------------------------------------------------------------
---------
>>> To unsubscribe, e-mail: dev-unsubscribe sip-communicator.dev.java.net
>>> For additional commands, e-mail: dev-help sip-communicator.dev.java.net
>>>
>>>
>>>
>>> __________ Información de NOD32, revisión 2759
(20080101) __________
>>>
>>> Este mensaje ha sido analizado con NOD32
antivirus system
>>> http://www.nod32.com
>>>
>>>
>>>
>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribe sip-communicator.dev.java.net
>> For additional commands, e-mail: dev-help sip-communicator.dev.java.net
>>
>>
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribe sip-communicator.dev.java.net
> For additional commands, e-mail: dev-help sip-communicator.dev.java.net
>
>
>
> __________ Información de NOD32, revisión 2759
(20080101) __________
>
> Este mensaje ha sido analizado con NOD32 antivirus
system
> http://www.nod32.com
>
>
>
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe sip-communicator.dev.java.net
For additional commands, e-mail: dev-help sip-communicator.dev.java.net
--ADC2A50869A.1201078894/starfire.sharedlog.com--
--AE570509372.1202109720/starfire.sharedlog.com--
|