[Spce-user] Registration expiration same as Last Registration

[Jon Bonilla (Manwe)]

El Wed, 3 Apr 2013 10:35:29 -0700
Cliff Farley <cloudkiker at rmanykids.com> escribió:


Hi Cliff


You message is quite unreadable. Maybe because html format? Could you please
explain who is who and send the ngre-sip captures attached rather than inline?

thanks,

Jon




> I have finally gotten both sides of the SBC setup to register but the peer
> side is continuously sending registration messages to the peer. In the
> subscriber screen it is showing the last registration and the expiration time
> as being the same time. I tried setting the sst timer in the domain and also
> the peering group levels but neither seemed to affect the messages. Here is
> what I see from the admin interface. a.. Currently Registered:yesLast
> Registration at:2013-04-03 10:01:45Expires at:2013-04-03 10:01:45Last
> Response Code:200Last Response
> String:OKContacts:<sip:5412291800 at 209.40.72.230:5060;uuid=8ce3f7be-7c47-4032-b...
> 
> Here is an example of the messages being sent to the switch for registration
> about one request every second. 10:14:10.04209
> |---------------------------------> |REGISTER sip:172.16.1.30 SIP/2.0
> |Via: SIP/2.0/UDP 209.40.72.230;bra
> |nch=z9hG4bK6cc3.34eb8b0d409004517e
> |60b0ca18279562.0
> |Via: SIP/2.0/UDP 172.16.1.119:5080
> |;branch=z9hG4bKjfPEkaD4;rport=5080
> |
> |From: 5412291800 <sip:5412291800 at 1
> |72.16.1.30>;tag=5B94439B-515C604B0
> |0083043-48E49720
> |To: 5412291800 <sip:5412291800 at 172
> |.16.1.30>
> |CSeq: 1629 REGISTER
> |Call-ID: 621B4E76-515C604B00083089
> |-48E49720
> |Contact: <sip:5412291800 at 209.40.72
> |.230:5060;uuid=8ce3f7be-7c47-4032-
> |bdda-66d9796d55ee>
> |Expires: 21600
> |User-Agent: Sipwise NGCP Applicati
> |on Server
> |Max-Forwards: 69
> |Authorization: Digest username="54
> |12291800", realm="172.16.1.30", no
> |nce="b8943bc99ec9", uri="sip:172.1
> |6.1.30", qop=auth, cnonce="3902ee7
> |a", nc=00000001, response="da0af1a
> |c99e1ceb8d27468d8cd5c126d", algori
> |thm=MD5
> |Content-Length: 0
> 10:14:10.04305 | <---------------------------------
> | SIP/2.0 200 OK
> | From: 5412291800 <sip:5412291800 at 1
> | 72.16.1.30>;tag=5B94439B-515C604B0
> | 0083043-48E49720
> | To: 5412291800 <sip:5412291800 at 172
> | .16.1.30>;tag=172.16.1.30+1+251424
> | +f0d776f1
> | Via: SIP/2.0/UDP 209.40.72.230;bra
> | nch=z9hG4bK6cc3.34eb8b0d409004517e
> | 60b0ca18279562.0
> | Server: DC-SIP/2.0
> | Organization: MetaSwitch
> | Content-Length: 0
> | Via: SIP/2.0/UDP 172.16.1.119:5080
> | ;branch=z9hG4bKjfPEkaD4;rport=5080
> | 
> | CSeq: 1629 REGISTER
> | Call-ID: 621B4E76-515C604B00083089
> | -48E49720
> | Contact: <sip:5412291800 at 209.40.72
> | .230:5060;uuid=8ce3f7be-7c47-4032-
> | bdda-66d9796d55ee>;EXPIRES=21600
> It seems to me the registration is saying that it should be good for 21600
> seconds but the expiration time in sipwise is not updating properly. So what
> did I do wrong? Thank you for any help you can provide. Have a wonderful day.
> Cliff Farley
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20130408/33f8ab17/attachment-0001.asc>