Well, I believe that there aren't standard method in order to complete your requirement, but some years ago, we resolve this issues as follow:<br><br>1. We modified the destination pattern for example if the normal destination pattern was: 9...... (the user dialed the 9 to take outside line then the 9 was striped and the digits were sent to PSTN) Then we used as destination pattern 93456...... where the string 3456 was the password, so the user dialed 9<password> + num to PSTN. the dial-peer worked only if the dialed digits matched with destination pattern.<br>
<br>2. time-range structure, we used only to block voip legs, no pots legs. So we implemented a access-list for RTP traffic and signalig traffic time-range based. then we put the access list in serial interface, or ethernet interface... then in some times the call didn't established.<br>
<br>Obviously these are not "THE SOLUTION" but was useful....<br><br>Rgds.<br><br><div class="gmail_quote">On Fri, Apr 11, 2008 at 12:12 PM, Marcelo Zilio <<a href="mailto:email@constel.com.br">email@constel.com.br</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Hi<br>
<br>
Two questions:<br>
1) Can I set a password in a dial-peer for the FXS ports with a<br>
telephone set? I mean, when the user try to call someone, before router<br>
sending the digits, it requests a password.<br>
2) Can the dial-peers work with "time-range" structure?<br>
<br>
This is not a CME or CallManager. Just VoIP.<br>
<br>
Thank you<br>
Marcelo<br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Omar E.P.T<br>-----------------<br>Certified Networking Professionals make better Connections!