Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

EX60 Using History to redial missed call fails

All,

   I have a scenario where I have a EX60 (home network) <-> VCS-E <-> VCS-C <-> EX60. We do have TMS, both units registered, if I dial e164 from external device or internal device call is successful BUT if the external device misses a call from internal and I try to use the history tab and call the internal unit, my call fails. Here is what the I see in the VCS-E. The VCS-C is below as well (I removed ome IP and domain info)

VCS-E

2013-09-13T11:20:26-05:00 tvcs: Event="Call Rejected" Service="SIP" Src-ip="external users IP" Src-port="55448" Src-alias-type="SIP" Src-alias="sip:6666@XXX.com" Dst-alias-type="SIP" Dst-alias="sip:brbrow.ex60@XXX.com" Call-serial-number="5a259a0e-1c90-11e3-b878-0050568000d1" Tag="5a259bd0-1c90-11e3-a19e-0050568000d1" Detail="Temporarily Not Available" Protocol="TLS" Response-code="480" Level="1" UTCTime="2013-09-13 16:20:26,897"

2013-09-13T11:20:26-05:00 tvcs: Event="Search Completed" Reason="Temporarily Not Available" Service="SIP" Src-alias-type="SIP" Src-alias="6666@XXX.com" Dst-alias-type="SIP" Dst-alias="sip:brbrow.ex60@XXX.com" Call-serial-number="5a259a0e-1c90-11e3-b878-0050568000d1" Tag="5a259bd0-1c90-11e3-a19e-0050568000d1" Detail="found:false, searchtype:INVITE" Level="1" UTCTime="2013-09-13 16:20:26,897"

2013-09-13T11:20:06-05:00 tvcs: Event="Call Attempted" Service="SIP" Src-ip="external users IP" Src-port="55448" Src-alias-type="SIP" Src-alias="sip:6666@XXX.com" Dst-alias-type="SIP" Dst-alias="sip:brbrow.ex60@XXX.com" Call-serial-number="5a259a0e-1c90-11e3-b878-0050568000d1" Tag="5a259bd0-1c90-11e3-a19e-0050568000d1" Protocol="TLS" Auth="YES" Level="1" UTCTime="2013-09-13 16:20:06,456"

2013-09-13T11:20:06-05:00 tvcs: Event="Search Attempted" Service="SIP" Src-alias-type="SIP" Src-alias="6666@XXX.com" Dst-alias-type="SIP" Dst-alias="sip:brbrow.ex60@XXX.com" Call-serial-number="5a259a0e-1c90-11e3-b878-0050568000d1" Tag="5a259bd0-1c90-11e3-a19e-0050568000d1" Detail="searchtype:INVITE" Level="1" UTCTime="2013-09-13 16:20:06,455"

VCS-C

2013-09-13T11:21:29-05:00 tvcs: Event="Call Rejected" Service="H323" Src-ip="internal IP" Src-port="2776" Src-alias-type="H323" Src-alias="6666@XXX.com" Src-alias-type="E164" Src-alias="6666" Dst-alias-type="H323" Dst-alias="brbrow.ex60@XXX.com" Call-serial-number="855035a4-1c90-11e3-9ec1-0050568000c5" Tag="7f42aade-1c90-11e3-865f-0050568000d1" Protocol="TCP" Response-code="Temporarily Not Available" Level="1" UTCTime="2013-09-13 16:21:29,044"

2013-09-13T11:21:29-05:00 tvcs: Event="Search Completed" Reason="Temporarily Not Available" Service="H323" Src-alias-type="H323" Src-alias="6666@XXX.com" Src-alias-type="E164" Src-alias="6666" Dst-alias-type="H323" Dst-alias="brbrow.ex60@XXX.com" Call-serial-number="855035a4-1c90-11e3-9ec1-0050568000c5" Tag="7f42aade-1c90-11e3-865f-0050568000d1" Detail="found:false, searchtype:Setup" Level="1" UTCTime="2013-09-13 16:21:29,043"

2013-09-13T11:21:18-05:00 tvcs: Event="Search Attempted" Service="H323" Src-alias-type="H323" Src-alias="6666@XXX.com" Src-alias-type="E164" Src-alias="6666" Dst-alias-type="H323" Dst-alias="brbrow.ex60@XXX.com" Call-serial-number="855035a4-1c90-11e3-9ec1-0050568000c5" Tag="7f42aade-1c90-11e3-865f-0050568000d1" Detail="searchtype:Setup" Level="1" UTCTime="2013-09-13 16:21:18,944"

