[jitsi-users] SIP Info 501 not implemented


#1

Hi,

We have exactly the same problem with Aastra A5000 version
5.4. With version 5.1 there were no problems.

I have also open a case
with our maintener.

Have you got any response from Aastra ?

Thanks,

Joël


#2

Hi,

While waiting a answer from AASTRA I have downloaded the
source code of Jitsi and made a few modifications to answer the way
Polycom does (send 200 ok when receving a INFO request ).

It works
well with our AASTRA A5000 callserver and we will test it a few days.

I am not at all a developper and I think my way of doing that is
awfull but if someone want to test.

What I did:

In file
jitsi-src-2.2.4603.9615srcnetjavasipcommunicatorimplprotocolsipProtocolProviderServiceSipImpl.java

Line 948 :

replace:

Response response =
this.getMessageFactory().createResponse(

Response.NOT_IMPLEMENTED,
request);

serverTransaction.sendResponse(response);

with:

if (
method.equals(Request.INFO))

{

Response response =
this.getMessageFactory().createResponse(

Response.OK, request);

serverTransaction.sendResponse(response);

}

else

{

Response
response = this.getMessageFactory().createResponse(

Response.NOT_IMPLEMENTED, request);

serverTransaction.sendResponse(response);

}

If needed I can give
the resulting class file or jar package.

Once compiled I have juste
taken the protocol-sip.jar file and put it in the C:Program
FilesJitsisc-bundles of jitsi installation.

Maybe AASTRA will correct
that problem in a new release.

Thanks to Jitsi developper for their
job on this project. I have been able to folow their instructions and
build from the source in a few hours. I did not think it was possible so
easyly.

Regards,

Joël


#3

Hey Joel,

Thanks for sending this. I still think that Aastra should fix their
issue ... but if they haven't responded to it yet, then ok ... let's
try to work around it.

In case you are willing to spend a little bit more time on this, the
best way to do it would be to implement a method processor and
register it in the protocol provider service using:
registerMethodProcessor();

You can have a look at
net.java.sip.communicator.impl.protocol.sip.ClientCapabilities which
handles OPTIONS requests. What you need to do is pretty much the same
thing (except for the content of the processRequest() method).

In processRequest() you would basically have to construct and send the OK.

Now, note that we already have an INFO method processor:
dtmf/DTMFInfo.java. It handles incoming DTMF tones and generates
events that other bundles can use for whatever. This will have to
continue working so in your new class (e.g. InfoKeepAliveProcessor)
you could make sure that you only handle INFO requests with no
content. Feel free to add javadocs that explain how this is a
workaround for AASTRA behaviour.

Let me know if you have any questions.

Cheers,
Emil

P.S. If you are interested in doing this we'd also need you to sign
our contributor agreement: https://jitsi.org/faq/patch
You can send this to me personally

···

On Fri, Nov 22, 2013 at 12:38 PM, Joël <jproal@nordnet.fr> wrote:

Hi,

While waiting a answer from AASTRA I have downloaded the source code of
Jitsi and made a few modifications to answer the way Polycom does (send 200
ok when receving a INFO request ).

It works well with our AASTRA A5000 callserver and we will test it a few
days.

I am not at all a developper and I think my way of doing that is awfull but
if someone want to test.

What I did:

In file
\jitsi-src-2.2.4603.9615\src\net\java\sip\communicator\impl\protocol\sip\ProtocolProviderServiceSipImpl.java

Line 948 :

replace:

                   Response response =
this.getMessageFactory().createResponse(

                                    Response.NOT_IMPLEMENTED, request);

                    serverTransaction.sendResponse(response);

with:

if ( method.equals(Request.INFO))

                                                           {

Response response = this.getMessageFactory().createResponse(

Response.OK, request);

serverTransaction.sendResponse(response);

                                                           }

                                                           else

                                                           {

Response response = this.getMessageFactory().createResponse(

Response.NOT_IMPLEMENTED, request);

serverTransaction.sendResponse(response);

                                                           }

If needed I can give the resulting class file or jar package.

