Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| vendors:cisco:uc:ucce:mobileagents [2020/12/16 11:23] – [Gateway Recording - Extended Media Forking Configuration] gerardorourke | vendors:cisco:uc:ucce:mobileagents [2025/04/25 10:32] (current) – [References] gerardorourke | ||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ==== References ==== | ==== References ==== | ||
| - | *[[https:// | + | *[[https:// |
| *[[https:// | *[[https:// | ||
| *[[https:// | *[[https:// | ||
| 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 | + | * 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 253: | Line 254: | ||
| </ | </ | ||
| + | ==== Access List for XMF ==== | ||
| + | Before applying below - confirm that no other application or user requires access to the HTTP server running on the gateway! | ||
| + | But in our case the only application using the http server is the XMF application and hence we only allow access to the http server from the CUCM Subscribers which are registered to the XMF server. | ||
| + | |||
| + | < | ||
| + | ! | ||
| + | ip http server | ||
| + | ip http access-class ipv4 80 | ||
| + | no ip http secure-server | ||
| + | ip http max-connections 50 | ||
| + | ip http timeout-policy idle 600 life 86400 requests 86400 | ||
| + | ip http client source-interface GigabitEthernet0/ | ||
| + | ! | ||
| + | access-list 80 permit 10.1.1.101 | ||
| + | access-list 80 permit 10.1.1.102 | ||
| + | ! | ||
| + | </ | ||