The 486 response is straight forward and might be indicative of the real
state of the phone. The thing that is crazy about this call is when
your ITSP receives the 486 response, it retries the same INVITE with the
same call ID different via, same cseq to sipXbridge which respond back
with "hey are you looping back to me or you are just plain crazy?"
On 11/12/2011 07:48 AM, Jeff Gilmore wrote:
Hi all,
In the last month or two, I have been getting reports of intermittent
problems with incoming calls. The callers get a message (I think from my ITSP)
that the number is not in service. The calls actually do make it to my server,
and all the way to the Linksys 2102 ATA device.
Over the course of the call, the ATA responds with a "486 busy here". I also see later a
"Loop detected" message from sipXbridge. It might be the case that the user is actually
on the phone when the call comes in (and this particular customer does not have voicemail enabled).
But the logs don't seem to indicate that.
A few minutes later, everything works fine. Until recently, there were no such
reported problems.
Would anyone be willing to look at this trace and comment on what you see?
I would greatly appreciate it.
Jeff
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
