changing sip/iax2 account context on web admin

Discussions about development of VICIDIAL and astGUIclient

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

changing sip/iax2 account context on web admin

Postby Op3r » Wed Oct 28, 2009 1:17 pm

Because vicidial uses default context even on the sip-vicidial generated accounts.

What I am trying to do is just create a separate context on the accounts just to make it more secure( prohibit agents from dialing on the phone itself)

Is there a way to do this without ever having to copy and pasting everything from sip-vicidial to sip.conf?
Get paid for US outbound Toll Free calls. PM me.
Op3r
 
Posts: 1432
Joined: Wed Jun 07, 2006 7:53 pm
Location: Manila

Postby aouyar » Wed Oct 28, 2009 3:37 pm

I was looking at the same issue recently. It seems like the only way to achieve what you want at the moment is copy-paste to custom contexts.

The best solution would be to define some standard contexts instead of putting everything to the default context directly. Then the default context could simply include all standard contexts and users can pick which contexts to include in custom contexts.

Actually it could be quite simple to implement it as described. It could be achieved by some minor changes to ADMIN_keepalive_all.sh. I would be willing to implement it, but only if I find out how to get the code into the official tree, because maintaining out of tree code is of little interest to me.
aouyar
 
Posts: 124
Joined: Fri Jan 30, 2009 12:49 pm

Postby mflorell » Wed Oct 28, 2009 10:53 pm

This has been made much easier in SVN trunk. Now you can define the outbound dialing context of your phone entries from the admin.php page. So now you can set the phone to dial out through a non-existant context which means the agents can only dial through the ViciDial interface.
mflorell
Site Admin
 
Posts: 18379
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby Op3r » Thu Oct 29, 2009 6:13 am

pretty cool matt.

For all the people who doesnt want to upgrade yet, here's what you can do.

nano sip-vicidial.conf

find and replace default

replace it with your context

save as sip-vicidial1.conf

nano sip.conf

find and replace sip-vicidial change it to sip-vicidial1

save

then reload asterisk :D
Get paid for US outbound Toll Free calls. PM me.
Op3r
 
Posts: 1432
Joined: Wed Jun 07, 2006 7:53 pm
Location: Manila

Postby aouyar » Thu Oct 29, 2009 7:06 am

I can confirm that putting agent phones in another context to forbid dialing is quite simple in the trunk version. I have tried it and it works great.

Once the agent phones are in a different extension context, one can populate this context with custom dialplan entries to permit certain types of dialing. At present, you can copy paste desired dialplan entries from the vicidial-auto context.

Separating the vicidial-auto context into some contexts with standard names, contexts per carrier, etc. could simplify including dialplan entries into custom agent phone contexts.
aouyar
 
Posts: 124
Joined: Fri Jan 30, 2009 12:49 pm

Postby mflorell » Thu Oct 29, 2009 8:17 am

We actually use a Call Menu to create custom dialplan contexts for agents, you have the ability to put in anything you want and it stays as web config so no messing around with conf files directly.
mflorell
Site Admin
 
Posts: 18379
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby aouyar » Thu Oct 29, 2009 1:37 pm

Seems like a really great idea. It never occurred to me that the Call Menus can be used to create custom contexts.

Thanks
aouyar
 
Posts: 124
Joined: Fri Jan 30, 2009 12:49 pm


Return to Development

Who is online

Users browsing this forum: No registered users and 11 guests