[sip-comm] Cannot connect to a ekiga.net sip account


#1

Hej,

I have to sip account one from justvoip.com and one from ekiga.net. sip-communicator works with justvoip but I can't connect to ekiga.net. The only message in the UI I get is that the connection to ekiga.net can't be established. Thanks for your help in advance.

Here are some debug output:

16:45:26.689 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: clientTx: looking for key z9hg4bk531ee5aab8307ece2467ac05716f7f96
16:45:26.690 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: Found Transaction gov.nist.javax.sip.stack.SIPClientTransaction@2ed88e44 for SIP/2.0 606 Not Acceptable
Call-ID: a549504274cf71f7380f48f71f8da07b@0:0:0:0:0:0:0:0
CSeq: 4 REGISTER

From: <sip:username@ekiga.net>;tag=733b8517

Via: SIP/2.0/UDP 192.168.1.95:5060;branch=z9hG4bK531ee5aab8307ece2467ac05716f7f96;received=78.55.3.82
Server: Kamailio (1.5.3-notls (i386/linux))
Content-Length: 0

16:45:26.690 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: Setting response interface for gov.nist.javax.sip.stack.SIPClientTransaction@2ed88e44 to gov.nist.javax.sip.DialogFilter@16e9494
16:45:26.691 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: processing SIP/2.0 606 Not Acceptable
current state = Trying Transaction
16:45:26.692 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: dialog = null
16:45:26.692 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: PROCESSING INCOMING RESPONSESIP/2.0 606 Not Acceptable
Call-ID: a549504274cf71f7380f48f71f8da07b@0:0:0:0:0:0:0:0
CSeq: 4 REGISTER

From: <sip:username@ekiga.net>;tag=733b8517

Via: SIP/2.0/UDP 192.168.1.95:5060;branch=z9hG4bK531ee5aab8307ece2467ac05716f7f96;received=78.55.3.82
Server: Kamailio (1.5.3-notls (i386/linux))
Content-Length: 0

16:45:26.693 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: Transaction = gov.nist.javax.sip.stack.SIPClientTransaction@2ed88e44
16:45:26.693 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: handleEvent javax.sip.ResponseEvent[source=gov.nist.javax.sip.SipProviderImpl@9a44f1]currentTransaction = gov.nist.javax.sip.stack.SIPClientTransaction@2ed88e44this.sipListener = net.java.sip.communicator.impl.protocol.sip.SipStackSharing@cf17c3sipEvent.source = gov.nist.javax.sip.SipProviderImpl@9a44f1
16:45:26.694 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: Dialog = null
16:45:26.695 FEINER: impl.protocol.sip.SipLogger.logStackTrace().41 JAIN-SIP stack trace
java.lang.Throwable
  at net.java.sip.communicator.impl.protocol.sip.SipLogger.logStackTrace(SipLogger.java:41)
  at gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:174)
  at gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1062)
  at gov.nist.javax.sip.stack.SIPClientTransaction.nonInviteClientTransaction(SIPClientTransaction.java:635)
  at gov.nist.javax.sip.stack.SIPClientTransaction.processResponse(SIPClientTransaction.java:548)
  at gov.nist.javax.sip.stack.SIPClientTransaction.processResponse(SIPClientTransaction.java:1431)
  at gov.nist.javax.sip.stack.UDPMessageChannel.processMessage(UDPMessageChannel.java:497)
  at gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:414)
  at gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:258)
  at java.lang.Thread.run(Thread.java:636)
16:45:26.705 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: sipEvent = javax.sip.ResponseEvent[source=gov.nist.javax.sip.SipProviderImpl@9a44f1]source = gov.nist.javax.sip.SipProviderImpl@9a44f1
16:45:26.706 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: Calling listener for SIP/2.0 606 Not Acceptable

16:45:26.706 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: setPassToListener()
16:45:26.706 FEINER: impl.protocol.sip.SipStackSharing.processResponse().655 received response: 606 Not Acceptable
16:45:26.707 FEINER: impl.protocol.sip.SipStackSharing.getServiceData().943 service was found in request data
16:45:26.707 FEIN: impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse().525 received response=
SIP/2.0 606 Not Acceptable
Call-ID: a549504274cf71f7380f48f71f8da07b@0:0:0:0:0:0:0:0
CSeq: 4 REGISTER

From: <sip:username@ekiga.net>;tag=733b8517

