Re: [Openbts-discuss] WARNING: cannot parse SIP message

[Kurtis H. <khe...@cs...>]

Ok, after taking a look at some of these issues, I first think you
should rebase onto the most recent version of OpenBTS. There's a small
bug you're starting with that seems to be causing a lot of issues.
Basically, your asterisk is going very very slowly, and not responding
with a 180 RINGING before the timeout goes off. This causes OpenBTS to
resend the invite, and things get confused from there.

We've made a change that causes OpenBTS to not resend messages when we
receive a 100 TRYING. That may help.

On Sun, Jul 1, 2012 at 3:48 PM, Kali M. <m.k...@ya...> wrote:
> I forgot to add file c and d...
>
>
> ----- Original Message -----
> Hello,
> Please find attached wireshark trace .
> File a.pcap - user 7002 try to call to user 7001, but 7002 ends call before 7001 pick up.
> File b.pcap???- user 7002 try to call to user 7001, but 7001 has power off handset
> File c.pcap?- user 7002 try to call to user 7001, user 7001 has power on handset, but connection is not established and after 7001 end call,command calls from OpenBTS CLI shows 1 transaction with GSMState=Null and SIPState=Canceled
>
> After change in Asterisk dialplan, which causes hangup call after 10 seconds ( exten => _N.,n,Dial(SIP/${Name}@${IPAddr}:5062,10) ):
> File d.pcap - user 7001 try to call to user 7002, but 7002 not pick up in 10 seconds and Asterisk end call
>
> Thanks for any help
>
> Best regards,
> Kali M.
>
>
> From: Kurtis Heimerl <khe...@cs...>
> To: Kali M. <m.k...@ya...>
> Cc: Thomas Tsou <tt...@vt...>; "ope...@li..." <ope...@li...>
> Sent: Tuesday, 26 June 2012, 3:31
> Subject: Re: [Openbts-discuss] WARNING: cannot parse SIP message
>
> That's a pretty reasonable guess.
>
> On Mon, Jun 25, 2012 at 1:42 PM, Kali M. <m.k...@ya...> wrote:
>> Hi,
>> Yes, I use most recent version.
>> Unfortunately I'm out of office now and I can't provide wireshark trace.
>> Additionally, I remember also that I receive few consecutive messages: "426: Request CANCEL sip:IMSIXXXXXXXXXXX@127.0.0.1:5062" from src port 5060 (Asterisk) to port 5062 (OpenBTS)(I don't remember IMSI) number). I will send wireshark trace when I came back to office.
>>
>> I think that problem is with order in exchanging SIP messages between OpenBTS and Asterisk. Am I right?
>>
>> Best regards,
>> Kali M.
>>
>> ________________________________
>> From: Thomas Tsou <tt...@vt...>
>> To: Kurtis Heimerl <khe...@cs...>
>> Cc: Kali M. <m.k...@ya...>; "ope...@li..." <ope...@li...>
>> Sent: Monday, 25 June 2012, 20:01
>> Subject: Re: [Openbts-discuss] WARNING: cannot parse SIP message
>>
>> On Mon, Jun 25, 2012 at 1:48 PM, Kurtis Heimerl
>> <khe...@cs...> wrote:
>>> First, I'm not sure about the ttsou branch, but I think Thomas always
>>> keeps it up to date. Have you made sure you have the most recent
>>> version?
>>
>> Yes, the master branch is just a git mirror of svn trunk.
>>
>>   Thomas
>>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Openbts-discuss mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openbts-discuss
>