Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Paging on FXO port gets fast busy 1

Status
Not open for further replies.

beckman68

Technical User
Jul 31, 2002
186
US
I have a 2911 router with a FXO port going into a Bogen UTI1 trunk page port, I setup a dial-peer setup with destination-pattern of 80 and set to use the correct FXO port. It's setup in the CM with a 80 Route pattern 80 setup in the same route partions as the phones. This is set up H323 not MGCP. when I dial the 80 there's a short pause the fast busy. any ideas of what I am missing? I have even tried not connecting it to the Bogen and I still get the same thing.
 
Assuming your call manager and router config is correct you should be able to dial 80 and see the FXO port LED go green for a brief second then you get fast busy. If you don't see the green LED you need to check all your configs again.

if it goes green then the issue is either wiring or with the Bogen.
is the bogen UTI dip switches set to trunk and the other to LS?
If not set them and test again.

If they are not check your wiring between the FXO port and the Bogen.

 
I have the settings correct on the Bogen, and I don't think I missed anything in the CM. The wiring is just Line cord and that was from a working phone. It's the short pause and then the fast busy that gets me.
 
So does the light on the FXO port go green when you call the access code? if it does that eliminates the router or CM being an issue.
 
On the router, get into the console and enter 'debug voip ccapi inout' and see if the CallManager ever actually dials into the router. If not, the delay you are getting could be an overlapping route pattern in your dial plan then it slects your '80' route pattern and can't get to the Gateway.
 
Also on your Dial-Peer, make sure you put in Forward-Digits None or it will send '80' to the Paging system
 
Here is the output from the Debug:

*Jan 8 17:13:23.664: //-1/00D56D761300/CCAPI/cc_api_display_ie_subfields:
cc_api_call_setup_ind_common:
cisco-username=5017399
----- ccCallInfo IE subfields -----
cisco-ani=5017399
cisco-anitype=0
cisco-aniplan=0
cisco-anipi=0
cisco-anisi=1
dest=80
cisco-desttype=0
cisco-destplan=0
cisco-rdie=FFFFFFFF
cisco-rdn=
cisco-lastrdn=
cisco-rdntype=-1
cisco-rdnplan=-1
cisco-rdnpi=-1
cisco-rdnsi=-1
cisco-redirectreason=-1 fwd_final_type =0
final_redirectNumber =
hunt_group_timeout =0

