MGCP FXO calling name not displaying

[Ayaz Khan]

Hello,

I have Cisco 2901 GW configured as MGCP.  IOS version 15.0(1r)M12.  We are not getting Calling name, it is appearing as "O".  Calling number is working fine.  The only option I can find to turn on this feature is under the voice port, Caller-id enable.

If anyone has encountered this problem or has any ideas please let me know.  If more infomration is requied please let me know.

Thanks,

Debug voice ccapi inout

ABOY-MA-VG-01#ter mon
ABOY-MA-VG-01#
Jun 22 11:07:08.378 EDT: //-1/C522BD518768/CCAPI/cc_api_display_ie_subfields:
   cc_api_call_setup_ind_common:
   cisco-username=
   ----- ccCallInfo IE subfields -----
   cisco-ani=19058476800
   cisco-anitype=0
   cisco-aniplan=0
   cisco-anipi=0
   cisco-anisi=0
   dest=8250
   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 22 11:07:08.378 EDT: //-1/C522BD518768/CCAPI/cc_api_call_setup_ind_common:
   Interface=0x30D4DCD4, Call Info(
   Calling Number=19058476800,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=8250(TON=Unknown, NPI=Unknown),
   Calling Translated=FALSE, Subscriber Type Str=RegularLine, FinalDestinationFlag=TRUE,
   Incoming Dial-peer=999000, Progress Indication=ORIGINATING SIDE IS NON ISDN(3), Calling IE Present=TRUE,
   Source Trkgrp Route Label=, Target Trkgrp Route Label=, CLID Transparent=FALSE), Call Id=-1
