Trunk blocked because of too many registration requests!!

[Paddyd]

Just had a trunk blocked by my provider because of too many registrations in too short a time. Going by the trace provided at one time there almost 1 per sec.

However the exchange was in the middle of a call at the time and only showed itself sending a request, once it noticed the trunk down, once every 120 secs. The xxxxx603 is the right Auth for the trunk and the a.b.c.90 is our external IP address. As soon as the block was removed the trunk came up. There was a short time after where calls where failing but it cleared in a couple of mins. Wondering if anyone else has had this happen before. Its like there was some one else trying to use the trunk but the Auth was valid, so that kind of disproves my only idea!

[Jul 22 14:25:29] VERBOSE[4636] logger.c: -- Registered SIP 'xxxxx603' at
aa.bb.cc.90 port 41028
[Jul 22 14:25:32] VERBOSE[4636] logger.c: -- Unregistered SIP 'xxxxx603'
[Jul 22 14:25:32] VERBOSE[4636] logger.c: -- Registered SIP 'xxxxx603' at
aa.bb.cc.90 port 41028
[Jul 22 14:26:14] VERBOSE[4636] logger.c: -- Unregistered SIP 'xxxxx603'
[Jul 22 14:26:14] VERBOSE[4636] logger.c: -- Registered SIP 'xxxxx603' at
aa.bb.cc.90 port 41028
[Jul 22 14:26:17] VERBOSE[4636] logger.c: -- Unregistered SIP 'xxxxx603'
[Jul 22 14:26:17] VERBOSE[4636] logger.c: -- Registered SIP 'xxxxx603' at
31.221.42.90 port 41028
[Jul 22 14:26:41] VERBOSE[4636] logger.c: -- Unregistered SIP 'xxxxx603'
[Jul 22 14:26:41] VERBOSE[4636] logger.c: -- Registered SIP 'xxxxx603' at
31.221.42.90 port 41028
[Jul 22 14:26:42] VERBOSE[4636] logger.c: -- Unregistered SIP 'xxxxx603'
[Jul 22 14:26:43] VERBOSE[4636] logger.c: -- Registered SIP 'xxxxx603' at
aa.bb.cc.90 port 41028