11-09-2020 12:36 AM
I have implemented a SIP Server that I am using for basic call recording using a built-in bridge. I process SIP INVITEs and BYEs for call initiating and processing. It works fine for inbound and outbound calls. The issue is with internal calls when an agent calls to another agent where recording is enabled on both phones. Each phone sends INVITE for itself and the other phone and in this way, I get four invites. In inbound and outbound calls, I get two Invites, one for agent phone and other from customer phone (from gateway).
Is there any informations in SIP Invites that I can use to ignore two of the invites?
below are the invites that I get when a call is made from a phone to another (Both CUCM phones and recording enabled).
INVITE sip:88888@192.168.1.x.x:5060 SIP/2.0 Via: SIP/2.0/TCP 192.168..x.x:5060;branch=z9hG4bK2095e06f3b8;rport=58747 From: <sip:2400@192.168..x.x;x-nearend;x-refci=27425142;x-nearendclusterid=BR-Cluster2;x-nearenddevice=SEPD0C282D15AAF;x-nearendaddr=2400;x-farendrefci=27425141;x-farendclusterid=BR-Cluster2;x-farenddevice=sikander1;x-farendaddr=2701>;tag=519~00d3be95-408b-41c6-90cf-01ef66258892-27425149 To: <sip:88888@192.168.1.124> Date: Mon, 09 Nov 2020 07:13:13 GMT Call-ID: 6649000-fa81ec09-1f6-3001a8c0@192.168..x.x Supported: timer,resource-priority,replaces,X-cisco-srtp-fallback,Geolocation Min-SE: 120 User-Agent: Cisco-CUCM11.5 Allow: INVITE,OPTIONS,INFO,BYE,CANCEL,ACK,PRACK,UPDATE,REFER,SUBSCRIBE,NOTIFY CSeq: 101 INVITE Expires: 180 Allow-Events: presence,kpml Call-Info: <sip:192.168..x.x:5060>;method="NOTIFY;Event=telephone-event;Duration=500" Session-ID: 00000000000000000000000000000000;remote=00000000000000000000000000000000 Cisco-Guid: 0107253760-0000065536-0000000011-0805415104 Session-Expires: 120 P-Asserted-Identity: <sip:2400@192.168..x.x> Remote-Party-ID: <sip:2400@192.168..x.x>;party=calling;screen=yes;privacy=off Contact: <sip:2400@192.168..x.x:5060;transport=tcp>;isFocus Max-Forwards: 70 Content-Length: 0 ----------------------------------------- INVITE sip:88888@192.168.x.x:5060 SIP/2.0 Via: SIP/2.0/TCP 192.168.x.x:5060;branch=z9hG4bK20a2071bec;rport=58747 From: <sip:2701@192.168.x.x;x-nearend;x-refci=27425141;x-nearendclusterid=BR-Cluster2;x-nearenddevice=sikander1;x-nearendaddr=2701;x-farendrefci=27425142;x-farendclusterid=BR-Cluster2;x-farenddevice=SEPD0C282D15AAF;x-farendaddr=2400>;tag=520~00d3be95-408b-41c6-90cf-01ef66258892-27425150 To: <sip:88888@192.168..x.x> Date: Mon, 09 Nov 2020 07:13:13 GMT Call-ID: 6649000-fa81ec09-1f7-3001a8c0@192.168..x.x Supported: timer,resource-priority,replaces,X-cisco-srtp-fallback,Geolocation Min-SE: 120 User-Agent: Cisco-CUCM11.5 Allow: INVITE,OPTIONS,INFO,BYE,CANCEL,ACK,PRACK,UPDATE,REFER,SUBSCRIBE,NOTIFY CSeq: 101 INVITE Expires: 180 Allow-Events: presence,kpml Call-Info: <sip:192.168..x.x:5060>;method="NOTIFY;Event=telephone-event;Duration=500" Session-ID: 00000000000000000000000000000000;remote=00000000000000000000000000000000 Cisco-Guid: 0107253760-0000065536-0000000012-0805415104 Session-Expires: 120 P-Asserted-Identity: <sip:2701@192.168..x.x> Remote-Party-ID: <sip:2701@192.168.1.x.x>;party=calling;screen=yes;privacy=off Contact: <sip:2701@192.168.x.x:5060;transport=tcp>;isFocus Max-Forwards: 70 Content-Length: 0 ------------------------- INVITE sip:88888@192.168..x.x:5060 SIP/2.0 Via: SIP/2.0/TCP 192.168..x.x:5060;branch=z9hG4bK20b5eb383e9;rport=58747 From: <sip:2400@192.168..x.x;x-farend;x-refci=27425142;x-nearendclusterid=BR-Cluster2;x-nearenddevice=SEPD0C282D15AAF;x-nearendaddr=2400;x-farendrefci=27425141;x-farendclusterid=BR-Cluster2;x-farenddevice=sikander1;x-farendaddr=2701>;tag=521~00d3be95-408b-41c6-90cf-01ef66258892-27425155 To: <sip:88888@192.168..x.x> Date: Mon, 09 Nov 2020 07:13:13 GMT Call-ID: 6649000-fa81ec09-1f8-3001a8c0@192.168..x.x Supported: timer,resource-priority,replaces,X-cisco-srtp-fallback,Geolocation Min-SE: 120 User-Agent: Cisco-CUCM11.5 Allow: INVITE,OPTIONS,INFO,BYE,CANCEL,ACK,PRACK,UPDATE,REFER,SUBSCRIBE,NOTIFY CSeq: 101 INVITE Expires: 180 Allow-Events: presence,kpml Call-Info: <sip:192.168..x.x:5060>;method="NOTIFY;Event=telephone-event;Duration=500" Session-ID: 00000000000000000000000000000000;remote=00000000000000000000000000000000 Cisco-Guid: 0107253760-0000065536-0000000013-0805415104 Session-Expires: 120 P-Asserted-Identity: <sip:2400@192.168.x.x> Remote-Party-ID: <sip:2400@192.168..x.x>;party=calling;screen=yes;privacy=off Contact: <sip:2400@192.168..x.x:5060;transport=tcp>;isFocus Max-Forwards: 70 Content-Length: 0 ------------------------- INVITE sip:88888@192.168.1.124:5060 SIP/2.0 Via: SIP/2.0/TCP 192.168..x.x:5060;branch=z9hG4bK20c2f880eb2;rport=58747 From: <sip:2701@192.168..x.x;x-farend;x-refci=27425141;x-nearendclusterid=BR-Cluster2;x-nearenddevice=sikander1;x-nearendaddr=2701;x-farendrefci=27425142;x-farendclusterid=BR-Cluster2;x-farenddevice=SEPD0C282D15AAF;x-farendaddr=2400>;tag=522~00d3be95-408b-41c6-90cf-01ef66258892-27425156 To: <sip:88888@192.168.1.124> Date: Mon, 09 Nov 2020 07:13:13 GMT Call-ID: 6649000-fa81ec09-1f9-3001a8c0@192.168..x.x Supported: timer,resource-priority,replaces,X-cisco-srtp-fallback,Geolocation Min-SE: 120 User-Agent: Cisco-CUCM11.5 Allow: INVITE,OPTIONS,INFO,BYE,CANCEL,ACK,PRACK,UPDATE,REFER,SUBSCRIBE,NOTIFY CSeq: 101 INVITE Expires: 180 Allow-Events: presence,kpml Call-Info: <sip:192.168..x.x:5060>;method="NOTIFY;Event=telephone-event;Duration=500" Session-ID: 00000000000000000000000000000000;remote=00000000000000000000000000000000 Cisco-Guid: 0107253760-0000065536-0000000014-0805415104 Session-Expires: 120 P-Asserted-Identity: <sip:2701@192.168..x.x> Remote-Party-ID: <sip:2701@192.168..x.x>;party=calling;screen=yes;privacy=off Contact: <sip:2701@192.168..x.x:5060;transport=tcp>;isFocus Max-Forwards: 70 Content-Length: 0
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide