[jitsi-users] SIP Info 501 not implemented

#1

Hello,

We try to use jitsi with an aastra 5000 as sip server.

After 30 sec the sip server send me a "request: INFO", jitsi respond
"Status: 501 Not implemented" then the server send the request "BYE" and
the call end.

We're not able to establish a call during more than 30sec.

Is there a way that jitsi send a 200 OK instead of an 501 to a SIP INFO
request ?

The aastra 5000 use the sip info as a keep-alive.

Thanks for your answer

Regards
Adrien F.

#2

Can we see a trace?

Also it would be great to ask Astra why they do this. If they use the info
as a keep alive, tearing down the call as a result of a 501 definitely
sounds like a bug worth reporting

--sent from my mobile

···

On 14 Nov 2013 18:25, "adrien" <adrienfirst@gmail.com> wrote:

Hello,

We try to use jitsi with an aastra 5000 as sip server.

After 30 sec the sip server send me a "request: INFO", jitsi respond
"Status: 501 Not implemented" then the server send the request "BYE" and
the call end.

We're not able to establish a call during more than 30sec.

Is there a way that jitsi send a 200 OK instead of an 501 to a SIP INFO
request ?

The aastra 5000 use the sip info as a keep-alive.

Thanks for your answer

Regards
Adrien F.

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

#3

When I start up Jitsi, I keep getting a notice of a message/mail I
received in my talk.google.com account. I go to my gmail accounts and
have eliminated all messages/emails, and I can find no reference to the
message that I am being notified of. How can I stop that notice from
appearing when I open Jitsi?

Thank you for your help.

Pablo

#4

Please find below the trace of the exchange between jitsi and aastra 5000.
We also have an open request with our aastra maintener for this case.

Polycom apparently bypassed this behavior by responding 200 OK:
*When a SIP INFO request is received, the KWS responds with 200 OK. In
previous firmware revisions the KWS responded with 501 Not implemented.
This address a problem reported in [DECTESC-254]. In a setup with an Aastra
5000 PBX, the PBXapparently usesSIP INFO for keep-alive signaling. If the
Aastra did not receive a 200 OK the call was terminated.*
http://kirk.ru/upload/iblock/65f/KIRK_WirelessServer_300_Release_Notes_PCS10.pdf

Thanks
Adrien F

*IP Source: AASTRAIP Destination: JitsiINFO
sip:210002@x.x.ip.jitsi:5060;transport=udp;registering_acc=ip_aastra_0_0
SIP/2.0Via: SIP/2.0/UDP
x.x.ip.aastra:5060;ctxe=00018985;branch=z9hG4bK_2_INFO_0206FFFFDFE2419D_A5000;uuid=d9e0c082c0184e2006a1df8da4d7d996;rportFrom:
"210001 Pierre"
<sip:210001@x.x.ip.aastra>;tag=201DBE62_nab_03DE_isp_02AB_cco_0736_igo_369B_mgt_FFFFTo:
<sip:210002@x.x.ip.jitsi:5060>;tag=7deffe1fCall-ID: 0206FFFFDFE2419DCSeq: 2
INFOMax-Forwards: 70P-Asserted-Identity: "210001 Pierre"
<sip:210001@x.x.ip.aastra>Privacy: noneUser-Agent: A5000 R5.4 SP2 /D700
FRAIP Source: JitsiIP Destination: AASTRASIP/2.0 501 Not implementedTo:
<sip:210002@x.x.ip.jitsi:5060>;tag=7deffe1fVia: SIP/2.0/UDP
x.x.ip.aastra:5060;ctxe=00018985;branch=z9hG4bK_2_INFO_0206FFFFDFE2419D_A5000;uuid=d9e0c082c0184e2006a1df8da4d7d996;rport=5060;received=x.x.ip.aastraCSeq:
2 INFOCall-ID: 0206FFFFDFE2419DFrom: "210001 Pierre"
<sip:210001@x.x.ip.aastra>;tag=201DBE62_nab_03DE_isp_02AB_cco_0736_igo_369B_mgt_FFFFContact:
"210002"
<sip:210002@x.x.ip.jitsi:5060;transport=udp;registering_acc=ip_aastra_0_0>User-Agent:
Jitsi2.3.4905Windows 7IP Source: AASTRAIP Destination: JitsiBYE
sip:210002@x.x.ip.jitsi:5060;transport=udp;registering_acc=ip_aastra_0_0
SIP/2.0Via: SIP/2.0/UDP
x.x.ip.aastra:5060;ctxe=00018985;branch=z9hG4bK_3_BYE_0206FFFFDFE2419D_A5000;uuid=d9e0c082c0184e2006a1df8da4d7d996;rportFrom:
"210001 Pierre"
<sip:210001@x.x.ip.aastra>;tag=201DBE62_nab_03DE_isp_02AB_cco_0736_igo_369B_mgt_FFFFTo:
<sip:210002@x.x.ip.jitsi:5060>;tag=7deffe1fCall-ID: 0206FFFFDFE2419DCSeq: 3
BYEMax-Forwards: 70User-Agent: A5000 R5.4 SP2 /D700 FRAIP Source: JitsiIP
Destination: AASTRASIP/2.0 200 OKTo:
<sip:210002@x.x.ip.jitsi:5060>;tag=7deffe1fVia: SIP/2.0/UDP
x.x.ip.aastra:5060;ctxe=00018985;branch=z9hG4bK_3_BYE_0206FFFFDFE2419D_A5000;uuid=d9e0c082c0184e2006a1df8da4d7d996;rport=5060;received=x.x.ip.aastraCSeq:
3 BYECall-ID: 0206FFFFDFE2419DFrom: "210001 Pierre"
<sip:210001@x.x.ip.aastra>;tag=201DBE62_nab_03DE_isp_02AB_cco_0736_igo_369B_mgt_FFFFContact:
"210002"
<sip:210002@x.x.ip.jitsi:5060;transport=udp;registering_acc=ip_aastra_0_0>User-Agent:
Jitsi2.3.4905Windows 7*

