[cisco-voip] Dropped calls coming from FXO

[Ryan Ratliff]

Not at all.  The only number CUCM will ever see coming from that FXO  
port is what you've got configured as the plar destination.   There  
is no requirement at all that CUCM have to be able to route calls to  
the calling party number.

-Ryan

On Apr 10, 2008, at 2:17 AM, Anthony Kouloglou wrote:

Thanks Gregory,
i hope you might get somewhere.
I would like to ask something more about route patterns in CCM:
the call from FXO, because callerid is enabled, arrives with a  
pattern 3069XXXXX. But there is no such a route pattern in CCM  
because i don't need one. I only route 3 digit calls beginning with *  
through that voice gateway (*XXX)
Does CCM needs to know the "return path" for each call?Or the  
signalling is fine and there is no problem?
I mean, every time a call arrives from a H323 ios gateways, does CCM  
need to have a route pattern back to that h323 ios gw with the same  
pattern?

Thanks
Anthony

Gregory, Christopher D. wrote:
>
> Anthony, just saw your attachment. Sorry. I will take a look at  
> that and get back with you
>
> From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip- 
> bounces at puck.nether.net] On Behalf Of Anthony Kouloglou
> Sent: Wednesday, April 09, 2008 6:47 AM
> To: cisco-voip at puck-nether.net
> Subject: [cisco-voip] Dropped calls coming from FXO
>
> Hi, i have a ccm 6.0 who has 2 h323 gateways configured.
> One of them has one E1 and works fine
> The other one, is a 2811 with 1 vic2-2fxo card and has 2 FCTs  
> attached.
>
> A specific route pattern on CUCM sends calls to Company's Mobiles  
> through 2811- This direction works fine!
> But, an incoming call to FCT, only rings the specified DN!!
> For example, i have a connection plar on the voice-port to send all  
> calls to 2000 (console).
> When someone calls FCT, 2000 rings once and then the call is dropped!!
> The amazing is a few times it works fine!! (most of the times it  
> doesn't)
>
> interface FastEthernet0/0.100
>  description ### Voice Vlan interface to 3560 ###
>  encapsulation dot1Q 100
>  ip address 10.254.254.253 255.255.255.0
>  h323-gateway voip bind srcaddr 10.254.254.253
> !
> voice-port 0/0/0
>  connection plar 2000
>  description *** FXO ACTIVE port -- Connected to FCT ***
>  bearer-cap Speech
>  station-id name FCT
>  station-id number 69XXXXXXX
> !
> voice-port 0/0/1
>  description *** FXO ACTIVE port -- Connected to FCT ***
>  connection plar 2000
>  bearer-cap Speech
>  station-id name FCT
>  station-id number 69XXXXXX
> !
> !
> dial-peer voice 1 pots
>  destination-pattern .
>  direct-inward-dial
> !
> dial-peer voice 2 pots
>  destination-pattern *...
>  port 0/0/0
>  prefix *
> !
> dial-peer voice 3 pots
>  destination-pattern *...
>  port 0/0/1
>  prefix *
> !
> dial-peer voice 2000 voip
>  destination-pattern 2...
>  session target ipv4:10.254.254.5
>  dtmf-relay h245-alphanumeric
>  codec g711alaw
> !
>
> I have used *... because the Telephone Company (mobile) uses *XXX  
> for calls between its subscribers.
>
> In CUCM, there is *XXX route-pattern pointing to this voice gateway.
>
> Any ideas? It seems really bizarre that a few times it does work!!
>
> i also provide the voip ccapi debug of a failed call as attachment.
> Thanks Akoul
>
> In accordance with the Black Box Anti-Virus Policy, this e-mail  
> message has been scanned for viruses. This banner message will  
> appear each time the message is scanned.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080410/ee04515b/attachment.html