- FreeSWITCH-users - FreeSWITCH Mailing Lists

Logical OR in conditions
by Matthew Ralston 09 Jun '11

09 Jun '11

Hi, What is the correct condition->break value to use in order to create a logical OR with conditions? I have two extensions which I'd like to merge into one. I'd like the actions to be run if either of the conditions matches: <extension name="call_forward_enable"> <condition field="destination_number" expression="^\*21\*([0-9]+)#$"> <action application="javascript" data="callForwardEnable.js"/> <action application="hangup"/> </condition> </extension>  <extension name="call_forward_enable"> <condition field="destination_number" expression="^7217([0-9]+)9$"> <action application="javascript" data="callForwardEnable.js"/> <action application="hangup"/> </condition> </extension> So the result would be something like: <extension name="call_forward_enable"> <condition field="destination_number" expression="^\*21\*([0-9]+)#$" break="on-true" /> <condition field="destination_number" expression="^7217([0-9]+)9$"> <action application="javascript" data="callForwardEnable.js"/> <action application="hangup"/> </condition> </extension> I can't seem to get it to work and my brain is melting trying to wrap my head around the different break values. Cheers, Matt

2 2

FS response
by Alessandro Luppi 09 Jun '11

09 Jun '11

Hi, I have the following scenario: If the softphone2 respond with 486 freeswitch is working in this way: softphone1 FS softphone2 INVITE ----------> INVITE ---------------> <------------------- 486 <-------------- 200 ACK ------------------> ACK ------------> <-------------- BYE i want this behaviour: softphone1 FS softphone2 INVITE ----------> INVITE ---------------> <------------------- 486 <-------------- 486 ACK ------------------> ACK ------------> Any suggestion? Regards Alessandro

4 3

FreeTDM does not work
by Valery Kalinin 09 Jun '11

09 Jun '11

