cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Please be advised, the GuideMe Wizard is no longer available on the Small Business Support Community. For search capability please use the community search field to find content related to Cisco Small Business documents, videos, and discussions.
766
Views
0
Helpful
5
Replies
Highlighted

AA working internally but Fails for external FXO lines.

Hi Everyone,

One of our client having UC520 has issue with Voicemail.

When i dial internally with ip phone it works fine but externally AA fails.

Pls check the debug:

Jun 13 08:22:23.613: //-1/BC9155439722/CCAPI/cc_api_display_ie_subfields:

cc_api_call_setup_ind_common:

cisco-username=

----- ccCallInfo IE subfields -----

cisco-ani=

cisco-anitype=0

cisco-aniplan=0

cisco-anipi=0

cisco-anisi=0

dest=280

cisco-desttype=0

cisco-destplan=0

cisco-rdie=FFFFFFFF

cisco-rdn=

cisco-rdntype=0

cisco-rdnplan=0

cisco-rdnpi=0

cisco-rdnsi=0

cisco-redirectreason=0 fwd_final_type =0

final_redirectNumber =

hunt_group_timeout =0

Jun 13 08:22:23.613: //-1/BC9155439722/CCAPI/cc_api_call_setup_ind_common:

Interface=0x851B9968, Call Info(

Calling Number=,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),

Called Number=280(TON=Unknown, NPI=Unknown),

Calling Translated=FALSE, Subscriber Type Str=RegularLine, FinalDestinationFlag=TRUE,

Incoming Dial-peer=152, Progress Indication=ORIGINATING SIDE IS NON ISDN(3), Calling IE Present=FALSE,

Source Trkgrp Route Label=ALL_FXO, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=-1

Jun 13 08:22:23.613: //-1/BC9155439722/CCAPI/ccCheckClipClir:

In: Calling Number=(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)

Jun 13 08:22:23.613: //-1/BC9155439722/CCAPI/ccCheckClipClir:

Out: Calling Number=(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)

Jun 13 08:22:23.613: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Jun 13 08:22:23.613: :cc_get_feature_vsa malloc success

Jun 13 08:22:23.613: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Jun 13 08:22:23.613: cc_get_feature_vsa count is 3

Jun 13 08:22:23.613: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Jun 13 08:22:23.613: :FEATURE_VSA attributes are: feature_name:0,feature_time:2232919864,feature_id:152533

Jun 13 08:22:23.613: //130313/BC9155439722/CCAPI/cc_api_call_setup_ind_common:

Set Up Event Sent;

Call Info(Calling Number=(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),

Called Number=280(TON=Unknown, NPI=Unknown))

Jun 13 08:22:23.613: //130313/BC9155439722/CCAPI/cc_process_call_setup_ind:

Event=0x85180048

Jun 13 08:22:23.617: //130313/BC9155439722/CCAPI/ccCallSetContext:

Context=0x876FF510

Jun 13 08:22:23.617: //130313/BC9155439722/CCAPI/cc_process_call_setup_ind:

>>>>CCAPI handed cid 130313 with tag 152 to app "_ManagedAppProcess_Default"

Jun 13 08:22:23.617: //130313/BC9155439722/CCAPI/ccCallProceeding:

Progress Indication=NULL(0)

Jun 13 08:22:23.617: //130313/BC9155439722/CCAPI/ccCallSetupRequest:

Destination=, Calling IE Present=FALSE, Mode=0,

Outgoing Dial-peer=2001, Params=0x846AF118, Progress Indication=ORIGINATING SIDE IS NON ISDN(3)

Jun 13 08:22:23.621: //130313/BC9155439722/CCAPI/ccCheckClipClir:

In: Calling Number=(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)

Jun 13 08:22:23.621: //130313/BC9155439722/CCAPI/ccCheckClipClir:

Out: Calling Number=(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)

Jun 13 08:22:23.621: //130313/BC9155439722/CCAPI/ccCallSetupRequest:

Destination Pattern=280, Called Number=280, Digit Strip=FALSE

Jun 13 08:22:23.621: //130313/BC9155439722/CCAPI/ccCallSetupRequest:

Calling Number=(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),

Called Number=280(TON=Unknown, NPI=Unknown),

Redirect Number=, Display Info=

Account Number=, Final Destination Flag=TRUE,

Guid=BC915543-B467-11E1-9722-A022D714BE6A, Outgoing Dial-peer=2001

Jun 13 08:22:23.621:

                  

Everyone's tags (4)
5 REPLIES 5

AA working internally but Fails for external FXO lines.

I forgot to mention the 280 is our AA number.

Re: AA working internally but Fails for external FXO lines.

Hi,

What exactly fails the connection to the AA or the AA forwarding.

You may need to check for transcoding if you are using alaw.

What is the IOS, CUE version?

HTH,

Alex

AA working internally but Fails for external FXO lines.

The IOS is  12.4 and cue version is 3.x

When i check the logs on cue what i find is call is actually coming to cue but AA is not playing the message.

but as i told everything is working fine internally.

I dont know but can we configure "Codecs" on FXO ports????(I dont think so).

All the dial-peers are using g711u law and this is UC520.

AA working internally but Fails for external FXO lines.

Actually when i tested with forwarding all the calls to a single extension the bell is ringing and when we lift the handset the call gets disconnected. Maybe this could be the issue why calls were failing with AA.

Can anybody advice something otherthan no battery reversal.

AA working internally but Fails for external FXO lines.

Hi,

You can try with some of the settings on the following link:

http://www.cisco.com/en/US/docs/ios/12_2t/12_2t2/feature/guide/ft_ansds.html

HTH,

Alex