Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
vendors:cisco:uc:ucce:mobileagents [2021/08/27 11:03] – [Access List for XMF] gerardorourkevendors:cisco:uc:ucce:mobileagents [2025/04/25 10:32] (current) – [References] gerardorourke
Line 2: Line 2:
  
 ==== References ==== ==== References ====
-  *[[https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_11_0_1/Configuration/Guide/UCCE_BK_S5702DCF_00_ucce-features-guide/UCCE_BK_S5702DCF_00_ucce-features-guide_chapter_0100.html|UCCE Feature Reference - Mobile Agent]]+  *[[https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_12_6_1/configuration/guide/ucce_b_features-guide-1261/ucce_m_mobile_agent-1261.html|UCCE Feature Reference - Mobile Agent]]
   *[[https://www.cisco.com/c/en/us/support/docs/customer-collaboration/unified-contact-center-enterprise-1001/213399-configure-mobile-agent-on-ucce.html|Connect Tone on Nailed Up Connections]]   *[[https://www.cisco.com/c/en/us/support/docs/customer-collaboration/unified-contact-center-enterprise-1001/213399-configure-mobile-agent-on-ucce.html|Connect Tone on Nailed Up Connections]]
   *[[https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/CUCIS_API/CUCIS_API_Guide/CUCISA_OVR.html|Unified Communication Gateway Services API]]   *[[https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucme/CUCIS_API/CUCIS_API_Guide/CUCISA_OVR.html|Unified Communication Gateway Services API]]
Line 169: Line 169:
 Since it is NOT possible to bind the RTP stream for eXtended Media Forking. You must make sure the SIP signally binds to the Physical interface. THis means the Orginating IP address that is included in the SIP header and recieved CVP will be set to CUCM. This IP address must the SIP trunk. Since it is NOT possible to bind the RTP stream for eXtended Media Forking. You must make sure the SIP signally binds to the Physical interface. THis means the Orginating IP address that is included in the SIP header and recieved CVP will be set to CUCM. This IP address must the SIP trunk.
 And also when CUCM sends the Recorder the SIP invite for the CallRecording Call, it gives the SIP trunk as the RTP source. And also when CUCM sends the Recorder the SIP invite for the CallRecording Call, it gives the SIP trunk as the RTP source.
-Verint (and I am sure others) Recorders will NOT record the call if it stream comes from a different address.+  * Verint Recorders will NOT record the call if it stream comes from a different address. 
 +  * Redbox / Uniphore records are not so fussy - and so do not have this issue.
  
 There is a feature enhancment so you can bind the RTP for XMF in future....\\ There is a feature enhancment so you can bind the RTP for XMF in future....\\
Line 260: Line 261:
 ! !
 ip http server ip http server
-ip http access-class 80+ip http access-class ipv4 80
 no ip http secure-server no ip http secure-server
 ip http max-connections 50 ip http max-connections 50
  • vendors/cisco/uc/ucce/mobileagents.1630058614.txt.gz
  • Last modified: 2021/08/27 11:03
  • by gerardorourke