Hi all! FreeTDM does not work with Digium equipment. Equipment: Digium TE121 OS: CentOS 5.6 DAHDI: 2.4.1.2 # ./dahdi_scan [1] active=yes alarms=OK description=Wildcard TE121 Card 0 name=WCT1/0 manufacturer=Digium devicetype=Wildcard TE121 (VPMADT032) location=PCI Bus 04 Slot 09 basechan=1 totchans=31 irq=5 type=digital-E1 syncsrc=1 lbo=0 db (CSU)/0-133 feet (DSX-1) coding_opts=AMI,HDB3 framing_opts=CCS,CRC4 coding=HDB3 framing=CCS LIBPRI: 1.4.11.5 zt.conf [defaults] codec_ms => 20 wink_ms => 150 flash_ms => 750 echo_cancel_level => 64 rxgain => 0.0 txgain => 0.0 freetdm.conf [span zt pri] name => pri trunk_type => E1 group => e1group b-channel => 1-15 b-channel => 17-31 d-channel => 16 part of freetdm.conf.xml: <libpri_spans> <span id="1" name="pri"> <param name="node" value="network"/> <param name="switch" value="4ess"/> <param name="l1" value="alaw"/> <param name="dp" value="unknown"/> <param name="debug" value="q931_all"/> <param name="dialplan" value="XML"/> <param name="context" value="default"/> </span> </libpri_spans> and log result (important parts): start freetdm: 2011-06-09 02:07:00.591482 [DEBUG] ftdm_config.c:52 New mod directory: /usr/local/freeswitch/mod 2011-06-09 02:07:00.591492 [DEBUG] ftdm_config.c:58 New config directory: /usr/local/freeswitch/conf 2011-06-09 02:07:00.591539 [DEBUG] ftdm_sched.c:154 Initializing scheduling API 2011-06-09 02:07:00.591545 [DEBUG] ftdm_sched.c:251 Created schedule freetdm-master 2011-06-09 02:07:00.591551 [NOTICE] ftdm_sched.c:178 Launching main schedule thread 2011-06-09 02:07:00.591581 [DEBUG] ftdm_sched.c:187 Running schedule freetdm-master in the main schedule thread 2011-06-09 02:07:00.591592 [DEBUG] ftdm_config.c:80 Configuration file is /usr/local/freeswitch/conf/modules.conf. 2011-06-09 02:07:00.591639 [NOTICE] ftdm_io.c:5656 Modules configured: 1 2011-06-09 02:07:00.591645 [DEBUG] ftdm_config.c:80 Configuration file is /usr/local/freeswitch/conf/freetdm.conf. 2011-06-09 02:07:00.591659 [DEBUG] ftdm_io.c:4595 Reading FreeTDM configuration file 2011-06-09 02:07:00.591679 [DEBUG] ftdm_io.c:4611 found config for span 2011-06-09 02:07:00.591783 [NOTICE] ftmod_zt.c:1300 Using DAHDI control device 2011-06-09 02:07:00.591794 [INFO] ftdm_io.c:4898 Loading IO from /usr/local/freeswitch/mod/ftmod_zt.so [zt] 2011-06-09 02:07:00.591814 [DEBUG] ftdm_config.c:80 Configuration file is /usr/local/freeswitch/conf/zt.conf. 2011-06-09 02:07:00.591840 [INFO] ftmod_zt.c:577 Setting rxgain val to 0.000000 2011-06-09 02:07:00.591846 [INFO] ftmod_zt.c:585 Setting txgain val to 0.000000 2011-06-09 02:07:00.591860 [INFO] ftdm_io.c:790 Auto-loaded I/O module 'zt' 2011-06-09 02:07:00.591885 [DEBUG] ftdm_io.c:4625 created span 1 (pri) of type zt 2011-06-09 02:07:00.591890 [DEBUG] ftdm_io.c:4641 span 1 [name]=[pri] 2011-06-09 02:07:00.591896 [DEBUG] ftdm_io.c:4641 span 1 [trunk_type]=[E1] 2011-06-09 02:07:00.591902 [DEBUG] ftdm_io.c:4646 setting trunk type to 'E1' 2011-06-09 02:07:00.591907 [DEBUG] ftdm_io.c:4641 span 1 [group]=[e1group] 2011-06-09 02:07:00.591912 [DEBUG] ftdm_io.c:4641 span 1 [b-channel]=[1-15] 2011-06-09 02:07:00.591940 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 1 as FreeTDM device 1:1 fd:25 2011-06-09 02:07:00.591963 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 2 as FreeTDM device 1:2 fd:26 2011-06-09 02:07:00.591984 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 3 as FreeTDM device 1:3 fd:27 2011-06-09 02:07:00.592006 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 4 as FreeTDM device 1:4 fd:28 2011-06-09 02:07:00.592029 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 5 as FreeTDM device 1:5 fd:29 2011-06-09 02:07:00.592049 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 6 as FreeTDM device 1:6 fd:30 2011-06-09 02:07:00.592069 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 7 as FreeTDM device 1:7 fd:31 2011-06-09 02:07:00.592090 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 8 as FreeTDM device 1:8 fd:32 2011-06-09 02:07:00.592110 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 9 as FreeTDM device 1:9 fd:33 2011-06-09 02:07:00.592131 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 10 as FreeTDM device 1:10 fd:34 2011-06-09 02:07:00.592151 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 11 as FreeTDM device 1:11 fd:35 2011-06-09 02:07:00.592171 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 12 as FreeTDM device 1:12 fd:36 2011-06-09 02:07:00.592192 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 13 as FreeTDM device 1:13 fd:37 2011-06-09 02:07:00.592212 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 14 as FreeTDM device 1:14 fd:38 2011-06-09 02:07:00.592231 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 15 as FreeTDM device 1:15 fd:39 2011-06-09 02:07:00.592239 [DEBUG] ftdm_io.c:5200 Creating new group:e1group 2011-06-09 02:07:00.592275 [DEBUG] ftdm_io.c:4641 span 1 [b-channel]=[17-31] 2011-06-09 02:07:00.592299 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 17 as FreeTDM device 1:16 fd:40 2011-06-09 02:07:00.592323 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 18 as FreeTDM device 1:17 fd:41 2011-06-09 02:07:00.592348 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 19 as FreeTDM device 1:18 fd:42 2011-06-09 02:07:00.592369 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 20 as FreeTDM device 1:19 fd:43 2011-06-09 02:07:00.592390 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 21 as FreeTDM device 1:20 fd:44 2011-06-09 02:07:00.592422 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 22 as FreeTDM device 1:21 fd:45 2011-06-09 02:07:00.592442 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 23 as FreeTDM device 1:22 fd:46 2011-06-09 02:07:00.592462 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 24 as FreeTDM device 1:23 fd:47 2011-06-09 02:07:00.592486 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 25 as FreeTDM device 1:24 fd:48 2011-06-09 02:07:00.592510 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 26 as FreeTDM device 1:25 fd:49 2011-06-09 02:07:00.592531 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 27 as FreeTDM device 1:26 fd:50 2011-06-09 02:07:00.592558 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 28 as FreeTDM device 1:27 fd:51 2011-06-09 02:07:00.592584 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 29 as FreeTDM device 1:28 fd:52 2011-06-09 02:07:00.592609 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 30 as FreeTDM device 1:29 fd:53 2011-06-09 02:07:00.592628 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 31 as FreeTDM device 1:30 fd:54 2011-06-09 02:07:00.592654 [DEBUG] ftdm_io.c:4641 span 1 [d-channel]=[16] 2011-06-09 02:07:00.592692 [INFO] ftmod_zt.c:396 configuring device /dev/dahdi/channel channel 16 as FreeTDM device 1:31 fd:55 2011-06-09 02:07:00.592712 [INFO] ftdm_io.c:4823 Configured 31 channel(s) 2011-06-09 02:07:00.593269 [INFO] ftdm_io.c:4898 Loading IO from /usr/local/freeswitch/mod/ftmod_libpri.so [libpri] 2011-06-09 02:07:00.593283 [DEBUG] ftdm_io.c:4839 Module libpri does not support configuration. 2011-06-09 02:07:00.593287 [INFO] ftdm_io.c:4910 Loading SIG from /usr/local/freeswitch/mod/ftmod_libpri.so 2011-06-09 02:07:00.593292 [INFO] ftdm_io.c:5133 auto-loaded 'libpri' 2011-06-09 02:07:00.593302 [NOTICE] ftmod_libpri.c:1981 Setting default Layer 1 to ALAW since this is an E1/BRI/BRI PTMP trunk 2011-06-09 02:07:00.593566 [DEBUG] ftmod_libpri.c:1629 opening D-Channel #0 1:31 2011-06-09 02:07:00.596450 [NOTICE] switch_loadable_module.c:145 Adding Endpoint 'freetdm' 2011-06-09 02:07:00.596481 [NOTICE] switch_loadable_module.c:252 Adding Application 'disable_ec' 2011-06-09 02:07:00.596510 [NOTICE] switch_loadable_module.c:252 Adding Application 'disable_dtmf' 2011-06-09 02:07:00.596530 [NOTICE] switch_loadable_module.c:252 Adding Application 'enable_dtmf' 2011-06-09 02:07:00.596552 [NOTICE] switch_loadable_module.c:274 Adding API Function 'ftdm' 2011-06-09 02:07:00.618807 [DEBUG] ftmod_libpri.c:1586 -- Caught Event span 1 4 (CONFIG_ERR) 2011-06-09 02:07:00.622776 [NOTICE] switch_loadable_module.c:274 Adding API Function 'acl' ...later: 2011-06-09 02:07:01.693551 [DEBUG] ftmod_libpri.c:1586 -- Caught Event span 1 4 (CONFIG_ERR) 2011-06-09 02:07:02.773590 [DEBUG] ftmod_libpri.c:1586 -- Caught Event span 1 4 (CONFIG_ERR) 2011-06-09 02:07:03.833629 [DEBUG] ftmod_libpri.c:1586 -- Caught Event span 1 4 (CONFIG_ERR) 2011-06-09 02:07:04.893667 [DEBUG] ftmod_libpri.c:146 TEI=0 DL event: Q931_DL_EVENT_DL_RELEASE_IND(3) 2011-06-09 02:07:05.962709 [DEBUG] ftmod_libpri.c:1586 -- Caught Event span 1 4 (CONFIG_ERR) 2011-06-09 02:07:07.982780 [DEBUG] ftmod_libpri.c:1586 -- Caught Event span 1 4 (CONFIG_ERR) 2011-06-09 02:07:10.002854 [DEBUG] ftmod_libpri.c:1586 -- Caught Event span 1 4 (CONFIG_ERR) ... making a call: ... Dialplan: sofia/internal/1000(a)192.168.200.11 Action bridge(freetdm/e1group/1/12345) Dialplan: sofia/internal/1000(a)192.168.200.11 Action answer() 2011-06-09 02:10:27.343089 [DEBUG] mod_dptools.c:1063 sofia/internal/ 1000(a)192.168.200.11 SET [RFC2822_DATE]=[Thu, 09 Jun 2011 02:10:27 +0600] EXECUTE sofia/internal/1000(a)192.168.200.11 bridge(freetdm/e1group/1/12345) 2011-06-09 02:10:27.343089 [DEBUG] switch_ivr_originate.c:1869 Parsing global variables 2011-06-09 02:10:27.343089 [NOTICE] mod_freetdm.c:1551 Close Channel N/A [CS_NEW] 2011-06-09 02:10:27.343089 [DEBUG] switch_core_state_machine.c:457 () Running State Change CS_DESTROY 2011-06-09 02:10:27.343089 [DEBUG] switch_core_state_machine.c:467 (N/A) State DESTROY 2011-06-09 02:10:27.343089 [DEBUG] switch_core_state_machine.c:467 (N/A) State DESTROY going to sleep 2011-06-09 02:10:27.343089 [ERR] switch_ivr_originate.c:2443 Cannot create outgoing channel of type [freetdm] cause: [NORMAL_CIRCUIT_CONGESTION] 2011-06-09 02:10:27.343089 [DEBUG] switch_ivr_originate.c:3296 Originate Resulted in Error Cause: 34 [NORMAL_CIRCUIT_CONGESTION] Why? Which means error: Caught Event span 1 4 (CONFIG_ERR) Which config???