Via: SIP/2.0/UDP 192.168.1.95:5060;branch=z9hG4bK531ee5aab8307ece2467ac05716f7f96;received=78.55.3.82
Server: Kamailio (1.5.3-notls (i386/linux))
Content-Length: 0

16:45:26.708 FEIN: impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse().543 Found 1 processor(s) for method REGISTER
16:45:26.708 SCHWERWIEGEND: impl.protocol.sip.SipRegistrarConnection.processResponse().740 Received an error response.
16:45:26.709 FEIN: service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged().115 Dispatching RegistrationStateChangeEvent[ oldState=Registering; newState=RegistrationState=Connection Failed; reasonCode=-1; reason=Received an error while trying to register. Server returned error:Not Acceptable] to 9 listeners.
16:45:26.709 FEIN: impl.protocol.sip.OperationSetBasicInstantMessagingSipImpl.registrationStateChanged().524 The provider changed state from: RegistrationState=Registering to: RegistrationState=Connection Failed
16:45:26.710 FEIN: impl.protocol.sip.OperationSetTypingNotificationsSipImpl.registrationStateChanged().102 The provider changed state from: RegistrationState=Registering to: RegistrationState=Connection Failed
16:45:27.106 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: sendMessage 86.64.162.35/5060
messageSize = 484 message = REGISTER sip:ekiga.net SIP/2.0
Call-ID: a549504274cf71f7380f48f71f8da07b@0:0:0:0:0:0:0:0
CSeq: 4 REGISTER

From: <sip:username@ekiga.net>;tag=733b8517

Via: SIP/2.0/UDP 192.168.1.95:5060;branch=z9hG4bK531ee5aab8307ece2467ac05716f7f96
Max-Forwards: 70
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2338Linux
Expires: 3600
Contact: "username" <sip:username@192.168.1.95:5060;transport=udp;registering_acc=ekiga_net>;expires=3600
Content-Length: 0

16:45:27.106 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: *******************

16:45:27.107 FEINER: impl.protocol.sip.SipLogger.logMessage().186 JAIN-SIP sent message from "0:0:0:0:0:0:0:0:5060"to "86.64.162.35:5060" at 1263656727104:
REGISTER sip:ekiga.net SIP/2.0
Call-ID: a549504274cf71f7380f48f71f8da07b@0:0:0:0:0:0:0:0
CSeq: 4 REGISTER

From: <sip:username@ekiga.net>;tag=733b8517

Via: SIP/2.0/UDP 192.168.1.95:5060;branch=z9hG4bK531ee5aab8307ece2467ac05716f7f96
Max-Forwards: 70
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2338Linux
Expires: 3600
Contact: "username" <sip:username@192.168.1.95:5060;transport=udp;registering_acc=ekiga_net>;expires=3600
Content-Length: 0

