Summary: | ASTERISK-05725: [POST 1.2] Add UserAgent to astdb | ||
Reporter: | opsys (opsys) | Labels: | |
Date Opened: | 2005-11-28 14:35:43.000-0600 | Date Closed: | 2011-06-07 14:03:00 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Channels/chan_sip/Registration |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | It would be nice to have the UserAgent saved. That way a config file can be made for UA specific operations. Be it Pageing (ALERT-INFO vs. SIPHeader) or features that require differences between devices, parking, blf, transfers etc. I would suggest that this be used in tandem with the features.conf file as well as creating a UA capabilities matrix. Or would these idiosyncracies be handled better via the DialPlan??? ****** ADDITIONAL INFORMATION ****** Index: channels/chan_sip.c =================================================================== RCS file: /usr/cvsroot/asterisk/channels/chan_sip.c,v retrieving revision 1.919 diff -u -r1.919 chan_sip.c --- channels/chan_sip.c 28 Nov 2005 02:55:56 -0000 1.919 +++ channels/chan_sip.c 28 Nov 2005 20:27:46 -0000 @@ -5605,6 +5605,7 @@ ast_update_realtime("sippeers", "name", peer->name, "ful lcontact", "", "ipaddr", "", "port", "", "regseconds", "0", "username", "", NULL ); } else { ast_db_del("SIP/Registry", peer->name); + ast_db_del("SIP/UserAgent", peer->name); } } } @@ -5927,6 +5928,7 @@ if (option_verbose > 3) { ast_verbose(VERBOSE_PREFIX_3 "Saved useragent \"%s\" for peer %s\n",p->useragent,p->name); } + ast_db_put("SIP/UserAgent", p->name, p->useragent); } return PARSE_REGISTER_UPDATE; } | ||
Comments: | By: Olle Johansson (oej) 2005-11-29 01:12:37.000-0600 You can already get the useragent with the dial plan function SIP_PEER - isn't that enough? By: opsys (opsys) 2005-11-30 10:18:01.000-0600 I will close this Issue as it functions cn be duplicated in the Dialplan with a Function call and write to the astDB.. Thanks Olle |