Hello,
I experienced some strange behaviour of my kphone (V3.11). When I click on register the first time nothing happens (no error message, keeps offline). Clicking the "register" button the second time makes kphone go online.
With the help of Uli and Daniel (thanks !) I could record the network traffic caused by both clicks. In the attached file the first two messages were caused by the first (unsuccessful) click on "register". The next two messages where caught after my second click on register which succeeds. Comparing the two requests I saw the different entries in the "Expires" field (fist 0, second 900) but to my surprise even the call-IDs are the same.
Do you know what is going wrong here ?
BTW: Of course I don't mind to click on register twice in kphone. But right now I have a problem receiving messages with MS Messenger (will describe that separately if I cannot solve it myself) and I'm trying to find out if the reason is within the SER on UA's side. Therefore I cannot ignore anything that looks like an error (e.g. wrong config) in SER or an UA while I'm testing different scenarios.
Thanks, Alex
keeping callid is legal and desirable for REGISTER requests. REGISTER with 0 means unREGISTER, no clue why k-phone sends it...
-jiri
At 12:37 PM 6/4/2003, Alexander Hoffmann wrote:
Hello,
I experienced some strange behaviour of my kphone (V3.11). When I click on register the first time nothing happens (no error message, keeps offline). Clicking the "register" button the second time makes kphone go online.
With the help of Uli and Daniel (thanks !) I could record the network traffic caused by both clicks. In the attached file the first two messages were caused by the first (unsuccessful) click on "register". The next two messages where caught after my second click on register which succeeds. Comparing the two requests I saw the different entries in the "Expires" field (fist 0, second 900) but to my surprise even the call-IDs are the same.
Do you know what is going wrong here ?
BTW: Of course I don't mind to click on register twice in kphone. But right now I have a problem receiving messages with MS Messenger (will describe that separately if I cannot solve it myself) and I'm trying to find out if the reason is within the SER on UA's side. Therefore I cannot ignore anything that looks like an error (e.g. wrong config) in SER or an UA while I'm testing different scenarios.
Thanks, Alex
-- Jiri Kuthan http://iptel.org/~jiri/
Jiri Kuthan writes:
keeping callid is legal and desirable for REGISTER requests. REGISTER with 0 means unREGISTER, no clue why k-phone sends it...
when kphone is registered with the proxy and the user presses unregister button, kphone sends register message with expire=0. that causes unregister button to turn into register button. when the user then presses register button, kphone sends a register message with expire=configured value.
i dont see any problem with that behavior.
-- juha
On 04-06 18:13, Juha Heinanen wrote:
Jiri Kuthan writes:
keeping callid is legal and desirable for REGISTER requests. REGISTER with 0 means unREGISTER, no clue why k-phone sends it...
when kphone is registered with the proxy and the user presses unregister button, kphone sends register message with expire=0. that causes unregister button to turn into register button. when the user then presses register button, kphone sends a register message with expire=configured value.
i dont see any problem with that behavior.
Yes, that's fine. But from time to time you have to press the button twice to trigger register or unregister. This usually happens when I am extensively using kphone for some time. I tried to find out where the problem is but I haven't succeeded yet.
Jan.
Hello,
On 04-06 12:37, Alexander Hoffmann wrote:
Hello,
I experienced some strange behaviour of my kphone (V3.11). When I click on register the first time nothing happens (no error message, keeps offline). Clicking the "register" button the second time makes kphone go online.
Yes, this happens sometimes, try to restart kphone.
With the help of Uli and Daniel (thanks !) I could record the network traffic caused by both clicks. In the attached file the first two messages were caused by the first (unsuccessful) click on "register". The next two messages where caught after my second click on register which succeeds. Comparing the two requests I saw the different entries in the "Expires" field (fist 0, second 900) but to my surprise even the call-IDs are the same.
Yes, the message with Expires: 900 is a registration, the other one is unregistration.
Do you know what is going wrong here ?
Nothing, if you click on register it tries to register. If you click the button again then it unregisters again, and so on. From time to time the button needs to be clicked twice (restart should help).
BTW: Of course I don't mind to click on register twice in kphone. But right now I have a problem receiving messages with MS Messenger (will describe that separately if I cannot solve it myself) and I'm trying to find out if the reason is within the SER on UA's side. Therefore I cannot ignore anything that looks like an error (e.g. wrong config) in SER or an UA while I'm testing different scenarios.
Jiri has replied this already.
Jan.
-
Alexander Hoffmann -
Jan Janak -
Jiri Kuthan -
Juha Heinanen