···

2013/11/14 Emil Ivov <emcho@jitsi.org>

Can we see a trace?

Also it would be great to ask Astra why they do this. If they use the info
as a keep alive, tearing down the call as a result of a 501 definitely
sounds like a bug worth reporting

--sent from my mobile
On 14 Nov 2013 18:25, "adrien" <adrienfirst@gmail.com> wrote:

Hello,

We try to use jitsi with an aastra 5000 as sip server.

After 30 sec the sip server send me a "request: INFO", jitsi respond
"Status: 501 Not implemented" then the server send the request "BYE" and
the call end.

We're not able to establish a call during more than 30sec.

Is there a way that jitsi send a 200 OK instead of an 501 to a SIP INFO
request ?

The aastra 5000 use the sip info as a keep-alive.

Thanks for your answer

Regards
Adrien F.

_______________________________________________
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

#5

We could do this ... but it doesn't make much sense. Astra are
clearly in the wrong here, so unless they are doing it intentionally
(e.g. in order to try and break some percentage of third party user
agents) then I don't see why they wouldn't want to fix it. Could you
please keep us posted as they progress your ticket and we will decide
how to act according to that?

Thanks,
Emil

···

On Fri, Nov 15, 2013 at 10:55 AM, adrien <adrienfirst@gmail.com> wrote:

Please find below the trace of the exchange between jitsi and aastra 5000.
We also have an open request with our aastra maintener for this case.

Polycom apparently bypassed this behavior by responding 200 OK:
When a SIP INFO request is received, the KWS responds with 200 OK. In
previous firmware revisions the KWS responded with 501 Not implemented. This
address a problem reported in [DECTESC-254]. In a setup with an Aastra 5000
PBX, the PBXapparently usesSIP INFO for keep-alive signaling. If the Aastra
did not receive a 200 OK the call was terminated.
http://kirk.ru/upload/iblock/65f/KIRK_WirelessServer_300_Release_Notes_PCS10.pdf

Thanks
Adrien F

