Need caller ID routed from remote sites to main site 1

[jmslandon]

Hi,

I just joined this site and so far have had great luck! I hope you guys can help me out with this one

We have call manager 6.1 at our main office. We have 2 remote sites that are set up so all calls are to those sites are routed up to our main office. The problem we are having is the caller ID seems to be dropping off the call when it rings at our main office. Is it possible to have the caller ID remain with the call so we know where the call is originating from? Please help!

Thanks

 

[DallasBPF]

what protocol are you using between the remote site and the main site... mgcp or h323? what are you using at the remote site for lines incoming? POTS or PRI?

------------------------------------
Dallas, Texas
Telecommunications Tech
CCVP, CCNA, Net+

CCNP in the works

 

[jmslandon]

We are using mgcp at the main site. At one of the remote sites we use POTS lines and at the other we are using lines through our Cable provider (Comcast), which i'm not sure if they are considered POTS lines or not. The only PRI is here at the main site.

 

[DallasBPF]

Well if you are using FXO with MGCP, you will not beable to bring in Caller ID since MGCP does not support FXO CallerID capabilities. If CallerID is a must, you will probably want to think about moving the FXO's over to H323 and then set up an FXS card on the router to get MGCP w/SRST

------------------------------------
Dallas, Texas
Telecommunications Tech
CCVP, CCNA, Net+

CCNP in the works

 

[jmslandon]

Okay, please help me understand the logic. The call comes in through the remote sites POTS line, with caller ID. It never rings there because it is automatically directed to our main site through the VPN tunnel to our main site, where it comes through as unknown.

So it's not dropping caller ID because its coming to us through a data connection (VPN) from the remote site?

Sorry, I'm still very new to this VoIP system.

 

[DallasBPF]

no, the remote site with mgcp set up on fxo will not bring in caller id. either at the remote site or your main site.

it is one of the limitations of mgcp, no caller id coming in on an fxo.

------------------------------------
Dallas, Texas
Telecommunications Tech
CCVP, CCNA, Net+

CCNP in the works

 

[DallasBPF]

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a008009428e.shtml

Below is an insert from the above link from Cisco;

Symptoms

You can potentially encounter these symptoms when you configure Cisco CallManager with IOS MGCP gateways with analog FXO and FXS ports:

The MGCP gateway does not register with Cisco CallManager. Refer to MGCP Gateway Registration Failure with Cisco CallManager.

Caller ID does not work on FXO ports. This is because caller ID is not supported with FXO ports when configured for MGCP. Instead, configure the gateway in H.323 mode.



------------------------------------
Dallas, Texas
Telecommunications Tech
CCVP, CCNA, Net+

CCNP in the works