2013-09-13T11:21:18-05:00 tvcs: Event="Call Attempted" Service="H323" Src-ip="internal IP" Src-port="2776" Src-alias-type="H323" Src-alias="6666@XXX.com" Src-alias-type="E164" Src-alias="6666" Dst-alias-type="H323" Dst-alias="brbrow.ex60@XXX.com" Call-serial-number="855035a4-1c90-11e3-9ec1-0050568000c5" Tag="7f42aade-1c90-11e3-865f-0050568000d1" Protocol="TCP" Auth="YES" Level="1" UTCTime="2013-09-13 16:21:18,943"

2013-09-13T11:21:18-05:00 tvcs: Event="Search Completed" Service="H323" Src-alias-type="H323" Src-alias="6666@XXX.com" Dst-alias-type="H323" Dst-alias="brbrow.ex60@XXX.com" Call-serial-number="855035a4-1c90-11e3-9ec1-0050568000c5" Tag="7f42aade-1c90-11e3-865f-0050568000d1" Detail="found:true, searchtype:LRQ" Call-routed="YES" Level="1" UTCTime="2013-09-13 16:21:18,923"

2013-09-13T11:21:18-05:00 tvcs: Event="Search Attempted" Service="H323" Src-alias-type="H323" Src-alias="6666@XXX.com" Dst-alias-type="H323" Dst-alias="brbrow.ex60@XXX.com" Call-serial-number="855035a4-1c90-11e3-9ec1-0050568000c5" Tag="7f42aade-1c90-11e3-865f-0050568000d1" Detail="searchtype:LRQ" Level="1" UTCTime="2013-09-13 16:21:18,875"

Because I am fairly new at troubleshooting these untis, I didnt pull any other logs. It almost looks to me like I am having issues with SIP to H323 calls. I will continue digging but was wondering if one of you could point me in the right direction.

Thanks

   Greg

2 ACCEPTED SOLUTIONS

Accepted Solutions

Re: EX60 Using History to redial missed call fails

Some additional remarks.

* please describe your deployment a bit better (network, and telepresene config, ... (also incl what Paulo asked for).

* do you have any bandwidth restrictions, default links present, call policies or other things in place?

* does it happen all the time or random / sometimes it works / ...?

* it looks the call back was a sip call. Is this the intention, what was the original, now returend call,

what is the default call protocoll on the endpoint and are the zones up properly?

* if you are using e164 numbers and only the vcs I would either use h323 as the default call protocol

or see that you get enum up and running so a call can stay in protocol all the time.

* did you check that all traversal zones are properly up?

* no ALG / Inspection or other layer3 h323/sip stuff active?

* search rules ok?

* any authentication used?

* registration of the endpoints ok?

* do you use a cluster? we noticed a bug which is still present in X7.2.2 (though it is said it was fixed).

If the call to e a164 number is hitting the VCS where the endpoint is NOT registered, the call will fail.

It could help us as well to see some screenshots of the registrations and the search history and search details.

Please remember to rate helpful responses and identify helpful or correct answers.

Please remember to rate helpful responses and identify

Community Member

Re: EX60 Using History to redial missed call fails

It was actually a search rule that didnt have continue. Thanks for your help.

4 REPLIES

Re: EX60 Using History to redial missed call fails

Are you using FindMe and Provisioning?

Paulo Souza


Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".

Paulo Souza Was my response helpful? Please rate useful replies and remember to mark any solved questions as "answered".

Re: EX60 Using History to redial missed call fails

Some additional remarks.

* please describe your deployment a bit better (network, and telepresene config, ... (also incl what Paulo asked for).

* do you have any bandwidth restrictions, default links present, call policies or other things in place?

* does it happen all the time or random / sometimes it works / ...?

* it looks the call back was a sip call. Is this the intention, what was the original, now returend call,

what is the default call protocoll on the endpoint and are the zones up properly?

* if you are using e164 numbers and only the vcs I would either use h323 as the default call protocol

or see that you get enum up and running so a call can stay in protocol all the time.

* did you check that all traversal zones are properly up?

* no ALG / Inspection or other layer3 h323/sip stuff active?

* search rules ok?

* any authentication used?

* registration of the endpoints ok?

* do you use a cluster? we noticed a bug which is still present in X7.2.2 (though it is said it was fixed).

If the call to e a164 number is hitting the VCS where the endpoint is NOT registered, the call will fail.

It could help us as well to see some screenshots of the registrations and the search history and search details.

Please remember to rate helpful responses and identify helpful or correct answers.

Please remember to rate helpful responses and identify

Community Member

Re: EX60 Using History to redial missed call fails

It was actually a search rule that didnt have continue. Thanks for your help.

EX60 Using History to redial missed call fails

Hi Greg!

Thank you for the feedback!

Please remember to rate helpful responses and identify helpful or correct answers.

Please remember to rate helpful responses and identify

404
Views
0
Helpful
4
Replies
CreatePlease to create content