[sip-comm-dev] SIP stack messages - something is umarked


#1

Hi all,

attached a short console printout that shows some messages of the SIP stack:
Somehow a Dialog wasn't marked - thus I report this to you guys.

Some additional remark regarding the SIP GUI: some time ago the GUI contained
a input field and buttons that enabled a phone call without creating a contact
first. Now this field/buttons are gone (see attached screen shot). How to do
"ad-hoc" phone calls without creating a contact first? I looked through the
menus bit didn't find a menu item for this.

Regards,
Werner

Console printout:

run:
     [java]
     [java] Welcome to Felix
     [java] ================
     [java]
     [java] 19:06:47.980 SCHWERWIEGEND: impl.neomedia.device.DeviceConfiguration.registerCustomRenderers().1005 Failed to register custom Renderer
net.java.sip.communicator.impl.neomedia.jmfext.media.renderer.video.JAWTRenderer with JMF.
     [java] Open log file: /home/werner/devhome/sc-git/jmf.log
     [java] 19:07:31.091 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processDialogTerminated().470 Dialog wasn't marked, please report this to
dev@sip-communicator.dev.java.net
     [java] 19:07:34.520 SCHWERWIEGEND: impl.protocol.sip.OperationSetBasicTelephonySipImpl.processResponse().487 Received error: 408 Request Timeout

     [java] 19:07:42.704 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processDialogTerminated().470 Dialog wasn't marked, please report this to
dev@sip-communicator.dev.java.net
     [java] 19:07:54.330 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processDialogTerminated().470 Dialog wasn't marked, please report this to
dev@sip-communicator.dev.java.net
     [java] 19:08:01.391 SCHWERWIEGEND: impl.protocol.sip.OperationSetBasicTelephonySipImpl.processResponse().487 Received error: 500 I'm terribly sorry, server
error occurred (1/SL)
     [java] 19:08:06.022 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processDialogTerminated().470 Dialog wasn't marked, please report this to
dev@sip-communicator.dev.java.net


#2

Hi Werner,

Now the search field implements this functionality i.e. you type the
address in the search field and if it doesn't match any contact in
your contact list, you get two buttons one of which allows you to make
a call.

Best regards,
Lubo

···

On Sun, May 9, 2010 at 8:19 PM, Werner Dittmann <Werner.Dittmann@t-online.de> wrote:

Some additional remark regarding the SIP GUI: some time ago the GUI contained
a input field and buttons that enabled a phone call without creating a contact
first. Now this field/buttons are gone (see attached screen shot). How to do
"ad-hoc" phone calls without creating a contact first? I looked through the
menus bit didn't find a menu item for this.

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


#3

Hey Werner,

На 09.05.10 19:19, Werner Dittmann написа:

Hi all,

attached a short console printout that shows some messages of the SIP stack:
Somehow a Dialog wasn't marked - thus I report this to you guys.

Are you able to reproduce this? If yes then could you please show us the
related sip messages? I suspect the reason for this is in keep alive
messages that we don't really care about in which case we'd have to turn
down the log level a notch.

Cheers
Emil

···

Some additional remark regarding the SIP GUI: some time ago the GUI contained
a input field and buttons that enabled a phone call without creating a contact
first. Now this field/buttons are gone (see attached screen shot). How to do
"ad-hoc" phone calls without creating a contact first? I looked through the
menus bit didn't find a menu item for this.

Regards,
Werner

Console printout:

run:
     [java]
     [java] Welcome to Felix
     [java] ================
     [java]
     [java] 19:06:47.980 SCHWERWIEGEND: impl.neomedia.device.DeviceConfiguration.registerCustomRenderers().1005 Failed to register custom Renderer
net.java.sip.communicator.impl.neomedia.jmfext.media.renderer.video.JAWTRenderer with JMF.
     [java] Open log file: /home/werner/devhome/sc-git/jmf.log
     [java] 19:07:31.091 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processDialogTerminated().470 Dialog wasn't marked, please report this to
dev@sip-communicator.dev.java.net
     [java] 19:07:34.520 SCHWERWIEGEND: impl.protocol.sip.OperationSetBasicTelephonySipImpl.processResponse().487 Received error: 408 Request Timeout

     [java] 19:07:42.704 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processDialogTerminated().470 Dialog wasn't marked, please report this to
dev@sip-communicator.dev.java.net
     [java] 19:07:54.330 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processDialogTerminated().470 Dialog wasn't marked, please report this to
dev@sip-communicator.dev.java.net
     [java] 19:08:01.391 SCHWERWIEGEND: impl.protocol.sip.OperationSetBasicTelephonySipImpl.processResponse().487 Received error: 500 I'm terribly sorry, server
error occurred (1/SL)
     [java] 19:08:06.022 SCHWERWIEGEND: impl.protocol.sip.SipStackSharing.processDialogTerminated().470 Dialog wasn't marked, please report this to
dev@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

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


#4

Hello everybody,
on Mac OS it is pretty clear (see attachment)
KR/Walter


#5

Lubo, Yana,

thanks for the explanataion. After updating ad-hoc calls using the search
filed work again.

However, to me the behaviour of the search field is somewhat confusing:
when I enter a new destination SC immediately starts to show the history
and after a short time I see the GUI as shown in the attachement
(SipComm1.png).

Some things to note:

- the search field has a magnifying glass at the left hand side - usually
  this is a sign for "search" or "zoom". Well, adding a destination id
  is not always a search.

- when I enter just a single charater I see a contact that does not even
  contain that character (see attached SipComm2.png). Well, the "e" is
  in the domain name of the SIP contact. Also this behaviour is not
  consistent, sometimes the contact field is not shown but only all the
  contacts that contain the character somewhere in their contact name
  or domain name.

- The GUI offers 3 ways to place the call after the contact shows up:
  - the button in the search field
  - the button in the contact field
  - a right click in the contact field
  where the two buttons offer the same functionality, the right click
  works a bit different

Wouldn't it make sense to add a "search button" (for example activate to
magnifying glass as a search toggle button?) to start a search and display
the call history and apply the entered characters as filter? Without
activating a search button take the input as destination and activate the
small call button in the field.

Better yet: have different input fields :slight_smile: as we already had. Overloading
one input field with different functions is not very easy to grasp, in
particular for non-IT people. They like dedicated functions, dedicated simple
to understand buttons, not overloaded functions.

Another topic: check the size of the fonts. The font in the input field for
example is small ( ~10pt?) which is quite small for many people. Make it
bigger please.

Regards,
Werner

···

Am 09.05.2010 19:23, schrieb Lubomir Marinov:

Hi Werner,

Now the search field implements this functionality i.e. you type the
address in the search field and if it doesn't match any contact in
your contact list, you get two buttons one of which allows you to make
a call.

Best regards,
Lubo

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


#6

Hey Werner,

На 10.05.10 20:13, Werner Dittmann написа:

Lubo, Yana,

thanks for the explanataion. After updating ad-hoc calls using the search
filed work again.

However, to me the behaviour of the search field is somewhat confusing:

Indeed, there are still a number of issues with it and Yana is working
on fixing them as I am writing these words. The point of all this
refactoring is to keep SC's UI as simple as possible. I agree that
things feel quite shaky in the process but it's all for a greater good
so pleas bear with us :slight_smile:

when I enter a new destination SC immediately starts to show the history
and after a short time I see the GUI as shown in the attachement
(SipComm1.png).

Yup. It would show whatever contains your string in both your contact
list and call history. The point of showing the history records is to
compensate for the drop down box that we got rid of.

Some things to note:

- the search field has a magnifying glass at the left hand side - usually
  this is a sign for "search" or "zoom". Well, adding a destination id
  is not always a search.

True, and the idea is that this is, above all, a search field. Being
able to call additional numbers is just something that would be of
interest in case of a non-satisfactory search reasult.

- when I enter just a single charater I see a contact that does not even
  contain that character (see attached SipComm2.png). Well, the "e" is
  in the domain name of the SIP contact.

Exactly. We try to match your search string to anything within your
contact addresses, display name, or meta contact display name.

Also this behaviour is not
  consistent, sometimes the contact field is not shown but only all the
  contacts that contain the character somewhere in their contact name
  or domain name.

That's part of the issues that Yana is currently working on. I also have
duplicated contact list results appearing every now and then, but,
hopefully, this would all be taken care of very soon.

- The GUI offers 3 ways to place the call after the contact shows up:
  - the button in the search field
  - the button in the contact field
  - a right click in the contact field
  where the two buttons offer the same functionality

Not quite. The search field button allows you to call the exact string
you've typed through any of your telephony supporting accounts. The
button in the contact field allows you to call the telephony supporting
contacts of the corresponding meta contact _through_their_own_ protocol
provider.

For example, imagine I have an iptel.org and an ippi.fr account. I add
echo@iptel.org to my contact list, then I type echo in the search field.
The small green button allows me to make a call to "echo" through either
ippi.fr or iptel.org, while clicking on the echo contact that just
appeared won't ask me anything and will make a call to echo@iptel.org
through my iptel.org account.

The point of the small green button is to be able to call strings that
are a substring of entries in your contact list without matching them
completely..

, the right click works a bit different

In my case the right click offers exactly the same choices as the green
button on the contact field.

Wouldn't it make sense to add a "search button" (for example activate to
magnifying glass as a search toggle button?) to start a search and display
the call history and apply the entered characters as filter? Without
activating a search button take the input as destination and activate the
small call button in the field.

Better yet: have different input fields :slight_smile: as we already had. Overloading
one input field with different functions is not very easy to grasp, in
particular for non-IT people. They like dedicated functions, dedicated simple
to understand buttons, not overloaded functions.

Well based on the discussions I've be part of the above two options are
generally perceived as more complicated than not having to click
anything at all and just typing. This also seems to be the default mode
of operation for several other popular communications applications.

I do agree that the extra green button is probably a bit clumsy from
that perspective but that's the only thing we could come up with to
address the substring problem.

Another topic: check the size of the fonts. The font in the input field for
example is small ( ~10pt?) which is quite small for many people. Make it
bigger please.

Will do.

Cheers,
Emil

···

Regards,
Werner

Am 09.05.2010 19:23, schrieb Lubomir Marinov:

Hi Werner,

Now the search field implements this functionality i.e. you type the
address in the search field and if it doesn't match any contact in
your contact list, you get two buttons one of which allows you to make
a call.

Best regards,
Lubo

---------------------------------------------------------------------
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

--
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: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net