i assume we talking about ata and sip.
2.14 and 2.15 does not have this bug. I have the same problem w/ fw
v2.16 when getting anything else then "100 trying" or "200 OK" on the
register callleg, which either results in stopping to register (i power
cycle the ata or go to the web config and update once then) or
registering with a malformed request uri "REGISTER sip:: SIP/2.0" where
host and port disapeared.
i suggest to upgrade the fw
Michael
Dan Fernandez wrote:
I´ve got an ATA with v2.16
configured as per JTodd´s guide having problems re-registering. The
only thing particular to this ATA (I´ve got several all configured the
same way but one of them have problems) is that is on a public IP. I
have commented NAT=1 and canreinvite=no on sip.conf
The ATA registers fine the first
time but on the following registration updates, * gives me the the
warning: "Registration fail for ....." and it continues trying to
register unsuccesfully over and over. If I do sip show peers, the ATA is not there, of course.
Looking at the archives I´ve found
that on the new version (2.16.1) they have fixed a bug which is
somewhat related:
CSCeb17953 The Cisco ATA stops the registration process if it
receives an unexpected response to a REGISTER request.
HAs anyone had this problem before
with 2.16? Woudl 2.16.1 fix this ?
Thanks in advance
|
