Is there a way to have multiple sip addresses for one account in serweb? For example, if a group or business wanted to have one login/account to view the activity/preferences for all of their sip addresses.
Thanks! - Daryl
Hi all,
I have a very urgent problem I should solve ASAP but I don't know how to do it. May one of you can help me.
I am using the stable version of SER v.0.8.14 and I would like to enable presence service. I have loaded the pa.so module and added the typical lines to process the SUBSCRIBEs in the SER to provide this capability:
if (method=="SUBSCRIBE"){ if (t_newtran()){ handle_subscription("registrar"); break; }; };
However each time the SIP endpoint sends a SUBSCRIBE message the SER replies with a 400 Bad Request. According to the LOGs there must be a problem in parsing the header of the message in SER.
Please, if there is somebody who can give a clue to know what's wrong I would appreciate it a lot because this problem is affecting seriously to the development of my project.l
Thanks in advance.
Victor
I never heard of someone who successfully used the pa module :-(
Which clients do you use? Probably you have to extend the pa module to support your client.
klaus
Victor Huertas Garcia wrote:
Hi all,
I have a very urgent problem I should solve ASAP but I don't know how to do it. May one of you can help me.
I am using the stable version of SER v.0.8.14 and I would like to enable presence service. I have loaded the pa.so module and added the typical lines to process the SUBSCRIBEs in the SER to provide this capability:
if (method=="SUBSCRIBE"){ if (t_newtran()){ handle_subscription("registrar"); break; }; };
However each time the SIP endpoint sends a SUBSCRIBE message the SER replies with a 400 Bad Request. According to the LOGs there must be a problem in parsing the header of the message in SER.
Please, if there is somebody who can give a clue to know what's wrong I would appreciate it a lot because this problem is affecting seriously to the development of my project.l
Thanks in advance.
Victor
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
I use Windows Messenger 4.7 and EyeBeam v1.1. and none have worked at all.
How could I extend the pa module using the SER v0.8.14? Do I take the pa module from the cvs? Do you know if it is going to work is this version of SER?
Thanks
Victor
From: Klaus Darilion klaus.mailinglists@pernau.at To: Victor Huertas Garcia vhuertas@hotmail.com CC: serusers@lists.iptel.org Subject: Re: [Serusers] URGENT!! SUBSCRIBE message handling failure in SER v0.8.14!!! Date: Thu, 30 Jun 2005 18:36:32 +0200
I never heard of someone who successfully used the pa module :-(
Which clients do you use? Probably you have to extend the pa module to support your client.
klaus
Victor Huertas Garcia wrote:
Hi all,
I have a very urgent problem I should solve ASAP but I don't know how to do it. May one of you can help me.
I am using the stable version of SER v.0.8.14 and I would like to enable presence service. I have loaded the pa.so module and added the typical lines to process the SUBSCRIBEs in the SER to provide this capability:
if (method=="SUBSCRIBE"){ if (t_newtran()){ handle_subscription("registrar"); break; }; };
However each time the SIP endpoint sends a SUBSCRIBE message the SER replies with a 400 Bad Request. According to the LOGs there must be a problem in parsing the header of the message in SER.
Please, if there is somebody who can give a clue to know what's wrong I would appreciate it a lot because this problem is affecting seriously to the development of my project.l
Thanks in advance.
Victor
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
On 30-06-2005 18:36, Klaus Darilion wrote:
I never heard of someone who successfully used the pa module :-(
I did. And I know of several people/companies using it. The problem is that there are so many SIMPLE specifications and drafts that it would take a really long time to implement it properly. And also it is hard to do you have no reasonable user agents for testing.
Jan.
Which clients do you use? Probably you have to extend the pa module to support your client.
klaus
Victor Huertas Garcia wrote:
Hi all,
I have a very urgent problem I should solve ASAP but I don't know how to do it. May one of you can help me.
I am using the stable version of SER v.0.8.14 and I would like to enable presence service. I have loaded the pa.so module and added the typical lines to process the SUBSCRIBEs in the SER to provide this capability:
if (method=="SUBSCRIBE"){ if (t_newtran()){ handle_subscription("registrar"); break; }; };
However each time the SIP endpoint sends a SUBSCRIBE message the SER replies with a 400 Bad Request. According to the LOGs there must be a problem in parsing the header of the message in SER.
Please, if there is somebody who can give a clue to know what's wrong I would appreciate it a lot because this problem is affecting seriously to the development of my project.l
Thanks in advance.
Victor
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi Jan!
Can you please name some user agents which are known to work?
regards, klaus
Jan Janak wrote:
On 30-06-2005 18:36, Klaus Darilion wrote:
I never heard of someone who successfully used the pa module :-(
I did. And I know of several people/companies using it. The problem is that there are so many SIMPLE specifications and drafts that it would take a really long time to implement it properly. And also it is hard to do you have no reasonable user agents for testing.
Jan.Which clients do you use? Probably you have to extend the pa module to support your client.
klaus
Victor Huertas Garcia wrote:
Hi all,
I have a very urgent problem I should solve ASAP but I don't know how to do it. May one of you can help me.
I am using the stable version of SER v.0.8.14 and I would like to enable presence service. I have loaded the pa.so module and added the typical lines to process the SUBSCRIBEs in the SER to provide this capability:
if (method=="SUBSCRIBE"){ if (t_newtran()){ handle_subscription("registrar"); break; }; };
However each time the SIP endpoint sends a SUBSCRIBE message the SER replies with a 400 Bad Request. According to the LOGs there must be a problem in parsing the header of the message in SER.
Please, if there is somebody who can give a clue to know what's wrong I would appreciate it a lot because this problem is affecting seriously to the development of my project.l
Thanks in advance.
Victor
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
kphone and Eyebeam to some extent.
Jan.
On 01-07-2005 08:54, Klaus Darilion wrote:
Hi Jan!
Can you please name some user agents which are known to work?
regards, klaus
Jan Janak wrote:
On 30-06-2005 18:36, Klaus Darilion wrote:
I never heard of someone who successfully used the pa module :-(
I did. And I know of several people/companies using it. The problem is that there are so many SIMPLE specifications and drafts that it would take a really long time to implement it properly. And also it is hard to do you have no reasonable user agents for testing.
Jan.
Which clients do you use? Probably you have to extend the pa module to support your client.
klaus
Victor Huertas Garcia wrote:
Hi all,
I have a very urgent problem I should solve ASAP but I don't know how to do it. May one of you can help me.
I am using the stable version of SER v.0.8.14 and I would like to enable presence service. I have loaded the pa.so module and added the typical lines to process the SUBSCRIBEs in the SER to provide this capability:
if (method=="SUBSCRIBE"){ if (t_newtran()){ handle_subscription("registrar"); break; }; };
However each time the SIP endpoint sends a SUBSCRIBE message the SER replies with a 400 Bad Request. According to the LOGs there must be a problem in parsing the header of the message in SER.
Please, if there is somebody who can give a clue to know what's wrong I would appreciate it a lot because this problem is affecting seriously to the development of my project.l
Thanks in advance.
Victor
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi Jan,
I haven't tested Kphone yet but regarding EyeBeam, it doesn't work. It would be good to know what software is using these companies you told us...
Regards
Victor
From: Jan Janak jan@iptel.org To: Klaus Darilion klaus.mailinglists@pernau.at CC: Victor Huertas Garcia vhuertas@hotmail.com, serusers@lists.iptel.org Subject: Re: [Serusers] URGENT!! SUBSCRIBE message handling failure in SER v0.8.14!!! Date: Fri, 1 Jul 2005 10:49:23 +0200
kphone and Eyebeam to some extent.
Jan.
On 01-07-2005 08:54, Klaus Darilion wrote:
Hi Jan!
Can you please name some user agents which are known to work?
regards, klaus
Jan Janak wrote:
On 30-06-2005 18:36, Klaus Darilion wrote:
I never heard of someone who successfully used the pa module :-(
I did. And I know of several people/companies using it. The problem
is
that there are so many SIMPLE specifications and drafts that it would take a really long time to implement it properly. And also it is hard to do you have no reasonable user agents for testing.
Jan.
Which clients do you use? Probably you have to extend the pa module to support your client.
klaus
Victor Huertas Garcia wrote:
Hi all,
I have a very urgent problem I should solve ASAP but I don't know how
to
do it. May one of you can help me.
I am using the stable version of SER v.0.8.14 and I would like to
enable
presence service. I have loaded the pa.so module and added the
typical
lines to process the SUBSCRIBEs in the SER to provide this
capability:
if (method=="SUBSCRIBE"){ if (t_newtran()){ handle_subscription("registrar"); break; }; };
However each time the SIP endpoint sends a SUBSCRIBE message the SER replies with a 400 Bad Request. According to the LOGs there must be a problem in parsing the header of the message in SER.
Please, if there is somebody who can give a clue to know what's wrong
I
would appreciate it a lot because this problem is affecting seriously
to
the development of my project.l
Thanks in advance.
Victor
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Hi all,
I am testing the Instant Message Service with the SER v0.8.14 and I see that it routes them correctly towards the destination user agent. However, what I have seen is a tremendous imcompatibility between user agents of different vendors.
Here just a bit of this:
IM between two Windows Messenger 4.7.
What I see it that the very first MESSAGE in the conversation is sent towards the SER and it routes it perfectly but the subsequent MESSAGES are exchange between both Messengers directly!!! It is weird... but this is how it is working.
IM between Window Messenger 4.7 and EyeBeam v1.1
The EyeBeam always send the MESSAGES towards the SIP proxy and messenger receive them with no problem. However, when the messenger tries to send a MESSAGE in the conversation it even doesn't send the packet (I tried to capture it with Ethereal and no packet was sent at all) and subsequently tell you that the text message could not be delivered to the destination.
IM between EyeBeam v1.1
No problem at all.
IM involving Windows Messenger 5.1
This version of messenger sends an INVITE to the destination before issuing the MESSAGE. With EyeBeam is a total disaster and the comunication is not possible.
My conclusion is that the SER has not implication in such incompatibility at all and that is a matter of interoperability among vendors and different implementations of SIMPLE. Do you agree?
Thanks in advance
Victor
Victor Huertas Garcia wrote:
Hi all,
I am testing the Instant Message Service with the SER v0.8.14 and I see that it routes them correctly towards the destination user agent. However, what I have seen is a tremendous imcompatibility between user agents of different vendors.
Here just a bit of this:
IM between two Windows Messenger 4.7.
What I see it that the very first MESSAGE in the conversation is sent towards the SER and it routes it perfectly but the subsequent MESSAGES are exchange between both Messengers directly!!! It is weird... but this is how it is working.
IM between Window Messenger 4.7 and EyeBeam v1.1
The EyeBeam always send the MESSAGES towards the SIP proxy and messenger receive them with no problem. However, when the messenger tries to send a MESSAGE in the conversation it even doesn't send the packet (I tried to capture it with Ethereal and no packet was sent at all) and subsequently tell you that the text message could not be delivered to the destination.
IM between EyeBeam v1.1
No problem at all.
IM involving Windows Messenger 5.1
This version of messenger sends an INVITE to the destination before issuing the MESSAGE. With EyeBeam is a total disaster and the comunication is not possible.
My conclusion is that the SER has not implication in such incompatibility at all and that is a matter of interoperability among vendors and different implementations of SIMPLE. Do you agree?
Correct!
Some notes: WM 4.7 replies with a Contact: header in the 200 OK to MESSAGE. This is not allowed according to the MESSAGE RFC, but WM uses this contact for further messages to this user. I think you can bypass this problem by using record_route.
WM 5.1: You can force WM 5.1 to fall back to "old mode" by catching the INVITEs in ser and reply with 4xx. But 5.1 wont accept MESSAGE without prior INVITE :-(
regards, klaus
Could you tell me some reasonable user agents for testing this feature? I have Windows Messenger 4.7 and 5.1 and EyeBeam v1.1 (X-ten) with no success at all? Always the same reply from SER (400 Bad REquest: Error parsing headers)
Thank you for your answer...
Victor
From: Jan Janak jan@iptel.org To: Klaus Darilion klaus.mailinglists@pernau.at CC: Victor Huertas Garcia vhuertas@hotmail.com, serusers@lists.iptel.org Subject: Re: [Serusers] URGENT!! SUBSCRIBE message handling failure in SER v0.8.14!!! Date: Fri, 1 Jul 2005 01:08:51 +0200
On 30-06-2005 18:36, Klaus Darilion wrote:
I never heard of someone who successfully used the pa module :-(
I did. And I know of several people/companies using it. The problem is that there are so many SIMPLE specifications and drafts that it would take a really long time to implement it properly. And also it is hard to do you have no reasonable user agents for testing.
Jan.Which clients do you use? Probably you have to extend the pa module to support your client.
klaus
Victor Huertas Garcia wrote:
Hi all,
I have a very urgent problem I should solve ASAP but I don't know how
to
do it. May one of you can help me.
I am using the stable version of SER v.0.8.14 and I would like to
enable
presence service. I have loaded the pa.so module and added the typical lines to process the SUBSCRIBEs in the SER to provide this capability:
if (method=="SUBSCRIBE"){ if (t_newtran()){ handle_subscription("registrar"); break; }; };
However each time the SIP endpoint sends a SUBSCRIBE message the SER replies with a 400 Bad Request. According to the LOGs there must be a problem in parsing the header of the message in SER.
Please, if there is somebody who can give a clue to know what's wrong I would appreciate it a lot because this problem is affecting seriously
to
the development of my project.l
Thanks in advance.
Victor
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Daryl Sanders -
Jan Janak -
Klaus Darilion -
Victor Huertas Garcia