Koozali.org: home of the SME Server

Obsolete Releases => SME VoIP (Asterisk, SAIL etc) => Topic started by: Teviot on April 29, 2009, 08:29:01 AM

Title: SIP ATA Question ( Log Entry)
Post by: Teviot on April 29, 2009, 08:29:01 AM

Hi S & All

I have a 3 in one ADSL, VOIP & Router (http://www.broadbandgear.com.au/products/broadband-routers/open824rlw-4-port-voip-adsl2-2-iad.html) which i have set up as a general sip client and i am getting the following in the logs

Quote

-- Got SIP response 400 "Bad Subscription-State or Content header or message body" back from 220.xxx.xxx.107

Is this something I should worry about and how can it be fixed?

Title: Re: SIP ATA Question ( Log Entry)
Post by: gippsweb on April 29, 2009, 10:38:47 AM

I've got a Billion 7402VGP at home connected to our box here at work.

We get the same messages in the logs from it. Never seems to bother the operation of the unit, Billion have never bothered to answer any questions about it, so I've never really bothered about it...

Title: Re: SIP ATA Question ( Log Entry)
Post by: Teviot on April 30, 2009, 01:11:41 AM

Thanks gippsweb

Just wondering if anyone else sees the same log entry?

Title: Re: SIP ATA Question ( Log Entry)
Post by: Teviot on April 30, 2009, 03:36:58 AM

An update with the log is as follows

Code: [Select]

  == Spawn extension (mainmenu, h, 1) exited non-zero on 'SIP/09398319-08837030'
    -- Saved useragent "OPEN824RLW VoIP/ADSL2+ Wireless Router (Lifeline) 5.53" for peer 4001
    -- Got SIP response 400 "Bad Subscription-State or Content header or message body" back from 220.xxx.xxx.107
    -- Saved useragent "Linksys/SPA3102-5.1.7(GW)" for peer 2000
    -- Saved useragent "Linksys/PAP2-3.1.22(LS)" for peer 2002
    -- Saved useragent "Linksys/PAP2-3.1.22(LS)" for peer 2001
    -- Saved useragent "Linksys/SPA3102-5.1.7(GW)" for peer telstra
    -- Got SIP response 400 "Bad Subscription-State or Content header or message body" back from 220.xxx.xxx.107
    -- Got SIP response 400 "Bad Subscription-State or Content header or message body" back from 220.xxx.xxx.107
    -- Got SIP response 400 "Bad Subscription-State or Content header or message body" back from 220.xxx.xxx.107
    -- Got SIP response 400 "Bad Subscription-State or Content header or message body" back from 220.xxx.xxx.107
    -- Got SIP response 400 "Bad Subscription-State or Content header or message body" back from 220.xxx.xxx.107
sail*CLI>


Title: Re: SIP ATA Question ( Log Entry)
Post by: SARK devs on April 30, 2009, 11:16:53 AM

SIP rc 400 usually means you are asking the UA(device) for something it doesn't understand.  The actual format of the message text is provided by the UA itself so you really need to ask Linksys what it means.

Either way, in this case, I don,t think it is anything to worry about (assuming he device works and is flowing traffic correctly). 


S

Title: Re: SIP ATA Question ( Log Entry)
Post by: gippsweb on April 30, 2009, 11:27:09 AM

'tis not the Linksys which he is questioning it is the open networks device which uses the same chipset as the Billion 740x vgp/o devices.

We've been having the discussion for a couple of years with Billion, they just keep hoping I'll go away and forget about it (which I pretty much have till now) because they don't/won't answer the question. Billion seem to be more open with questions about it prosucts up to a point, so if they won't discuss it the chance of Open Networks doing so are pretty damn slim..

That being said, myself and quite a few customers have these Billions at home connecting to the Sail boxes at work without any issues.