16:45:27.191 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: UDPMessageChannel: processIncomingDataPacket : peerAddress = 86.64.162.35/5060 Length = 387
16:45:27.193 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: acquireSem [[[[gov.nist.javax.sip.stack.SIPClientTransaction@2ed88e44
16:45:27.194 FEINER: impl.protocol.sip.SipLogger.logStackTrace().41 JAIN-SIP stack trace
java.lang.Throwable
  at net.java.sip.communicator.impl.protocol.sip.SipLogger.logStackTrace(SipLogger.java:41)
  at gov.nist.javax.sip.stack.SIPTransaction.acquireSem(SIPTransaction.java:1158)
  at gov.nist.javax.sip.stack.SIPTransactionStack.newSIPServerResponse(SIPTransactionStack.java:1176)
  at gov.nist.javax.sip.stack.UDPMessageChannel.processMessage(UDPMessageChannel.java:483)
  at gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:414)
  at gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:258)
  at java.lang.Thread.run(Thread.java:636)
16:45:28.195 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: acquireSem() returning : false
16:45:28.196 FEINER: impl.protocol.sip.SipLogger.logMessage().209 JAIN-SIP received message from "86.64.162.35:5060" to "0:0:0:0:0:0:0:0:5060" at 1263656728195 (status: before processing):
SIP/2.0 606 Not Acceptable
Call-ID: a549504274cf71f7380f48f71f8da07b@0:0:0:0:0:0:0:0
CSeq: 4 REGISTER

From: <sip:username@ekiga.net>;tag=733b8517

Via: SIP/2.0/UDP 192.168.1.95:5060;branch=z9hG4bK531ee5aab8307ece2467ac05716f7f96;received=78.55.3.82
Server: Kamailio (1.5.3-notls (i386/linux))
Content-Length: 0

bye,
martin.

···

To: <sip:username@ekiga.net>;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.df3e
To: <sip:username@ekiga.net>;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.df3e
To: <sip:username@ekiga.net>;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.df3e
To: <sip:username@ekiga.net>
To: <sip:username@ekiga.net>
To: <sip:username@ekiga.net>;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.df3e


#2

Hey Martin,

I am afraid we don't consider this to be an issue with SIP Communicator :frowning:

You can have a look here for a few more details explanation:

https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=435

Maybe we should try to sort this out with the ekiga.net maintainers
(provided they are willing to). Anyone wants to serve as liaison?

Cheers,
Emil

Martin Schaaf написа:

···

Hej,

I have to sip account one from justvoip.com and one from ekiga.net. sip-communicator works with justvoip but I can't connect to ekiga.net. The only message in the UI I get is that the connection to ekiga.net can't be established. Thanks for your help in advance.

Here are some debug output:

16:45:26.689 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: clientTx: looking for key z9hg4bk531ee5aab8307ece2467ac05716f7f96
16:45:26.690 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: Found Transaction gov.nist.javax.sip.stack.SIPClientTransaction@2ed88e44 for SIP/2.0 606 Not Acceptable
Call-ID: a549504274cf71f7380f48f71f8da07b@0:0:0:0:0:0:0:0
CSeq: 4 REGISTER
From: <sip:username@ekiga.net>;tag=733b8517
To: <sip:username@ekiga.net>;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.df3e
Via: SIP/2.0/UDP 192.168.1.95:5060;branch=z9hG4bK531ee5aab8307ece2467ac05716f7f96;received=78.55.3.82
Server: Kamailio (1.5.3-notls (i386/linux))
Content-Length: 0

16:45:26.690 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: Setting response interface for gov.nist.javax.sip.stack.SIPClientTransaction@2ed88e44 to gov.nist.javax.sip.DialogFilter@16e9494
16:45:26.691 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: processing SIP/2.0 606 Not Acceptable
current state = Trying Transaction
16:45:26.692 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: dialog = null
16:45:26.692 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: PROCESSING INCOMING RESPONSESIP/2.0 606 Not Acceptable
Call-ID: a549504274cf71f7380f48f71f8da07b@0:0:0:0:0:0:0:0
CSeq: 4 REGISTER
From: <sip:username@ekiga.net>;tag=733b8517
To: <sip:username@ekiga.net>;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.df3e
Via: SIP/2.0/UDP 192.168.1.95:5060;branch=z9hG4bK531ee5aab8307ece2467ac05716f7f96;received=78.55.3.82
Server: Kamailio (1.5.3-notls (i386/linux))
Content-Length: 0

16:45:26.693 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: Transaction = gov.nist.javax.sip.stack.SIPClientTransaction@2ed88e44
16:45:26.693 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: handleEvent javax.sip.ResponseEvent[source=gov.nist.javax.sip.SipProviderImpl@9a44f1]currentTransaction = gov.nist.javax.sip.stack.SIPClientTransaction@2ed88e44this.sipListener = net.java.sip.communicator.impl.protocol.sip.SipStackSharing@cf17c3sipEvent.source = gov.nist.javax.sip.SipProviderImpl@9a44f1
16:45:26.694 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: Dialog = null
16:45:26.695 FEINER: impl.protocol.sip.SipLogger.logStackTrace().41 JAIN-SIP stack trace
java.lang.Throwable
  at net.java.sip.communicator.impl.protocol.sip.SipLogger.logStackTrace(SipLogger.java:41)
  at gov.nist.javax.sip.SipProviderImpl.handleEvent(SipProviderImpl.java:174)
  at gov.nist.javax.sip.DialogFilter.processResponse(DialogFilter.java:1062)
  at gov.nist.javax.sip.stack.SIPClientTransaction.nonInviteClientTransaction(SIPClientTransaction.java:635)
  at gov.nist.javax.sip.stack.SIPClientTransaction.processResponse(SIPClientTransaction.java:548)
  at gov.nist.javax.sip.stack.SIPClientTransaction.processResponse(SIPClientTransaction.java:1431)
  at gov.nist.javax.sip.stack.UDPMessageChannel.processMessage(UDPMessageChannel.java:497)
  at gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:414)
  at gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:258)
  at java.lang.Thread.run(Thread.java:636)
