| Author |
|
mfitzgerald
Vetran
Joined: June 14 2006
Location: United States
Posts: 142
|
| Posted: May 05 2008 at 11:36am | IP Logged
|
|
|
We’ve noticed LS appears to continuously attempt to REGISTER an endpoint when the REGISTER request fails or receives no reply.
I was looking for a method to either halt this process; limit the number of times it will attempt to register or some other work-around to stop LS from continuing to register to a flawed/unavailable PBX.
LS Engine v. 5.12.3.30
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: May 05 2008 at 12:55pm | IP Logged
|
|
|
Hi Fitz,
Good point. You can’t tell the media engine to stop registering a failed registration attempt unless you call the DisableSipRegisterServer() API procedure.
Unfortunately if your VOIP app is registering to multiple registrars, calling DisableSipRegisterServer() will turn OFF all registration attempts. We will have to do something about this.
Please tell us:
1)
Are you registering to more than one registrar server? If not, simply calling DisableSipRegisterServer() will turn OFF further registration attempts.
2)
Minimally, we could define a new API procedure (or a new parameter to the EnableSipRegisterServer() API proc) that would allow the app to specify a max number of failed register attempts before it would completely give up further retries to the specific registrar server. This would be a simple approach and may do what we want. What are your thoughts?
3)
As an addition or alternative to #2, we could add an immediate event that would be sent to the app telling the app about the failed attempt with a failure count. The app could then determine at any registration boundary if further registration attempts should be terminated. What are your thoughts?
Your version media engine is pretty old. Please consider re-licensing to the current version.
Thanks Fitz,
Support
|
| Back to Top |
|
| |
mfitzgerald
Vetran
Joined: June 14 2006
Location: United States
Posts: 142
|
| Posted: May 05 2008 at 1:19pm | IP Logged
|
|
|
I believe our company is looking into a work order which should include an upgrade.
Your solution #1 will work for us at this time.
I was thinking something like a hybrid of suggestion #2 & 3 would be a nice add-on.
Adding a limit to EnableSipRegisterServer() would be a nice feature (maybe a value of 0 could indicate an infinite number of attempts), with perhaps a TELEPHONY_RETURN_VALUE reflecting something like SipRegisterFailed sent to the EventThreadCallback as a GLOBAL_NOTIFICATION in case the maximum number of attempts was made. This message would not require a numeric value indicating the number of attempts made as the coder should know what the value was set to.
Does that seem reasonable enough?
And as always, thanks for your prompt response.
|
| Back to Top |
|
| |
support
Administrator
Joined: January 26 2005
Location: United States
Posts: 1666
|
| Posted: May 05 2008 at 2:23pm | IP Logged
|
|
|
Fizt,
<<< You
Adding a limit to EnableSipRegisterServer() would be a nice feature (maybe a value of 0 could indicate an infinite number of attempts), with perhaps a TELEPHONY_RETURN_VALUE reflecting something like SipRegisterFailed sent to the EventThreadCallback as a GLOBAL_NOTIFICATION in case the maximum number of attempts was made. This message would not require a numeric value indicating the number of attempts made as the coder should know what the value was set to.
Does that seem reasonable enough?
Support >>>
Right on. Just what we were thinking.
We have made a note of this request for inclusion in a new release.
Support
|
| Back to Top |
|
| |
Active Topics 
Member List 
Search 
Help 
Register 
Login
LanScape Support Forum -> LanScape VOIP Media Engine™ - Technical Support
Topic: Stop Repeating Register Attempts