*Jan 8 17:13:23.664: //-1/00D56D761300/CCAPI/cc_api_call_setup_ind_common:
Interface=0x299BE0B4, Call Info(
Calling Number=5017399,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
Called Number=80(TON=Unknown, NPI=Unknown),
Calling Translated=FALSE, Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE,
Incoming Dial-peer=100, Progress Indication=NULL(0), Calling IE Present=TRUE,
Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=67636
*Jan 8 17:13:23.664: //-1/00D56D761300/CCAPI/ccCheckClipClir:
In: Calling Number=5017399(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)
*Jan 8 17:13:23.664: //-1/00D56D761300/CCAPI/ccCheckClipClir:
Out: Calling Number=5017399(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)
*Jan 8 17:13:23.664: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Jan 8 17:13:23.664: :cc_get_feature_vsa malloc success
*Jan 8 17:13:23.664: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Jan 8 17:13:23.664: cc_get_feature_vsa count is 1
*Jan 8 17:13:23.664: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Jan 8 17:13:23.664: :FEATURE_VSA attributes are: feature_name:0,feature_time:717588272,feature_id:67636
*Jan 8 17:13:23.664: //67636/00D56D761300/CCAPI/cc_api_call_setup_ind_common:
Set Up Event Sent;
Call Info(Calling Number=5017399(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
Called Number=80(TON=Unknown, NPI=Unknown))
*Jan 8 17:13:23.664: //67636/00D56D761300/CCAPI/cc_process_call_setup_ind:
Event=0x29CE8C90
*Jan 8 17:13:23.664: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
Try with the demoted called number 80
*Jan 8 17:13:23.664: //67636/00D56D761300/CCAPI/ccCallSetContext:
Context=0x301A14B4
*Jan 8 17:13:23.664: //67636/00D56D761300/CCAPI/cc_process_call_setup_ind:
>>>>CCAPI handed cid 67636 with tag 100 to app "_ManagedAppProcess_Default"
*Jan 8 17:13:23.668: //67636/00D56D761300/CCAPI/ccCallProceeding:
Progress Indication=NULL(0)
*Jan 8 17:13:23.668: //67636/00D56D761300/CCAPI/ccCallSetupRequest:
Destination=, Calling IE Present=TRUE, Mode=0,
Outgoing Dial-peer=80, Params=0x2AAC1AC8, Progress Indication=NULL(0)
*Jan 8 17:13:23.668: //67636/00D56D761300/CCAPI/ccCheckClipClir:
In: Calling Number=5017399(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)
*Jan 8 17:13:23.668: //67636/00D56D761300/CCAPI/ccCheckClipClir:
Out: Calling Number=5017399(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed)
*Jan 8 17:13:23.668: //67636/00D56D761300/CCAPI/ccCallSetupRequest:
Destination Pattern=80, Called Number=80, Digit Strip=TRUE
*Jan 8 17:13:23.668: //67636/00D56D761300/CCAPI/ccCallSetupRequest:
Calling Number=5017399(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
Called Number=80(TON=Unknown, NPI=Unknown),
Redirect Number=, Display Info=
Account Number=5017399, Final Destination Flag=TRUE,
Guid=00D56D76-FB9A-81D2-1300-8101AC107565, Outgoing Dial-peer=80
*Jan 8 17:13:23.668: //67636/00D56D761300/CCAPI/cc_api_display_ie_subfields:
ccCallSetupRequest:
cisco-username=5017399
----- ccCallInfo IE subfields -----
cisco-ani=5017399
cisco-anitype=0
cisco-aniplan=0
cisco-anipi=0
cisco-anisi=1
dest=80
cisco-desttype=0
cisco-destplan=0
cisco-rdie=FFFFFFFF
cisco-rdn=
cisco-lastrdn=
cisco-rdntype=-1
cisco-rdnplan=-1
cisco-rdnpi=-1
cisco-rdnsi=-1
cisco-redirectreason=-1 fwd_final_type =0
final_redirectNumber =
hunt_group_timeout =0

*Jan 8 17:13:23.668: //67636/00D56D761300/CCAPI/ccIFCallSetupRequestPrivate:
Interface=0x29D14800, Interface Type=6, Destination=, Mode=0x0,
Call Params(Calling Number=5017399,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed),
Called Number=80(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,
Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE, Outgoing Dial-peer=80, Call Count On=FALSE,
Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=)
*Jan 8 17:13:23.668: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Jan 8 17:13:23.668: :cc_get_feature_vsa malloc success
*Jan 8 17:13:23.668: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Jan 8 17:13:23.668: cc_get_feature_vsa count is 2
*Jan 8 17:13:23.668: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

*Jan 8 17:13:23.668: :FEATURE_VSA attributes are: feature_name:0,feature_time:717588048,feature_id:67637
*Jan 8 17:13:23.668: //67637/00D56D761300/CCAPI/ccIFCallSetupRequestPrivate:
SPI Call Setup Request Is Success; Interface Type=6, FlowMode=1
*Jan 8 17:13:23.668: //67637/00D56D761300/CCAPI/ccCallSetContext:
Context=0x2AAC1A78
*Jan 8 17:13:23.668: //67636/00D56D761300/CCAPI/ccSaveDialpeerTag:
Outgoing Dial-peer=80
*Jan 8 17:13:23.668: //67637/00D56D761300/CCAPI/cc_api_call_proceeding:
Interface=0x29D14800, Progress Indication=NULL(0)
*Jan 8 17:13:24.920: //67637/00D56D761300/CCAPI/cc_api_call_disconnected:
Cause Value=34, Interface=0x29D14800, Call Id=67637
*Jan 8 17:13:24.920: //67637/00D56D761300/CCAPI/cc_api_call_disconnected:
Call Entry(Responsed=TRUE, Cause Value=34, Retry Count=0)
*Jan 8 17:13:24.920: //67636/xxxxxxxxxxxx/CCAPI/ccCallReleaseResources:
release reserved xcoding resource.
*Jan 8 17:13:24.920: //67637/00D56D761300/CCAPI/ccCallSetAAA_Accounting:
Accounting=0, Call Id=67637
*Jan 8 17:13:24.920: //67637/00D56D761300/CCAPI/ccCallDisconnect:
Cause Value=34, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=34)
*Jan 8 17:13:24.920: //67637/00D56D761300/CCAPI/ccCallDisconnect:
Cause Value=34, Call Entry(Responsed=TRUE, Cause Value=34)
*Jan 8 17:13:24.920: //67637/00D56D761300/CCAPI/cc_api_call_disconnect_done:
Disposition=0, Interface=0x29D14800, Tag=0x0, Call Id=67637,
Call Entry(Disconnect Cause=34, Voice Class Cause Code=0, Retry Count=0)
*Jan 8 17:13:24.920: //67637/00D56D761300/CCAPI/cc_api_call_disconnect_done:
Call Disconnect Event Sent
*Jan 8 17:13:24.920: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

*Jan 8 17:13:24.920: :cc_free_feature_vsa freeing 2AC58648
*Jan 8 17:13:24.920: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

*Jan 8 17:13:24.920: vsacount in free is 1
*Jan 8 17:13:24.920: //67636/00D56D761300/CCAPI/ccCallDisconnect:
Cause Value=34, Tag=0x0, Call Entry(Previous Disconnect Cause=0, Disconnect Cause=0)
*Jan 8 17:13:24.920: //67636/00D56D761300/CCAPI/ccCallDisconnect:
Cause Value=34, Call Entry(Responsed=TRUE, Cause Value=34)
*Jan 8 17:13:24.920: //67636/00D56D761300/CCAPI/cc_api_get_transfer_info:
Transfer Number Is Null
*Jan 8 17:13:24.924: //67636/00D56D761300/CCAPI/cc_api_call_disconnect_done:
Disposition=0, Interface=0x299BE0B4, Tag=0x0, Call Id=67636,
Call Entry(Disconnect Cause=34, Voice Class Cause Code=0, Retry Count=0)
*Jan 8 17:13:24.924: //67636/00D56D761300/CCAPI/cc_api_call_disconnect_done:
Call Disconnect Event Sent
*Jan 8 17:13:24.924: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

*Jan 8 17:13:24.924: :cc_free_feature_vsa freeing 2AC58728
*Jan 8 17:13:24.924: //-1/xxxxxxxxxxxx/CCAPI/cc_free_feature_vsa:

*Jan 8 17:13:24.924: vsacount in free is 0
 
Here is how I have the dial-peer set up:
!
dial-peer voice 80 pots
description *** Overhead paging ***
destination-pattern 80
port 0/1/1
forward-digits 0
!

 
Looks like you're getting there. Have you tried reversing your connections between the FXO and the Bogen? Tip and Ring are polarity sensitive. Try a straight cable or a reversed cable to see if either work.

If not, maybe try the other FXO port on your card.
 
The thing I don't get is why am I still getting the fast busy when the line cord is not even plugged in? that to me rules out the Bogen too. Any thoughts?
 
It's an FXO port and not and FXS so if you do not have anything plugged in it you will get a fast busy.
 
That's why I suggested reversing tip and ring on the cord between the 2. If the FXO doesn't see the correct voltage on the correct wire, it's like having the wire unplugged.
 
OK found the issue, it wasn't an issue with the Cisco it was the outputs on the paging system its self. I had them remove the outputs to the speakers and the paging relays clicked and the tone. Thank you everyone for your post.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top