| Summary: | ASTERISK-02755: temporarily set SIP UA string on CLI | ||
| Reporter: | benjk (benjk) | Labels: | |
| Date Opened: | 2004-11-06 19:57:55.000-0600 | Date Closed: | 2004-11-07 13:49:41.000-0600 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Interoperability |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | In many interoperability troubleshooting cases, it has proven helpful to ***temporarily*** change the SIP useragent string just for long enought to get support staff of the remote SIP service to attend to one's problem. I know that there is now a global useragent=bob option in sip.conf, but that is not really suited to the troubleshooting of interoperability issues with one particular provider in a production environment at a customer site. What happens is that the the time when the customer allows you to make a global change is the time when the support of the provider is closed. I therefore kindly request that a CLI option be considered which allows an administrator/troubleshooter to temporarily change the UA string for a particular peer, and reset it in the same way after the interoperability issue has been resolved. this could look like the following ... *CLI> sip useragent "Blob V.1.2.3" ip hostile.sipprovider.com and ... *CLI sip useragent default ip hostile.sipprovider.com to reset. | ||
| Comments: | By: Mark Spencer (markster) 2004-11-07 01:18:10.000-0600 You can already change it by just issuing a reload chan_sip.so. Making any such option runtime settable at the command prompt opens the door to wanting more of them to be and it seems wholly unnecessary given the ability to reload a single module and the ability to set a useragent by peer or user. | ||