[asterisk-users] 423 "Interval Too Brief" and expiry settings insip.conf

[Robert Rozman]

----- Original Message ----- 
From: "Robert Rozman" <robert.rozman at comutel.si>
To: <asterisk-users at lists.digium.com>
Sent: Thursday, March 20, 2008 7:40 PM
Subject: [asterisk-users] 423 "Interval Too Brief" and expiry settings 
insip.conf


> Hi,
>
> I'm getting this error when registering with SIP server using Asterisk
> 1.4.10 and Freepbx...
>
> I'm getting this error no matter what I try to setup in sip.conf :
> - I'm getting confused whether options are maxexpirey=36000 or
> maxexpiry=36000  ?
> - Can I solve this with some settings in sip.conf or is this problem 
> harder
> ?
> - I've read something about Asterisk's bug on this error, but am not sure 
> it
> really patching is necessary or can be avoided with different settings ?
>
> Thanks in advance,
>
> regards,
>
> Rob.
>
> --- (10 headers 0 lines) ---
>    -- Got SIP response 423 "Interval Too Brief" back from xxx.xxx.xxx.xxx
> Really destroying SIP dialog 
> '5d7cec216c2e56db5bdb83c16896467b at 192.168.0.1'
> Method: REGISTER
>
>
> [Mar 20 18:34:49] VERBOSE[7840] logger.c:
> <--- SIP read from  xxx.xxx.xxx.xxx:5060 --->
> SIP/2.0 423 Interval Too Brief
> Call-ID: 522ef0f7118f00d83d42b1082882fc10 at 192.168.0.1
> CSeq: 174 REGISTER
> From: <sip:XXXXXXXX@ xxx.xxx.xxx.xxx>;tag=as200dbc2c
> Min-Expires: 600
> Server: Cirpack/v4.41f (gw_sip)
> To: <sip:59972778@ xxx.xxx.xxx.xxx>;tag=00-08013-1313fd60-3a4260273
> Via: SIP/2.0/UDP  xxx.xxx.xxx.xxx:5060;received=
> xxx.xxx.xxx.xxx;rport=5060;branch=z9hG4bK259bcd00
> WWW-Authenticate: Digest
> realm="XXX.XXX",nonce="1313fbd315b1cefb52c870440e6f5455",opaque="1311d5ce56cc060",stale=false,algorithm=MD5
> Content-Length: 0
>
>
> <------------->
> [Mar 20 18:34:49] VERBOSE[7840] logger.c: --- (10 headers 0 lines) ---
> [Mar 20 18:34:49] VERBOSE[7840] logger.c:     -- Got SIP response 423
> "Interval Too Brief" back from  xxx.xxx.xxx.xxx
> [Mar 20 18:34:49] VERBOSE[7840] logger.c: Really destroying SIP dialog
> '522ef0f7118f00d83d42b1082882fc10 at 192.168.0.1' Method: REGISTER
>
Hi,

I explored further and I find something weird in my registration sip packet.

It says expires : 120 in any case. Does this field mean expiry for SIP 
registration or just some expiry for sip packet ?
If it is for SIP registration, why is always 120 regardles of settings in 
sip.conf ?

Thanks in advance,

regards,

Rob.


REGISTER 13 headers, 0 lines
Reliably Transmitting (no NAT) to 10.253.1.31:5060:
REGISTER sip:10.253.1.31 SIP/2.0
Via: SIP/2.0/UDP 10.135.125.59:5060;branch=z9hG4bK2b4e2906;rport
From: <sip:59972778 at 10.253.1.31>;tag=as38898bbb
To: <sip:59972778 at 10.253.1.31>
Call-ID: 3b9637f60999f2cf401f5a602a866036 at 192.168.0.1
CSeq: 107 REGISTER
User-Agent: Asterisk PBX
Max-Forwards: 70
Authorization: Digest username="59972778", realm="voip.siol", algorithm=MD5, 
uri="sip:10.253.1.31", nonce="178ab9c669db2748795e5a3442b8657b", 
response="7035dac9ab19de49f63d45f8c162558c", opaque="178aaca821979d1"
Expires: 120
Contact: <sip:59972778 at 10.135.125.59>
Event: registration
Content-Length: 0


>
> _______________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users