|
List Info
Thread: Little problems on Mac OS 10.3
|
|
| Little problems on Mac OS 10.3 |
  Germany |
2007-02-27 16:59:09 |
Hi all,
I'm new to this mailing-list so please consider me as a
total newbie when it
comes to SIP Communicator... and don't shoot me for this
post ;o). (If you
wanna shoot somebody for posting this, shoot emcho, he
forced me to do so
;-P).
I installed SIP Communicator on my mother's computer last
week-end as she
needed an SIP client. She's running a Mac OS 10.3 computer,
and I used an
installer (can't tell exactly which one it was). The
installation worked
without a hitch, but in the end, I couldn't lauch SIP
Communicator. I tried
to launch the run.sh script directly, but it failed, so I
soon realized the
problem was coming from the environment variable defining
the path to the
java binary location: it was pointing to "opt"
instead of "usr" on this
system. What's more, the script couldn't execute correctly
because of wrong
line-terminating caracters (but this conversion problem
should be
double-checked since it might come from the text editor I
used to edit the
file on this system).
. IMHO, it would be better to replace this variable with a
variable pointing
directly on the binary, using something like: export
JAVA_BIN=`which java` .
Is there a special reason why this variable wasn't set this
way (portability
issue maybe)?
. This modification enables to launch SIP Communicator by
hand (sh run.sh),
but it still doesn't work when simply clicking on the
directory. I added the
".app" extension to the directory containing SIP
Communicator, but it still
doesn't work. I guess I missed something? I'm not very
familiar with MacOS
and its .app directory tree.
. I couldn't manage to establish an SIP communication
(outgoing as well as
incoming). It rings, but when accepting the call, I get a
"failed!" popup
and the following console output (should I post the outputs
at the end of
the mail or as attachments next time?) :
------------------------------
22:49:07.546 GRAVE:
impl.media.MediaControl.createDataSourceForEncodings()
Processor is null.
22:49:08.051 GRAVE:
impl.protocol.sip.OperationSetBasicTelephonySipImpl.answerCa
llParticipant()
No sdp data was provided for the ok response to an INVITE
request!
net.java.sip.communicator.service.media.MediaException: The
source Processor
has not been initialized.
at
net.java.sip.communicator.impl.media.MediaControl.createData
SourceForEncodings(MediaControl.java:637)
at
net.java.sip.communicator.impl.media.CallSessionImpl.createS
endStreams(CallSessionImpl.java:515)
at
net.java.sip.communicator.impl.media.CallSessionImpl.process
SdpOffer(CallSessionImpl.java:490)
at
net.java.sip.communicator.impl.protocol.sip.OperationSetBasi
cTelephonySipImpl.answerCallParticipant(OperationSetBasicTel
ephonySipImpl.java:1760)
at
net.java.sip.communicator.impl.gui.main.call.CallManager$Ans
werCallThread.run(CallManager.java:777)
22:49:08.056 GRAVE: impl.gui.main.call.CallManager.run()
Could not answer to
: fwdusers pulver.com <"fwdusers pulver.com"
<sip:513 fwd.pulver.com>>;status=Failed caused by the
following exception:
net.java.sip.communicator.service.protocol.OperationFailedEx
ception: Failed
to created an SDP description for an ok response to an
INVITE request!
-------------------------------
I'm afraid I forgot to catch the output when initiating a
call, but I'll add
that next time. Is this a "normal" output (maybe
caused by a badly
configured router)?
As you noticed, my descriptions are quite vague since I was
really in a
hurry when I did all this (I spent only one night at my
mum's place), so I
couldn't dig deeper (especially check the router/NAT). I'm
in Germany at the
moment, so I won't be able to give more information or to
test anything.
I'll be back there next week-end.
Cheers,
Chris (onibaku on 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
|
|
| Re: Little problems on Mac OS 10.3 |

|
2007-02-27 19:13:16 |
Hi Chris,
Since you're having problems with the Mac package, let's all
shoot
Romain .
Jean
uid0 free.fr wrote:
> Hi all,
>
> I'm new to this mailing-list so please consider me as a
total newbie when it
> comes to SIP Communicator... and don't shoot me for
this post ;o). (If you
> wanna shoot somebody for posting this, shoot emcho, he
forced me to do so
> ;-P).
>
> I installed SIP Communicator on my mother's computer
last week-end as she
> needed an SIP client. She's running a Mac OS 10.3
computer, and I used an
> installer (can't tell exactly which one it was). The
installation worked
> without a hitch, but in the end, I couldn't lauch SIP
Communicator. I tried
> to launch the run.sh script directly, but it failed, so
I soon realized the
> problem was coming from the environment variable
defining the path to the
> java binary location: it was pointing to
"opt" instead of "usr" on this
> system. What's more, the script couldn't execute
correctly because of wrong
> line-terminating caracters (but this conversion problem
should be
> double-checked since it might come from the text editor
I used to edit the
> file on this system).
>
> . IMHO, it would be better to replace this variable
with a variable pointing
> directly on the binary, using something like: export
JAVA_BIN=`which java` .
> Is there a special reason why this variable wasn't set
this way (portability
> issue maybe)?
>
> . This modification enables to launch SIP Communicator
by hand (sh run.sh),
> but it still doesn't work when simply clicking on the
directory. I added the
> ".app" extension to the directory containing
SIP Communicator, but it still
> doesn't work. I guess I missed something? I'm not very
familiar with MacOS
> and its .app directory tree.
>
> . I couldn't manage to establish an SIP communication
(outgoing as well as
> incoming). It rings, but when accepting the call, I get
a "failed!" popup
> and the following console output (should I post the
outputs at the end of
> the mail or as attachments next time?) :
>
> ------------------------------
> 22:49:07.546 GRAVE:
impl.media.MediaControl.createDataSourceForEncodings()
> Processor is null.
> 22:49:08.051 GRAVE:
>
impl.protocol.sip.OperationSetBasicTelephonySipImpl.answerCa
llParticipant()
> No sdp data was provided for the ok response to an
INVITE request!
> net.java.sip.communicator.service.media.MediaException:
The source Processor
> has not been initialized.
> at
>
net.java.sip.communicator.impl.media.MediaControl.createData
SourceForEncodings(MediaControl.java:637)
> at
>
net.java.sip.communicator.impl.media.CallSessionImpl.createS
endStreams(CallSessionImpl.java:515)
> at
>
net.java.sip.communicator.impl.media.CallSessionImpl.process
SdpOffer(CallSessionImpl.java:490)
> at
>
net.java.sip.communicator.impl.protocol.sip.OperationSetBasi
cTelephonySipImpl.answerCallParticipant(OperationSetBasicTel
ephonySipImpl.java:1760)
> at
>
net.java.sip.communicator.impl.gui.main.call.CallManager$Ans
werCallThread.run(CallManager.java:777)
> 22:49:08.056 GRAVE:
impl.gui.main.call.CallManager.run() Could not answer to
> : fwdusers pulver.com <"fwdusers pulver.com"
> <sip:513 fwd.pulver.com>>;status=Failed
caused by the following exception:
>
net.java.sip.communicator.service.protocol.OperationFailedEx
ception: Failed
> to created an SDP description for an ok response to an
INVITE request!
> -------------------------------
>
> I'm afraid I forgot to catch the output when initiating
a call, but I'll add
> that next time. Is this a "normal" output
(maybe caused by a badly
> configured router)?
>
> As you noticed, my descriptions are quite vague since I
was really in a
> hurry when I did all this (I spent only one night at my
mum's place), so I
> couldn't dig deeper (especially check the router/NAT).
I'm in Germany at the
> moment, so I won't be able to give more information or
to test anything.
> I'll be back there next week-end.
>
> Cheers,
> Chris (onibaku on 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
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe sip-communicator.dev.java.net
For additional commands, e-mail: dev-help sip-communicator.dev.java.net
|
|
| Re: Little problems on Mac OS 10.3 |

|
2007-02-27 19:31:54 |
Hi Chris,
Jean Lorchat wrote:
> Since you're having problems with the Mac package,
let's all shoot
> Romain .
Actually, are you using the MacOSX specific package?
>> to launch the run.sh script directly, but it
failed, so I soon realized the
This makes me think you are using the generic installer. The
MacOSX
package does not have such script.
Please try a package from:
http://download.java.net/communications/
sip-communicator/nightly/macosx/
Regards,
--
Romain KUNTZ
kuntz sfc.wide.ad.jp
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe sip-communicator.dev.java.net
For additional commands, e-mail: dev-help sip-communicator.dev.java.net
|
|
[1-3]
|
|