[asterisk-bugs] [Asterisk 0015701]: [patch] Not possible to specify expiry for peer callback

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Sep 4 04:06:11 CDT 2009


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15701 
====================================================================== 
Reported By:                Nick_Lewis
Assigned To:                oej
====================================================================== 
Project:                    Asterisk
Issue ID:                   15701
Category:                   Channels/chan_sip/Registration
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-08-12 04:57 CDT
Last Modified:              2009-09-04 04:06 CDT
====================================================================== 
Summary:                    [patch] Not possible to specify expiry for peer
callback
Description: 
It is possible in sip.conf to specify a callback extension for a peer.
(This automatically causes a registration to be generated.) However it is
not currently possible to control how long the callback extension is active
for before it expires and is refreshed. This is a problem particularly when
working behind a nat firewall because the nat binding tends to expire
before the callback is refreshed causing the callback to fail to work.

I propose the addition of the callbackexpiry parameter to sip.conf to
provide this functionality
====================================================================== 

---------------------------------------------------------------------- 
 (0110216) oej (manager) - 2009-09-04 04:06
 https://issues.asterisk.org/view.php?id=15701#c110216 
---------------------------------------------------------------------- 
I think we have two separate the issues here. You reported that you could
not set expiry - let's solve that now and add the rest later. 

I would say that register=yes would work if we have regexten, but on the
other hand regexten causes other effects we might not want.

Ouch. sip.conf is really a pain. 

Let's see. The hint in the dialplan points from exten to device. We have
nothing that points from device to a "default extension" for this device
other than regexten.  We had to come up with something new, and that's why
callbackexten was invented, which is a poor name. It should have been
defaultexten or primaryexten or something. A reverse hint could be useful
in many situations, like call transfers, forwards an others.

Anyway, let's focus on the expiry. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-04 04:06 oej            Note Added: 0110216                          
======================================================================




More information about the asterisk-bugs mailing list