[jitsi-users] SIP Info 501 not implemented


#1

Hi,

Thanks for long response.
I will try to do what you explain
even if it seems a little complicated for my knowledge.
Maybe it will
take some time. If I have something significant I will come back
here.

Regards,
Joël

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

···

Le 22/11/2013 15:32, Emil Ivov a écrit :

_______________________________________________

users mailing list

users@jitsi.org

Unsubscribe instructions and other list options:

http://lists.jitsi.org/mailman/listinfo/users


#2

It should be relatively straightforward. Don't hesitate to ask if you have any questions.

Cheers,
Emil

···

On 27.11.13, 19:00, Joël wrote:

Hi,

Thanks for long response.
I will try to do what you explain even if it seems a little complicated
for my knowledge.
Maybe it will take some time. If I have something significant I will
come back here.

Regards,
Joël

Le 22/11/2013 15:32, Emil Ivov a écrit :
> 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
>

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

--
https://jitsi.org


#3

Hi,

We don't have yet the response from our maintener about this case.

So I also modified ProtocolProviderServiceSipImpl.java file and compile it with ant, now jitsi works fine with aastra.

Regards,
Adrien

Le 27/11/13 21:08, Emil Ivov a �crit :

···

It should be relatively straightforward. Don't hesitate to ask if you
have any questions.

Cheers,
Emil

On 27.11.13, 19:00, Jo�l wrote:

Hi,

Thanks for long response.
I will try to do what you explain even if it seems a little complicated
for my knowledge.
Maybe it will take some time. If I have something significant I will
come back here.

Regards,
Jo�l

Le 22/11/2013 15:32, Emil Ivov a �crit :
> 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
>

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