Jump to content

410 Error


jlumby
 Share

Recommended Posts

I know that mid way into the 4.2 releases a 410 error was added as a feature to deal with out of sequence CSeq numbers as a result of a PBX restart. The problem was it did not fix things for Aastra, and it created problems for others like Grandstream, and Yealink. I am wondering if there are any plans to remove it from future versions since it seems to be doing more harm than good.

Link to comment
Share on other sites

The problem was that if the PBX accepts the subscription, the subscription dialog would be fine; however the sequence number of the notifications would randomly start with a lower number and the phone would reject it. Additionally, the notification XML bodies also contain sequence numbers which create additional problems. That is why the PBX tries to force the user agent to come up with a new subscription with reset sequence numbers.

 

IMHO it is clearly a bug of the endpoints that they dont retry after some time with a new subscription. That would solve the problem 100 %.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...