IP Source: AASTRA
IP Destination: Jitsi
INFO
sip:210002@x.x.ip.jitsi:5060;transport=udp;registering_acc=ip_aastra_0_0
SIP/2.0
Via: SIP/2.0/UDP
x.x.ip.aastra:5060;ctxe=00018985;branch=z9hG4bK_2_INFO_0206FFFFDFE2419D_A5000;uuid=d9e0c082c0184e2006a1df8da4d7d996;rport
From: "210001 Pierre"
<sip:210001@x.x.ip.aastra>;tag=201DBE62_nab_03DE_isp_02AB_cco_0736_igo_369B_mgt_FFFF
To: <sip:210002@x.x.ip.jitsi:5060>;tag=7deffe1f
Call-ID: 0206FFFFDFE2419D
CSeq: 2 INFO
Max-Forwards: 70
P-Asserted-Identity: "210001 Pierre" <sip:210001@x.x.ip.aastra>
Privacy: none
User-Agent: A5000 R5.4 SP2 /D700 FRA

IP Source: Jitsi
IP Destination: AASTRA
SIP/2.0 501 Not implemented
To: <sip:210002@x.x.ip.jitsi:5060>;tag=7deffe1f
Via: SIP/2.0/UDP
x.x.ip.aastra:5060;ctxe=00018985;branch=z9hG4bK_2_INFO_0206FFFFDFE2419D_A5000;uuid=d9e0c082c0184e2006a1df8da4d7d996;rport=5060;received=x.x.ip.aastra
CSeq: 2 INFO
Call-ID: 0206FFFFDFE2419D
From: "210001 Pierre"
<sip:210001@x.x.ip.aastra>;tag=201DBE62_nab_03DE_isp_02AB_cco_0736_igo_369B_mgt_FFFF
Contact: "210002"
<sip:210002@x.x.ip.jitsi:5060;transport=udp;registering_acc=ip_aastra_0_0>
User-Agent: Jitsi2.3.4905Windows 7

IP Source: AASTRA
IP Destination: Jitsi
BYE sip:210002@x.x.ip.jitsi:5060;transport=udp;registering_acc=ip_aastra_0_0
SIP/2.0
Via: SIP/2.0/UDP
x.x.ip.aastra:5060;ctxe=00018985;branch=z9hG4bK_3_BYE_0206FFFFDFE2419D_A5000;uuid=d9e0c082c0184e2006a1df8da4d7d996;rport
From: "210001 Pierre"
<sip:210001@x.x.ip.aastra>;tag=201DBE62_nab_03DE_isp_02AB_cco_0736_igo_369B_mgt_FFFF
To: <sip:210002@x.x.ip.jitsi:5060>;tag=7deffe1f
Call-ID: 0206FFFFDFE2419D
CSeq: 3 BYE
Max-Forwards: 70
User-Agent: A5000 R5.4 SP2 /D700 FRA

IP Source: Jitsi
IP Destination: AASTRA
SIP/2.0 200 OK
To: <sip:210002@x.x.ip.jitsi:5060>;tag=7deffe1f
Via: SIP/2.0/UDP
x.x.ip.aastra:5060;ctxe=00018985;branch=z9hG4bK_3_BYE_0206FFFFDFE2419D_A5000;uuid=d9e0c082c0184e2006a1df8da4d7d996;rport=5060;received=x.x.ip.aastra
CSeq: 3 BYE
Call-ID: 0206FFFFDFE2419D
From: "210001 Pierre"
<sip:210001@x.x.ip.aastra>;tag=201DBE62_nab_03DE_isp_02AB_cco_0736_igo_369B_mgt_FFFF
Contact: "210002"
<sip:210002@x.x.ip.jitsi:5060;transport=udp;registering_acc=ip_aastra_0_0>
User-Agent: Jitsi2.3.4905Windows 7

2013/11/14 Emil Ivov <emcho@jitsi.org>

Can we see a trace?

Also it would be great to ask Astra why they do this. If they use the info
as a keep alive, tearing down the call as a result of a 501 definitely
sounds like a bug worth reporting

--sent from my mobile

On 14 Nov 2013 18:25, "adrien" <adrienfirst@gmail.com> wrote:

Hello,

We try to use jitsi with an aastra 5000 as sip server.

After 30 sec the sip server send me a "request: INFO", jitsi respond
"Status: 501 Not implemented" then the server send the request "BYE" and the
call end.

We're not able to establish a call during more than 30sec.

Is there a way that jitsi send a 200 OK instead of an 501 to a SIP INFO
request ?

The aastra 5000 use the sip info as a keep-alive.

Thanks for your answer

Regards
Adrien F.

_______________________________________________
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

_______________________________________________
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