×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

Caller-ID on CallManager3.3 with FXO port on Gateway

Unanswered Question
Apr 5th, 2004
User Badges:

My gateway (2621XM) supports the caller-id command for the FXO port. I run a debug and see the calling parties number coming through, but Callmanager does not seem to push it through to the ip phones. Does Callmanager 3.3(3) support caller-id for FXO ports?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Hin Lee Mon, 04/05/2004 - 16:04
User Badges:
  • Cisco Employee,

Do you have VIC-2FXO-M1?

Are you using H.323?

Can you please show your config?


H. M.

adignan Mon, 04/05/2004 - 17:56
User Badges:
  • Blue, 1500 points or more

hinho is correct in asking if you are using h.323. CallerId on FXO's w/ MGCP is not supported.

sticano Tue, 04/06/2004 - 03:42
User Badges:

I am using MGCP. Forgive my ignorance, but can you use H.323 with Callmanager 3.3(3)?

sticano Tue, 04/06/2004 - 04:09
User Badges:

No I am using VIC-2FXO with MGCP. The later post says that I cannot use MGCP with FXO to use caller-id. I am going to research if I can use H-323 with Callmanager to achieve this goal.

sarmentrout.bok77 Fri, 04/09/2004 - 18:46
User Badges:

You can definitely use the VIC-2FXO with H.323 and CCM3.3.3 and retrieve Caller-ID as we are doing that right now in my network... If you need more specifics, let me know.


We also have MGCP with FXO and I am going to check on the caller-id because I thought it worked as well, but those sites may only use the FXO for SRST dial-out purposes.

adignan Fri, 04/09/2004 - 18:58
User Badges:
  • Blue, 1500 points or more

Caller-Id with fxo and mgcp definately does not work.

adignan Sat, 04/10/2004 - 07:28
User Badges:
  • Blue, 1500 points or more

Why don't you post your config, that way I can get a good idea of whats going on.


/andy

sticano Sat, 04/10/2004 - 07:32
User Badges:

dial-peer voice 1 pots

destination-pattern 9T

direct-inward-dial

port 1/0/1

!

dial-peer voice 100 voip

destination-pattern .......

session target ipv4:10.0.96.200

incoming called-number 1234

dtmf-relay h245-alphanumeric

codec g711ulaw


voice-port 1/0/1

timing hookflash-out 50

caller-id enable


and I have a H.323 gateway defined in Callmanager


adignan Sat, 04/10/2004 - 07:43
User Badges:
  • Blue, 1500 points or more

Where do you want your inbound calls to the fxo port to go? What number do your inbound extensions begin with? For my example lets say your extension are four digit and start with 34 and you want inbound calls to go to 3400, here is what you would paste in:


voice-port 1/0/1

timing hookflash-out 50

caller-id enable

connection plar 3400

!

dial-peer voice 1 pots

destination-pattern 9T

direct-inward-dial

port 1/0/1

!

dial-peer voice 100 voip

destination-pattern 34..

session target ipv4:10.0.96.200

dtmf-relay h245-alphanumeric

codec g711ulaw


/andy


sticano Sat, 04/10/2004 - 07:54
User Badges:

I added the plar statement. That makes sense, although I am still getting a busy signal when I dial in. I can debug on the router and see the call come in, it just doesn't seem to go to the callmanager. Any ideas??


Scott

adignan Sat, 04/10/2004 - 07:55
User Badges:
  • Blue, 1500 points or more

remove the direct inward dial command from your voice pots dial-peer

adignan Sat, 04/10/2004 - 07:46
User Badges:
  • Blue, 1500 points or more

Why don't you post your config, that way I can get a good idea of whats going on.


/andy

adignan Sat, 04/10/2004 - 07:49
User Badges:
  • Blue, 1500 points or more

Why don't you post your config, that way I can get a good idea of whats going on.


/andy

jdiegmueller Sun, 05/02/2004 - 19:02
User Badges:
  • Bronze, 100 points or more

Cisco claims there is no demand for Caller ID on FXO in a CCM/MGCP.


Of course, this is hogwash, but this is how the story goes.

This was the official response I received when researching the same issue...this was over a month ago..


As I mentioned on the phone with you, unfortunately this is a technical limitation at this point that Caller ID is not supported with MGCP and FXO. Here's the link that should address this. Please search the page for 'caller id'.


http://www.cisco.com/warp/public/cc/pd/rt/2600/prodlit/imgcp_ds.htm


There has been an internal feature request open on this, but for now, your options would be to use H.323 on the GW. I hope this helps to explain things a bit. Let me know if there's anything else on this I can clear up for now.

Actions

This Discussion