Jun 22 11:07:08.378 EDT: //-1/C522BD518768/CCAPI/ccCheckClipClir:
   In: Calling Number=19058476800(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
Jun 22 11:07:08.378 EDT: //-1/C522BD518768/CCAPI/ccCheckClipClir:
   Out: Calling Number=19058476800(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed)
Jun 22 11:07:08.378 EDT: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Jun 22 11:07:08.378 EDT: :cc_get_feature_vsa malloc success
Jun 22 11:07:08.378 EDT: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Jun 22 11:07:08.378 EDT:  cc_get_feature_vsa count is 1
Jun 22 11:07:08.378 EDT: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa:

Jun 22 11:07:08.378 EDT: :FEATURE_VSA attributes are: feature_name:0,feature_time:716741080,feature_id:779
Jun 22 11:07:08.378 EDT: //754/C522BD518768/CCAPI/cc_api_call_setup_ind_common:
   Set Up Event Sent;
   Call Info(Calling Number=19058476800(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=8250(TON=Unknown, NPI=Unknown))
Jun 22 11:07:08.378 EDT: //754/C522BD518768/CCAPI/cc_process_call_setup_ind:
   Event=0x30D2F298
Jun 22 11:07:08.378 EDT: //-1/xxxxxxxxxxxx/CCAPI/cc_setupind_match_search:
   Try with the demoted called number 8250
Jun 22 11:07:08.378 EDT: //754/C522BD518768/CCAPI/cc_process_call_setup_ind:
   >>>>CCAPI handed cid 754 with tag 999000 to app "MGCPAPP"
Jun 22 11:07:08.378 EDT: //754/C522BD518768/CCAPI/ccCallSetContext:
   Context=0x31986C30
Jun 22 11:07:08.378 EDT: //754/C522BD518768/CCAPI/ccCallSetupAck:
   Call Id=754
Jun 22 11:07:08.378 EDT: //754/C522BD518768/CCAPI/cc_api_set_transfer_info:
   Transfer Number=, Transfer Reason=0x0
Jun 22 11:07:08.378 EDT: //754/C522BD518768/CCAPI/ccCallConnect:
   Progress Indication=NULL(0), Data Bitmask=0x0
Jun 22 11:07:08.378 EDT: //754/C522BD518768/CCAPI/ccCallConnect:
   Call Entry(Connected=TRUE, Responsed=TRUE)
Jun 22 11:07:08.386 EDT: //754/C522BD518768/CCAPI/ccCallModify:
   Nominator=0x1, Params=0x31890370, Call Id=754
Jun 22 11:07:08.386 EDT: //-1/xxxxxxxxxxxx/CCAPI/ccIFCallSetupRequestPrivate:
   Interface=0x2B32E584, Interface Type=9, Destination=0.0.0.0, Mode=0x9,
   Call Params(Calling Number=,(Calling Name=)(TON=Unknown, NPI=Unknown, Screening=Not Screened, Presentation=Allowed),
   Called Number=(TON=Unknown, NPI=Unknown), Calling Translated=FALSE,

[Ayodeji Okanlawon]

The caller-id enable is used for displaying the calling number on fxs ports not the caller name. Infact until cucm 8.x and above, fxo with mgcp gateway did not support caller-id. I do not know if this can support calling name. Does your provider even send the caller name to the gateway? or is this on the outbound direction?

Please rate useful posts

"For the love of God is broader than the measure of man's mind And the heart of the Eternal is most wonderfully kind"

[paolo bevilacqua]

Thta is 'normal' with MGCP. Use H.323 or SIP, and everything will work fine.

[bill.roland]

Caller ID name and Number does work using FXO ports under MGCP control, we've got it running on 4 different 2901's at different sites.  We had a lot of trouble with it at first as well, Cisco TAC advised us to configure "answer-address .T" on the existing MGCP dial-peers and it has worked fine ever since.

Hope that helps.

[Utkarsh Singh]

Hi,

As mentioned above after adding "answer-address .T" has resolved issue of caller ID name on FXO port. Is this possible below 8.X call manager version. Please advice is there anyway i can see Caller ID name on fxo port which is registered through MGCP and CM 7.1 version.

Regards,

NN

[pcabarga]

Confirmed, "answer-address .T" on MGCP dial peers did the trick for me also.

Thanks.

[mlinsemier]

Adding "answer-address .T" on MGCP fixed this for me as well!  Thanks so much Bill.  Another golden nugget for my internal voip database.

[warquezho0612]

Where do you put the answer-address .T? Is it under the preconfigured MGCP dial-peers where the FXO port number receives the call?

Like if the call comming from fxo 0/1/0 and it has a corresponding dial-peer, is it there where we will put the answer-address .T?

[mlinsemier]

Here is an example of how we have it on our MGCP dial peers.

dial-peer voice 999010 pots
service mgcpapp
answer-address .T
port 0/1/0
!
dial-peer voice 999011 pots
service mgcpapp
answer-address .T
port 0/1/1
!
dial-peer voice 999012 pots
service mgcpapp
answer-address .T
port 0/1/2
!
dial-peer voice 999013 pots
service mgcpapp
answer-address .T
port 0/1/3

[Dave Tuell]

Try configuring "caller-id alerting ring 2" against the FXO voice-port. This will resolve the issue where the telco is only providing the caller ID after initially ringing the phone and then "shut" and "no shut" the port. If that does not work can you try changing to "caller-id alerting ring 3".

[warquezho0612]

I see now where to put the answer address, but the problem is when using MGCP and FXO port and configuring Attendant DN under MGCP's fxo port, when the caller calls the fxo and transfer to a certain number, the call is automatically answered even though the callee's phone is still ringing, any solution to this?

[paolo bevilacqua]

warquezho0612 wrote:
I see now where to put the answer address, but the problem is when using MGCP and FXO port and configuring Attendant DN under MGCP's fxo port, when the caller calls the fxo and transfer to a certain number, the call is automatically answered even though the callee's phone is still ringing, any solution to this?

Not with MGCP, if you want the call not to be answered until called phone answers, use H.323 and "connection plar opx".

[warquezho0612]

Thats what I thought, everything is almost perfect with MGCP until cisco can find a solution to this automatic answer in fxo port, but until then h323 is a must

[paolo bevilacqua]

Cisco will not do anything. Customers do not care if the call is answered or not.

[warquezho0612]

But in some other country (like mine) when using your mobile number and you call to a local number using MGCP in fxo, the caller is already being charge even though the callee is not yet answering the call. I guess cisco doesn't care if thats the case is some places