Once compiled I have juste taken the protocol-sip.jar file and put it in the
C:\Program Files\Jitsi\sc-bundles of jitsi installation.

Maybe AASTRA will correct that problem in a new release.

Thanks to Jitsi developper for their job on this project. I have been able
to folow their instructions and build from the source in a few hours. I did
not think it was possible so easyly.

Regards,

Joël

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
https://jitsi.org FAX: +33.1.77.62.47.31


#4

You may wait even longer now that Aastra = Mitel :wink:

···

On Fri, Nov 22, 2013 at 9:32 AM, Emil Ivov <emcho@jitsi.org> wrote:

Hey Joel,

Thanks for sending this. I still think that Aastra should fix their
issue ... but if they haven't responded to it yet, then ok ... let's
try to work around it.

In case you are willing to spend a little bit more time on this, the
best way to do it would be to implement a method processor and
register it in the protocol provider service using:
registerMethodProcessor();

You can have a look at
net.java.sip.communicator.impl.protocol.sip.ClientCapabilities which
handles OPTIONS requests. What you need to do is pretty much the same
thing (except for the content of the processRequest() method).

In processRequest() you would basically have to construct and send the OK.

Now, note that we already have an INFO method processor:
dtmf/DTMFInfo.java. It handles incoming DTMF tones and generates
events that other bundles can use for whatever. This will have to
continue working so in your new class (e.g. InfoKeepAliveProcessor)
you could make sure that you only handle INFO requests with no
content. Feel free to add javadocs that explain how this is a
workaround for AASTRA behaviour.

Let me know if you have any questions.

Cheers,
Emil

P.S. If you are interested in doing this we'd also need you to sign
our contributor agreement: https://jitsi.org/faq/patch
You can send this to me personally

On Fri, Nov 22, 2013 at 12:38 PM, Joël <jproal@nordnet.fr> wrote:
> Hi,
>
> While waiting a answer from AASTRA I have downloaded the source code of
> Jitsi and made a few modifications to answer the way Polycom does (send
200
> ok when receving a INFO request ).
>
> It works well with our AASTRA A5000 callserver and we will test it a few
> days.
>
> I am not at all a developper and I think my way of doing that is awfull
but
> if someone want to test.
>
> What I did:
>
> In file
> \jitsi-src-2.2.4603.9615
\src\net\java\sip\communicator\impl\protocol\sip\ProtocolProviderServiceSipImpl.java
>
> Line 948 :
>
> replace:
>
> Response response =
> this.getMessageFactory().createResponse(
>
> Response.NOT_IMPLEMENTED, request);
>
> serverTransaction.sendResponse(response);
>
>
>
> with:
>
> if ( method.equals(Request.INFO))
>
> {
>
>
> Response response = this.getMessageFactory().createResponse(
>
>
> Response.OK, request);
>
>
> serverTransaction.sendResponse(response);
>
> }
>
> else
>
> {
>
>
> Response response = this.getMessageFactory().createResponse(
>
>
> Response.NOT_IMPLEMENTED, request);
>
>
> serverTransaction.sendResponse(response);
>
> }
>
> If needed I can give the resulting class file or jar package.
>
> Once compiled I have juste taken the protocol-sip.jar file and put it in
the
> C:\Program Files\Jitsi\sc-bundles of jitsi installation.
>
> Maybe AASTRA will correct that problem in a new release.
>
> Thanks to Jitsi developper for their job on this project. I have been
able
> to folow their instructions and build from the source in a few hours. I
did
> not think it was possible so easyly.
>
> Regards,
>
> Joël
>
>
>
>
>
>
>
>
>
> _______________________________________________
> users mailing list
> users@jitsi.org
> Unsubscribe instructions and other list options:
> http://lists.jitsi.org/mailman/listinfo/users

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
https://jitsi.org FAX: +33.1.77.62.47.31

_______________________________________________
users mailing list
users@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/users

--
There are 10 kinds of people in this world, those who understand binary and
those who don't.

mpicher@gmail.com
blog: http://www.sipxecs.info
call: sip:mpicher@sipxecs.info