2 1

FreeTDM - destination_number empty on inbound call
by Christian Benke 09 Jun '11

09 Jun '11

Hi! My FS is connected to a plain BRI-line via a HFC-S PCI-card. On inbound calls i don't receive a dialed number. Please see the debug at http://pastebin.freeswitch.org/16456 for details. Do i have to fetch the DID from a variable before i can handle the call or is there some other problem, which i assume? Outbound calls work just fine btw. Best regards, Christian

3 4

originating a call from an outbound socket app
by Hector Geraldino 09 Jun '11

09 Jun '11

Hi all, I've been playing with FS around weeks, with some level of success. Right now I'm stuck trying to dial an extension, or to bridge a call to an external extension. Briefly, the scenario is the following: - Cisco CCM forwarding SIP calls to FS - FS in outbound mode, forwarding calls to a Java application using freeswitch-esl jar The java application answers the call, says a dialogue using TTS and receives input using DTFM or speech commands; all this is working pretty well. Now I'm trying to put this call in hold, originate a call to another extension and, depending on the result (call answered, not answered, destination user presses an specific number generating an expected DTMF), I need to bridge both calls and finish the session. I try several ways to get this done with no luck yet: using api originate to make the call with different arguments ({ignore_early_media, etc). I even tried to skip this step and just do the bridge between the inbound call and the external extension, but this didn't work either. I can't see any errors thrown by FS, and the result of the command is +OK, but nothing happens, the external phone never rings. The FS log only says: [DEBUG] switch_core_session.c:954 Send signal sofia/external/5655(a)192.168.8.1 [BREAK] <= this ext/IP address is from the inbound caller, not the one I'm trying to connect to. My first impression was that I might have something wrong with the originate/bridge parameters. I changed the dialplan XML file to just do the bridge, and it worked like a charm. <include> <extension name="test"> <condition field="destination_number" expression="6114|5121">  <action application="bridge" data="sofia/external/5562(a)192.168.2.14" /> </condition> </extension> </include> I don't know what path to follow here. I was unable to find relevant examples on google that guides me to solve this little issue. Can somebody please give me some advice? Thanks all, Hector

