[Rtcomm] [Rtcomm] N800 not doing outgoing SIP calls with Linksys SPA3102

[From: Hugo]

Hi,

ok, thanks for confirming what I though. First of all, Im using the N800 as
my home phone in my new house, so this issue is really disturbing. Is there
a way to quickly get arround this? H.263 is a video format and Im not using
video at the moment, just audio. If I tell the spa3012 to not use video
(dont know if this is posible) or to not use H.263 do you think this would
be enough for the N800 and the spa3012 to work together? Would this need
some tweeking in the N800 as well?

Second, Im a electronic engineer and my computer skills are mainly
self-tough. I know I can check the SIP traffic from and to asterisk with the
Asterisk CLI and the SIP debug option, but asterisk is not going to get the
traffic from the N800 and the spa3012, so how can I get this traffic and
paste it to the maemo bug page?

Thanks

Hugo Baldasano

mikhail.zabaluev at nokia.com ha escrit: 
>

Hi, 
>
>Thanks for your feedback. See my comments below.
>
>>-----Original Message-----
>>From: rtcomm-bounces at maemo.org 
>>[mailto:rtcomm-bounces at maemo.org] On Behalf Of ext Hugo
>>Sent: Wednesday, February 27, 2008 3:17 PM
>>To: rtcomm at maemo.org
>>Subject: [Rtcomm] N800 not doing outgoing SIP calls with 
>>Linksys SPA3102
>>
>>The N800 works with asterisk and registers fine (althoug 
>>asterisk cli keeps
>>on telling me that Got SIP response 405 "Methon Not Allowed" back from
>>N800).
>
>That's because Asterisk insists on sending our client NOTIFY requests it
>didn't subscribe for, nevermind this method wasn't even advertized as
>supported. It should be harmless though.
>
>>Incoming calls is not a problem, they work fine. But the 
>>problem is when
>>making a phone call from the N800. It comunicates with asterisk, and
>>asterisk cli says its bridging the N800 and the spa3102. Then 
>>the N800 says
>>its been a problem with the one server and stops the call. 
>
>We've seen this behavior when calling to Linksys SPA941. The problem is,
>the Linksys sends us an SDP answer where our offered video payload number
>for H.263 is present, but the MIME type is different (even though it seems
>to be really the same format).
>We decided that it's an unsafe assumption generally that the encoder will
>be the same as offered if the MIME type has changed. We could implement a
>static registry of known mistaken type names to achieve interoperability
>with Linksys phones; as of now it's still a pending issue.
>
>>I am no voip expert, and this is my first time setting a 
>>asterisk server,
>>but I will gladly help debuggin sip messages to check what 
>>fails between the
>>N800 and the spa3102, to get them working together.
>
>You're welcome to submit this issue and SIP traffic captures to our bug
>tracking system at
>https://bugs.maemo.org
>
>Best regards,
>  Mikhail
>
>