I never noticed those dial peers pointing to the 0/2/x ports. Interesting, since NONE of the 0/2/x ports have ever been active. Only recently did I turn on 0/2/0 for the paging system. I think you're right. My limited understanding then says if someone is dialing out on the PRI and an error occurs (for whatever reason), the 2801 will send the call out 0/2/0 as currently configured, which would cause the overhead page to activate. <br>
<br>Really strange config the more I look at it! It would make more sense to route the call out 0/1/x as those are connected to POTS lines.<br><br>Thanks everyone! <br><br>David<br><br><div class="gmail_quote">On Mon, Apr 26, 2010 at 2:57 PM, Nick Matthews <span dir="ltr"><<a href="mailto:matthnick@gmail.com">matthnick@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I would kill dial peer 101. If you received a failure code on your<br>
pri, it would re route to your next dial peer. You may want to adjust<br>
the gatewat so it doesn't reroute on that particular error code.<br>
<font color="#888888"><br>
-nick<br>
</font><div><div></div><div class="h5">On Monday, April 26, 2010, David Zhars <<a href="mailto:dzhars@gmail.com">dzhars@gmail.com</a>> wrote:<br>
> Sorry, I was substituting # so I didn't have to type "number". She does not dial the hash key at the end of dialing.<br>
> You are correct, I could not duplicate the issue when I tried calling (the call went right through to the end user's cell phone and the end user answered).<br>
><br>
> Gateway config:<br>
><br>
> !! Last configuration change at 10:51:37 edt Fri Apr 23 2010<br>
> ! NVRAM config last updated at 10:51:55 edt Fri Apr 23 2010<br>
> !<br>
> version 12.4<br>
> service timestamps debug datetime msec localtime<br>
> service timestamps log datetime msec localtime<br>
> service password-encryption<br>
> service sequence-numbers<br>
> !<br>
> hostname noname-2801<br>
> !<br>
> boot-start-marker<br>
> boot system flash:c2801-spservicesk9-mz.124-22.T.bin<br>
> boot-end-marker<br>
> !<br>
> logging message-counter syslog<br>
> logging buffered 4096 informational<br>
> enable secret 5 $1$rDeJ$wQbhfjKKM2KiBeHquZr51<br>
> !<br>
> no aaa new-model<br>
> clock timezone est -5<br>
> clock summer-time edt recurring<br>
> network-clock-participate wic 1<br>
> network-clock-select 1 T1 0/1/0<br>
> dot11 syslog<br>
> ip source-route<br>
> !<br>
> !<br>
> ip cef<br>
> no ipv6 cef<br>
> multilink bundle-name authenticated<br>
> !<br>
> !<br>
> isdn switch-type primary-ni<br>
> !<br>
> voice class codec 100<br>
> codec preference 1 g711ulaw<br>
> codec preference 2 g729br8<br>
> codec preference 3 g729r8<br>
> !<br>
> voice class h323 1<br>
> h225 timeout tcp establish 3<br>
> h225 display-ie ccm-compatible<br>
> !<br>
> voice-card 0<br>
> !<br>
> !<br>
> archive<br>
> log config<br>
> hidekeys<br>
> !<br>
> !<br>
> controller T1 0/1/0<br>
> pri-group timeslots 9-24<br>
> !<br>
> interface Vif1<br>
> no ip address<br>
> !<br>
> interface FastEthernet0/0<br>
> no ip address<br>
> shutdown<br>
> duplex auto<br>
> speed auto<br>
> !<br>
> interface FastEthernet0/1<br>
> ip address 192.168.6.229 255.255.255.0<br>
> speed 100<br>
> full-duplex<br>
> !<br>
> interface Serial0/1/0:23<br>
> no ip address<br>
> encapsulation hdlc<br>
> isdn switch-type primary-ni<br>
> isdn incoming-voice voice<br>
> isdn supp-service name calling<br>
> no cdp enable<br>
> !<br>
> ip forward-protocol nd<br>
> ip route 0.0.0.0 0.0.0.0 192.168.6.210<br>
> ip http server<br>
> no ip http secure-server<br>
> !<br>
> !<br>
> snmp-server community hiddentext RO<br>
> disable-eadi<br>
> !<br>
> control-plane<br>
> !<br>
> voice-port 0/0/0<br>
> connection plar 2002<br>
> description 111-222-3223<br>
> caller-id enable<br>
> !<br>
> voice-port 0/0/1<br>
> connection plar 4074<br>
> description 111-222-3333<br>
> caller-id enable<br>
> !<br>
> voice-port 0/0/2<br>
> echo-cancel coverage 48<br>
> timing hookflash-out 500<br>
> !<br>
> voice-port 0/0/3<br>
> echo-cancel coverage 48<br>
> timing hookflash-out 500<br>
> !<br>
> voice-port 0/1/0:23<br>
> !<br>
> voice-port 0/2/0<br>
> !<br>
> voice-port 0/2/1<br>
> !<br>
> voice-port 0/2/2<br>
> !<br>
> voice-port 0/2/3<br>
> !<br>
> no ccm-manager fax protocol cisco<br>
> !<br>
> no mgcp package-capability res-package<br>
> no mgcp package-capability fxr-package<br>
> no mgcp timer receive-rtcp<br>
> mgcp fax t38 ecm<br>
> !<br>
> dial-peer voice 7 voip<br>
> preference 1<br>
> destination-pattern 1...<br>
> progress_ind setup enable 3<br>
> voice-class codec 100<br>
> voice-class h323 1<br>
> session target ipv4:192.168.6.1<br>
> incoming called-number .<br>
> dtmf-relay h245-alphanumeric<br>
> ip qos dscp cs5 media<br>
> no vad<br>
> !<br>
> dial-peer voice 8 voip<br>
> preference 1<br>
> destination-pattern 8...<br>
> progress_ind setup enable 3<br>
> voice-class codec 100<br>
> voice-class h323 1<br>
> session target ipv4:192.168.6.1<br>
> incoming called-number .<br>
> dtmf-relay h245-alphanumeric<br>
> ip qos dscp cs5 media<br>
> no vad<br>
> !<br>
> dial-peer voice 9 voip<br>
> preference 1<br>
> destination-pattern 4...<br>
> progress_ind setup enable 3<br>
> voice-class codec 100<br>
> voice-class h323 1<br>
> session target ipv4:192.168.6.1<br>
> incoming called-number .<br>
> dtmf-relay h245-alphanumeric<br>
> ip qos dscp cs5 media<br>
> no vad<br>
> !<br>
> dial-peer voice 10 voip<br>
> preference 1<br>
> destination-pattern 2...<br>
> progress_ind setup enable 3<br>
> voice-class codec 100<br>
> voice-class h323 1<br>
> session target ipv4:192.168.6.1<br>
> incoming called-number .<br>
> dtmf-relay h245-alphanumeric<br>
> ip qos dscp cs5 media<br>
> no vad<br>
> !<br>
> dial-peer voice 100 pots<br>
> preference 1<br>
> destination-pattern 9T<br>
> direct-inward-dial<br>
> port 0/1/0:23<br>
> !<br>
> dial-peer voice 101 pots<br>
> preference 2<br>
> destination-pattern 9T<br>
> port 0/2/0<br>
> !<br>
> dial-peer voice 102 pots<br>
> preference 3<br>
> destination-pattern 9T<br>
> port 0/2/1<br>
> !<br>
> dial-peer voice 911 pots<br>
> preference 1<br>
> destination-pattern 9911<br>
> port 0/0/0<br>
> prefix 911<br>
> !<br>
> dial-peer voice 913 pots<br>
> preference 4<br>
> destination-pattern 9911<br>
> direct-inward-dial<br>
> port 0/1/0:23<br>
> prefix 911<br>
> !<br>
> dial-peer voice 912 pots<br>
> preference 3<br>
> destination-pattern 9911<br>
> port 0/0/1<br>
> prefix 911<br>
> !<br>
> dial-peer voice 17 voip<br>
> preference 1<br>
> destination-pattern 6...<br>
> progress_ind setup enable 3<br>
> voice-class codec 100<br>
> voice-class h323 1<br>
> session target ipv4:192.168.6.1<br>
> incoming called-number .<br>
> dtmf-relay h245-alphanumeric<br>
> ip qos dscp cs5 media<br>
> no vad<br>
> !<br>
> dial-peer voice 11 voip<br>
> preference 1<br>
> destination-pattern 3...<br>
> progress_ind setup enable 3<br>
> voice-class codec 100<br>
> voice-class h323 1<br>
> session target ipv4:192.168.6.1<br>
> incoming called-number .<br>
> dtmf-relay h245-alphanumeric<br>
> ip qos dscp cs5 media<br>
> no vad<br>
> !<br>
> dial-peer voice 55 pots<br>
> description Paging for Fire<br>
> destination-pattern *34<br>
> port 0/2/0<br>
> forward-digits all<br>
> !<br>
> !<br>
> num-exp 8581 4071<br>
> num-exp 8812 1752<br>
> !<br>
> line con 0<br>
> password 7 045A081206<br>
> login<br>
> line aux 0<br>
> line vty 0 4<br>
> password 7 1416111F05<br>
> login<br>
> line vty 5 15<br>
> password 7 070E225847<br>
> login<br>
> !<br>
> scheduler allocate 20000 1000<br>
> ntp server 192.168.6.1<br>
> end<br>
> l<br>
><br>
> On Mon, Apr 26, 2010 at 2:44 PM, Peter Slow <<a href="mailto:peter.slow@gmail.com">peter.slow@gmail.com</a>> wrote:<br>
> can we see the complete configuration of your gateway, please? also,<br>
> did you say that you were unable to reproduce this issue when you<br>
> tried calling?<br>
><br>
> Also, why did your user hit the hash key at the end of dialing?<br>
><br>
> -Peter<br>
><br>
> On Mon, Apr 26, 2010 at 2:36 PM, David Zhars <<a href="mailto:dzhars@gmail.com">dzhars@gmail.com</a>> wrote:<br>
>> Still getting more info from my user. Here is what she said happened<br>
>> (twice!):<br>
>><br>
>> She goes to dial the cell phone person. Presses 9 so she can have an<br>
>> outbound line. The person's cell is fairly innocuous, no 3 and 4 together,<br>
>> in fact there is no 4 in the number. Once she dials the # she gets this<br>
>> sort of automated voice that says "Per this subscriber's request this phone<br>
>> cannot accept any incoming calls. Reference # MA95285". She then hears a<br>
>> beep. Thinking this is the answering machine of the cell phone, she starts<br>
>> talking, and that's when it starts going over the intercom.<br>
>><br>
>> I have to believe that it is the cell phone that (perhaps since it won't<br>
>> accept any incoming calls) is being forwarded or is itself dialing a *34<br>
>> code, and we pick it up.<br>
>><br>
>> I just dialed the person's cell # and the person on the other end picked<br>
>> right up. So I didn't even get the message about "not accepting incoming<br>
>> calls".<br>
>><br>
>> The crosstalk thing has some merit, but like Peter says, it would seem like<br>
>> I would be having a whole lot more complaints if that was the cause. Plus<br>
>> my user made other calls to cell phones and POTS people and none of those<br>
>> went over the intercom. I have checked my end user's phone and under<br>
>> "recently placed calls" I can see the cell # called, there are no *34's<br>
>> anywhere in there. I am going to try and do a CDR report tonight and see if<br>
>> that shows anything.<br>
>><br>
>><br>
>><br>
>><br>
>> On Mon, Apr 26, 2010 at 1:26 PM, Norton, Mike <<a href="mailto:mikenorton@pwsd76.ab.ca">mikenorton@pwsd76.ab.ca</a>><br>
>> wrote:<br>
>>><br>
>>> Another thing... did she actually hear the person’s voicemail greeting? Or<br>
>>> did she just hear the intercom system’s pre-announce tone, assume it was a<br>
>>> voicemail beep, and start talking? If it was the latter, then you might just<br>
>>> accidentally be matching the wrong route pattern somewhere.<br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>><br>
>>> Mike Norton<br>
>>><br>
>>> I.T. Support<br>
>>><br>
>>> Peace Wapiti School Division No. 76<br>
>>><br>
>>> Helpdesk: 780-831-3080<br>
>>><br>
>>> Direct: 780-831-3076<br>
>>><br>
>>><br>
>>><br>
>>><br>
>>><br>
>>> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>
>>> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of David Zhars<br>
>>> Sent: April-26-10 11:01 AM<br>
>>> To: Peter Slow<br>
>>> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
>>> Subject: Re: [cisco-voip] User Inadvertently Reaches Intercom<br>
>>><br>
>>><br>
>>><br>
>>> What I meant was we did not hear her dialing the phone, but we heard her<br>
>>> leaving a message for this person (since the person dialed did not answer).<br>
>>> All I can think is the cell phone she was calling was forwarded to a *34<br>
>>> speed-dial or something, and somehow we picked it up.<br>
>>><br>
>>> It was so bizarre because when it happened, we called my user and told her<br>
>>> what happened. She figured the call didn't go through, so she placed the<br>
>>> call again, and again, we heard her leaving the message over the intercom!<br>
>>> She has since tried calling other cells and POTS and none of those have gone<br>
>>> over the intercom.<br>
>>><br>
>>> When I look at recently dialed calls, all I see are the cell # she is<br>
>>> calling (which has no 3 or 4 in it!!) I have never seen anything like this<br>
>>> one, but like you said, CDR might be a<br>
</div></div></blockquote></div><br>