1 0

test
by Michal Bielicki 09 Jun '11

09 Jun '11

test Michal Bielicki Geschäftsführer / CEO Seventh Signal Ltd. & Co. KG Weigandufer 45, Büro 115, D-12059 Berlin Voice: +49 30 60988730 Amtsgericht Charlottenburg HRA 44413 B Ust.-ID: DE266981999 Geschäftsführer: Michal Bielicki Persönlich Haftende Gesellschafterin: Seventh Signal Ltd, 69 Great Hampton St. Birmingham, B18 6EW, GB, Company Nr.: 06889439 WWW.: http://www.seventhsignal.de

1 0

IP Whitelist
by Eric Beard 09 Jun '11

09 Jun '11

It seems I misunderstand the purpose of the acl.conf.xml file. What I want to do is create an IP whitelist, so only the IPs I designate get a response from FreeSwitch. I'd like to do this with FreeSwitch rather than a firewall. I have this in acl.conf.xml: <list name="domains" default="deny">  <node type="allow" domain="$${domain}"/>  <node type="allow" cidr="10.1.0.0/24"/>  <node type="allow" cidr="209.249.3.74/32"/> </list> I was assuming that this would only allow traffic from my local network, 10.1.0.0, and from the single IP 209.249.3.74 But while watching sip traffic, I saw an OPTIONS request from a different IP (sipvicious scan). Freeswitch happily responded to the OPTIONS with an OK. How can I configure it so that it ignores requests that are not on my whitelist? Thanks! ----------------------- Eric Z. Beard, CTO Loop LLC w (877) 850-2010 x9249 m (727) 776-2768 eric(a)loopfx.com<mailto:eric@loopfx.com>