16:45:26.705 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: sipEvent = javax.sip.ResponseEvent[source=gov.nist.javax.sip.SipProviderImpl@9a44f1]source = gov.nist.javax.sip.SipProviderImpl@9a44f1
16:45:26.706 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: Calling listener for SIP/2.0 606 Not Acceptable

16:45:26.706 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: setPassToListener()
16:45:26.706 FEINER: impl.protocol.sip.SipStackSharing.processResponse().655 received response: 606 Not Acceptable
16:45:26.707 FEINER: impl.protocol.sip.SipStackSharing.getServiceData().943 service was found in request data
16:45:26.707 FEIN: impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse().525 received response=
SIP/2.0 606 Not Acceptable
Call-ID: a549504274cf71f7380f48f71f8da07b@0:0:0:0:0:0:0:0
CSeq: 4 REGISTER
From: <sip:username@ekiga.net>;tag=733b8517
To: <sip:username@ekiga.net>;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.df3e
Via: SIP/2.0/UDP 192.168.1.95:5060;branch=z9hG4bK531ee5aab8307ece2467ac05716f7f96;received=78.55.3.82
Server: Kamailio (1.5.3-notls (i386/linux))
Content-Length: 0

16:45:26.708 FEIN: impl.protocol.sip.ProtocolProviderServiceSipImpl.processResponse().543 Found 1 processor(s) for method REGISTER
16:45:26.708 SCHWERWIEGEND: impl.protocol.sip.SipRegistrarConnection.processResponse().740 Received an error response.
16:45:26.709 FEIN: service.protocol.AbstractProtocolProviderService.fireRegistrationStateChanged().115 Dispatching RegistrationStateChangeEvent[ oldState=Registering; newState=RegistrationState=Connection Failed; reasonCode=-1; reason=Received an error while trying to register. Server returned error:Not Acceptable] to 9 listeners.
16:45:26.709 FEIN: impl.protocol.sip.OperationSetBasicInstantMessagingSipImpl.registrationStateChanged().524 The provider changed state from: RegistrationState=Registering to: RegistrationState=Connection Failed
16:45:26.710 FEIN: impl.protocol.sip.OperationSetTypingNotificationsSipImpl.registrationStateChanged().102 The provider changed state from: RegistrationState=Registering to: RegistrationState=Connection Failed
16:45:27.106 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: sendMessage 86.64.162.35/5060
messageSize = 484 message = REGISTER sip:ekiga.net SIP/2.0
Call-ID: a549504274cf71f7380f48f71f8da07b@0:0:0:0:0:0:0:0
CSeq: 4 REGISTER
From: <sip:username@ekiga.net>;tag=733b8517
To: <sip:username@ekiga.net>
Via: SIP/2.0/UDP 192.168.1.95:5060;branch=z9hG4bK531ee5aab8307ece2467ac05716f7f96
Max-Forwards: 70
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2338Linux
Expires: 3600
Contact: "username" <sip:username@192.168.1.95:5060;transport=udp;registering_acc=ekiga_net>;expires=3600
Content-Length: 0

16:45:27.106 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: *******************

16:45:27.107 FEINER: impl.protocol.sip.SipLogger.logMessage().186 JAIN-SIP sent message from "0:0:0:0:0:0:0:0:5060"to "86.64.162.35:5060" at 1263656727104:
REGISTER sip:ekiga.net SIP/2.0
Call-ID: a549504274cf71f7380f48f71f8da07b@0:0:0:0:0:0:0:0
CSeq: 4 REGISTER
From: <sip:username@ekiga.net>;tag=733b8517
To: <sip:username@ekiga.net>
Via: SIP/2.0/UDP 192.168.1.95:5060;branch=z9hG4bK531ee5aab8307ece2467ac05716f7f96
Max-Forwards: 70
User-Agent: SIP Communicator1.0-alpha3-nightly.build.2338Linux
Expires: 3600
Contact: "username" <sip:username@192.168.1.95:5060;transport=udp;registering_acc=ekiga_net>;expires=3600
Content-Length: 0

