[Asterisk-Dev] Thoughts on a context for dialplan execution upon a sip or iax register?

[Chris A. Icide]

 >On April 25, 2005 10:28 am, Brian West wrote:
 >> Well from his example he must no tknow you can do setvar in a
 >> sip.conf entry...
 >>
 >> [bob]
 >> type=friend
 >> setvar=TEST=asdf

While being able to setvar from a sip entry is nice, there are alot of 
things you can do besides setting a variable from the dialplan that you 
cannot currently do from the sip entry.

Also, that var gets set when that sip entry places a call, not registers, 
correct?

What I was thinking about was a context in which a register or un-register 
event would present to the context uniquely based upon the sip entry header 
and the un-register or register (you could even extend this to options or 
any other non-invite or active call signalling).  I used SetVar as an example.

However, you may want to call an AGI that updates a back-end database, or 
you may want to auto-login the phone/agent to a ACD.

You might be using the registering device as a call route and you could 
enable to disable the route in the dialplan based upon it's registration 
status.

I don't know what everyone might want to do with such a feature.

At this point if it were available, I'd be using it to change some fields 
in an external database based upon it's registration status.

Think about this.

If we had this, and the MWI function (allowing local VM status to be 
presented to a remote device) then you could use the two to keep a database 
of phone registration locations and re-route the MWI indication to the 
phone when it logs in.  Basically allowing devices to travel across a 
multiple asterisk cluster seamlessly...

So yes, you can set a variable in sip.conf, and yes, currently a 
registration event can dynamically add a priority 1 NoOp statement, both 
very useful in their own right, but I'm not sure how those apply to my 
original question.

-Chris