3 5

Response status from client
by Alessandro 09 Jun '11

09 Jun '11

Hi, I have two questions about FS: Question 1: i'm developing a custom client sip with pjsip. This client when receive a call that can't be accepted respond with status 603. I think that freeswitch filter this status. This is an example of desired behaviour: 1000@localnet_ip FS(ip:localnet_ip) 1001@localnet_ip INVITE ----------> INVITE ---------------> <-------------- trying<--------------------trying <-------------- 603<------------------ 603 ACK ------------> ACK------------------> The current behaviour of FS is: 1000@localnet_ip FS(ip:localnet_ip) 1001@localnet_ip INVITE ----------> INVITE ---------------> <-------------- trying<--------------------trying <------------------ 603 <-------------- 200 ACK------------------> <--------------------BYE I'd like to avoid the current behaviour. It's possible a kind of message status path trough? If the called party terminate the call before answering, FS send always to the calling partner 200 and BYE. First thought was related to the voice-mail. Now voice-mail is disabled but the behaviour is the same. Question:2 It's possible a custom Header pass trough in status response like trying or session in progress? I'm able to use custom header only on invite adding to invite a header with name like X-myheader. Any suggestion? Thanks Good Evening Alessandro -- Ing. Alessandro Luppi Software development Seletech srl Via Collodi 8, 20052 Monza (MI) - Italy Tel: +39.039.5962000 - Fax: +39.039.9716905 email:a.luppi@seletech.com - Web:www.seletech.com orwww.seletech.eu

2 8

UUID_Bridge Fails But Reports +OK
by Antonio Teixeira 09 Jun '11