16:45:27.191 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: UDPMessageChannel: processIncomingDataPacket : peerAddress = 86.64.162.35/5060 Length = 387
16:45:27.193 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: acquireSem [[[[gov.nist.javax.sip.stack.SIPClientTransaction@2ed88e44
16:45:27.194 FEINER: impl.protocol.sip.SipLogger.logStackTrace().41 JAIN-SIP stack trace
java.lang.Throwable
  at net.java.sip.communicator.impl.protocol.sip.SipLogger.logStackTrace(SipLogger.java:41)
  at gov.nist.javax.sip.stack.SIPTransaction.acquireSem(SIPTransaction.java:1158)
  at gov.nist.javax.sip.stack.SIPTransactionStack.newSIPServerResponse(SIPTransactionStack.java:1176)
  at gov.nist.javax.sip.stack.UDPMessageChannel.processMessage(UDPMessageChannel.java:483)
  at gov.nist.javax.sip.stack.UDPMessageChannel.processIncomingDataPacket(UDPMessageChannel.java:414)
  at gov.nist.javax.sip.stack.UDPMessageChannel.run(UDPMessageChannel.java:258)
  at java.lang.Thread.run(Thread.java:636)
16:45:28.195 FEIN: impl.protocol.sip.SipLogger.logDebug().81 Debug output from the JAIN-SIP stack: acquireSem() returning : false
16:45:28.196 FEINER: impl.protocol.sip.SipLogger.logMessage().209 JAIN-SIP received message from "86.64.162.35:5060" to "0:0:0:0:0:0:0:0:5060" at 1263656728195 (status: before processing):
SIP/2.0 606 Not Acceptable
Call-ID: a549504274cf71f7380f48f71f8da07b@0:0:0:0:0:0:0:0
CSeq: 4 REGISTER
From: <sip:username@ekiga.net>;tag=733b8517
To: <sip:username@ekiga.net>;tag=c64e1f832a41ec1c1f4e5673ac5b80f6.df3e
Via: SIP/2.0/UDP 192.168.1.95:5060;branch=z9hG4bK531ee5aab8307ece2467ac05716f7f96;received=78.55.3.82
Server: Kamailio (1.5.3-notls (i386/linux))
Content-Length: 0

bye,
martin.

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
SIP Communicator
emcho@sip-communicator.org PHONE: +33.1.77.62.43.30
http://sip-communicator.org FAX: +33.1.77.62.47.31

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#3

Hej Emil,

···

On Sun, 17 Jan 2010 15:19:31 +0100 Emil Ivov wrote:

I am afraid we don't consider this to be an issue with SIP
Communicator :frowning:

You can have a look here for a few more details explanation:

https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=435

Maybe we should try to sort this out with the ekiga.net maintainers
(provided they are willing to). Anyone wants to serve as liaison?

Thank you for your answer. I will ask there and will report back if I
get an answer.

Bye,
martin.


#4

Martin Schaaf написа:

Hej Emil,

I am afraid we don't consider this to be an issue with SIP
Communicator :frowning:

You can have a look here for a few more details explanation:

https://sip-communicator.dev.java.net/issues/show_bug.cgi?id=435

Maybe we should try to sort this out with the ekiga.net maintainers
(provided they are willing to). Anyone wants to serve as liaison?

Thank you for your answer. I will ask there and will report back if I
get an answer.

Thanks Martin. Don't hesitate to let us know in case you need assistance
in explaining the problem. Feel free to CC our dev list (or me) in your
post to their lists if you wish.

Cheers,
Emil

···

On Sun, 17 Jan 2010 15:19:31 +0100 Emil Ivov wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#5

They are not in the repository. I saw that the rest of architectures have 2346 built. But Debian has
only the builds up to 2343. Is there a problem with the build system?

Kertesz Laszlo

···

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net


#6

Yes, there is some problem with the download server, will be fixing it
shortly.
Sorry for the problems

···

On Mon, Jan 18, 2010 at 12:46 PM, Kertesz Laszlo < laszlo.kertesz@infobenefic.ro> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

They are not in the repository. I saw that the rest of architectures have
2346 built. But Debian has
only the builds up to 2343. Is there a problem with the build system?

Kertesz Laszlo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktUPAoACgkQrlZ/rySPZHpX3wCcDhmoyR/sg5cflACQuwF11NKG
E64An1W3lIyGO7ZSklnIuOySS+VOH1Gm
=6Y7X
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net