Kill the user!
For many years, I’ve been working to remove the “type=user” and “type=friend” from chan_sip. In 1.4 you can in fact do everything you can do with a user with a peer. The only difference is the way we match incoming calls.
- For users, we match the user object name with the From: username (without the domain).
- For peers, we match on IP for incoming calls.
I’ve created a branch called “kill_the_user” that has no type=friend or type=user, only peers.alls are handled this way
- First, we match on peer object name with the From username
- Then we try to match on IP/Port
- If we can’t match, we send to the context defined in the “general” section in sip.conf or to “default”.
If you can find any way this may give you problems, please inform me now. Otherwise, I’m goingto test this branch with all of you. I don’t foresee any problems going ahead with this in trunk.s compatibility, we will accept “type=friend” and “type=user” with a warning in 1.6,then remove it totally. Old configurations will still work. The longterm goal is to define new objects, please check the docs for Codename Pineapple objects,phone, service and trunk.For realtime, realtime users will not be used any more.
Tags: Asterisk news, chan_sip