09 Jun '11

Hello List , Good Morning. In my fight to get ESL & Python & Freeswitch all to behave properly i noticed a possible BUG ( need the veterans to confirm). Scenario : Originate & ValetPark () + MOH OR Just Park() , Both show the same problem. Codec G729 I Make another call: originate & park() codec G729 Now Python ESL Inbound Or FS Console : uuid_bridge uuid1 uuid2 +OK uuid Now one of the two things happen : 1) One the call gets connected hurray :) , Audio Perfect , etc. 2) The call gets dropped :( In both cases uuid_bridge reports +OK even in the case the call is dropped. Even if i Park() Both Calls using the dialplan XML ( NO ESL with those SYN/ASYNC Problems) I still get sometimes ( not always) a dropped call could this be related to the use of G729 ? I have lots of available licenses. Regards António Teixeira

5 17

Problem with Cancel
by kawarod 09 Jun '11

09 Jun '11

Hi List, I have an issue with FS connected to a SIP gateway. When I receive a call from the SIP Gateway and try to hangup the call before he call is answered, so that a Cancel is emitted by the SIP GW, I have a SIP 481 Call Transaction does not exist. I understand that FS is unable to match this Cancel with the correct Invite, so that FS can not process the Cancel. Below is the SIP trace. It seems to me that the issue is because the Invite and the Cancel (generated by the same SIP GW) have different branch in the Via field. But I have no way to update the SIP GW and I absolutely need it for connection to the core network. May you please help to check if the issue could be related to the Via branch. It seems that they should be the same based on RFC. Do you have any idea to bypass this issue (any SIP profile magic trick :p). I made a "make current" this morning to check if this could help. U 10.69.208.204:5060 -> 10.69.208.200:5063 INVITE sip:770056@10.69.208.200:5063;user=phone SIP/2.0. Via: SIP/2.0/UDP 10.69.208.204:5060;branch=z9hG4bK-600-8524. To: <sip:770056@10.69.208.200:5063;user=phone>. From: <sip:265912@10.69.208.204:5060;user=phone>;tag=s24df07240-600-9408. Call-ID: 10.69.208.204:5060-4df07240-600-4680. Max-Forwards: 70. CSeq: 1 INVITE. Content-Length: 679. Remote-Party-Id: <sip:265912@10.69.208.204:5060;user=phone>;privacy=off;screen=yes. X-Fmc-Signaling-Info: location-pdu=83178679040000;location-pdu=689740000. Contact: <sip:265912@10.69.208.204:5060>. Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,REFER,PRACK,INFO,MESSAGE,SUBSCRIBE,NOTIFY,UPDATE. Content-Type: application/sdp. U 10.69.208.204:5060 -> 10.69.208.200:5063 CANCEL sip:770056@10.69.208.200:5063 SIP/2.0. Via: SIP/2.0/UDP 10.69.208.204:5060;branch=z9hG4bK-5800-392. To: <sip:770056@10.69.208.200:5063;user=phone>;tag=6XN6KF2N267cp. From: <sip:265912@10.69.208.204:5060;user=phone>;tag=s24df07240-600-9408. Call-ID: 10.69.208.204:5060-4df07240-600-4680. Max-Forwards: 70. CSeq: 1 CANCEL. Content-Length: 0. Reason: Q.850;cause=16;text="Normal call clearing". . U 10.69.208.200:5063 -> 10.69.208.204:5060 SIP/2.0 481 Call/Transaction Does Not Exist. Via: SIP/2.0/UDP 10.69.208.204:5060;branch=z9hG4bK-5800-392. From: <sip:265912@10.69.208.204:5060;user=phone>;tag=s24df07240-600-9408. To: <sip:770056@10.69.208.200:5063;user=phone>;tag=6XN6KF2N267cp. Call-ID: 10.69.208.204:5060-4df07240-600-4680. CSeq: 1 CANCEL. Content-Length: 0. regards, rod

1 0