Jump to content
Vodia PBX forum
voipguy

Record outgoing calls to emergency numbers

Recommended Posts

Record outgoing calls to emergency numbers - I don't think this feature is working or I can't find where it stores the recording.

 

PBXNSIP 4.2.0.3981 Linux centos 32 bit running on centos 5 64bit

 

Under Domain Settings we have Record outgoing calls to emergency numbers set to Yes, we also have the setting Emergency numbers: 911.

 

For the Account in question we have under the Redirection tab Record outgoing calls to emergency numbers set to default.

 

For the PBXNSIP system under Settings we have Record Location: $r/$o/$a/$d-$t-$i-$n-$u.wav

 

911 was called and the system knows this because it sent us an email stating "Account *blanked out* is calling the emergency number 911 at 2011/02/08 15:49:59" but we can't find where the recording is stored or it's not working.

 

Please let us know if this is a bug.

 

Thanks

Share this post


Link to post
Share on other sites

What type of license do you have? To my understanding recording has to be enable on the license thread. If is not activated in the license then recording will not work, Send me you license and I can decoded it for you or you can do it yourself here. http://www.opinionatedgeek.com/DotNet/Tools/Base64Decode/default.aspx

Share this post


Link to post
Share on other sites

What type of license do you have? To my understanding recording has to be enable on the license thread. If is not activated in the license then recording will not work, Send me you license and I can decoded it for you or you can do it yourself here. http://www.opinionatedgeek.com/DotNet/Tools/Base64Decode/default.aspx

 

We have the recording in our license.....we record all our calls - few hundred a day.

Share this post


Link to post
Share on other sites

Please set the log level to 8 & turn on everything but "Analyze audio levels" in the "Specific Events" on the logging page. No SIP logging is needed. Then we can check the log file to see if the call is being recorded. As you may already know, the recorded file should be under "recordings/<domain>/<account>" folder.

 

If you still do not see any log or recording, then try to set the "Record outgoing calls to emergency" field to "On", instead of default, just to see if there was any issue with the setting.

Share this post


Link to post
Share on other sites

Please set the log level to 8 & turn on everything but "Analyze audio levels" in the "Specific Events" on the logging page. No SIP logging is needed. Then we can check the log file to see if the call is being recorded. As you may already know, the recorded file should be under "recordings/<domain>/<account>" folder.

 

If you still do not see any log or recording, then try to set the "Record outgoing calls to emergency" field to "On", instead of default, just to see if there was any issue with the setting.

 

 

I turned on the logging and it's definitely not recording the 911 calls even when I set the users account to ON for "Record outgoing calls to emergency".

 

My log....

 

 

[8] 2011/02/09 21:20:05: Last message repeated 6 times

[8] 2011/02/09 21:20:05: Could not find a trunk (41 trunks)

[7] 2011/02/09 21:20:05: Set packet length to 20

[6] 2011/02/09 21:20:05: Sending RTP for 3c2af091d007-rh3p3vyggbhk to 192.168.1.25:56612, codec not set yet

[8] 2011/02/09 21:20:05: Call from an user 224

[8] 2011/02/09 21:20:05: To is <sip:911@mydomain.com;user=phone>, user 0, domain 2

[8] 2011/02/09 21:20:05: From user 224

[8] 2011/02/09 21:20:05: Set the To domain based on From user 224@mydomain.com

[8] 2011/02/09 21:20:05: Call state for call object 5166: idle

[7] 2011/02/09 21:20:05: set_codecs: for 3c2af091d007-rh3p3vyggbhk codecs "", codec_preference count 3

[5] 2011/02/09 21:20:05: Dialplan "mypbxnsiptrunk": Match 911@mydomain.com to <sip:the911number@myproxyip;user=phone> on trunk mypbxnsiptrunk

[8] 2011/02/09 21:20:05: DNS: Add AAAA smtp.myisp.ca (ttl=60)

[8] 2011/02/09 21:20:05: Play audio_moh/noise.wav

[7] 2011/02/09 21:20:05: set_codecs: for 5e6e8de4@pbx codecs "18 0", codec_preference count 3

[8] 2011/02/09 21:20:05: Answer challenge with username mypbxnsiptrunk

[7] 2011/02/09 21:20:05: Set packet length to 20

[6] 2011/02/09 21:20:05: Codec g729/8000 is chosen for call id 3c2af091d007-rh3p3vyggbhk

[8] 2011/02/09 21:20:05: SMTP: Connect to ipaddress:25

[8] 2011/02/09 21:20:05: SMTP: Received 220 ip03.myisp.ca ESMTP

 

[8] 2011/02/09 21:20:05: SMTP: Send EHLO localhost

 

[8] 2011/02/09 21:20:05: SMTP: Received 250-ip03.myisp.ca

250-8BITMIME

250 SIZE 31457280

 

[8] 2011/02/09 21:20:05: SMTP: Send MAIL FROM:<pbx@mymaildomain>

 

[8] 2011/02/09 21:20:05: SMTP: Received 250 sender <pbx@mymaildomain> ok

 

[8] 2011/02/09 21:20:05: SMTP: Send RCPT TO:<me@mydomain.com>

 

[8] 2011/02/09 21:20:05: SMTP: Received 250 recipient <me@mydomain.com> ok

 

[8] 2011/02/09 21:20:05: SMTP: Send DATA

 

[8] 2011/02/09 21:20:05: SMTP: Received 354 go ahead

 

[8] 2011/02/09 21:20:05: SMTP: Send From:pbx@mymaildomain

To:<me@mydomain.com>

Subject: =?UTF-8?Q?mycompanyname:_224_is_calling_911!?=

Date: Thu, 10 Feb 2011 01:20:05 -0000

MIME-Version: 1.0

Content-Type: text/plain

Content-Length: 89

 

 

[...]

[8] 2011/02/09 21:20:05: SMTP: Received 250 ok: Message 796407137 accepted

 

[8] 2011/02/09 21:20:05: SMTP: Send QUIT

 

[8] 2011/02/09 21:20:05: SMTP: Received 221 ip03.myisp.ca

 

[8] 2011/02/09 21:20:05: Sucessfully sent email to <me@mydomain.com>

[8] 2011/02/09 21:20:05: Packet authenticated by transport layer

[6] 2011/02/09 21:20:05: Sending RTP for 5e6e8de4@pbx to ipaddress:4690, codec not set yet

[7] 2011/02/09 21:20:05: Set packet length to 20

[6] 2011/02/09 21:20:05: Codec g729/8000 is chosen for call id 5e6e8de4@pbx

[8] 2011/02/09 21:20:05: Call state for call object 5166: alerting

[7] 2011/02/09 21:20:05: 3c2af091d007-rh3p3vyggbhk: RTP pass-through mode

[7] 2011/02/09 21:20:05: 5e6e8de4@pbx: RTP pass-through mode

[8] 2011/02/09 21:20:05: SRTP MAC mismatch: 4238c45d != 00000000

[7] 2011/02/09 21:20:05: Discard SRTCP packet from ipaddress:57830 with wrong MAC

[6] 2011/02/09 21:20:05: Sending RTP for 3c2af091d007-rh3p3vyggbhk to ipaddress.45:57831, codec g729/8000

[8] 2011/02/09 21:20:06: Packet authenticated by transport layer

[8] 2011/02/09 21:20:14: Last message repeated 7 times

[7] 2011/02/09 21:20:14: Call 5e6e8de4@pbx: Clear last INVITE

[7] 2011/02/09 21:20:14: Set packet length to 20

[7] 2011/02/09 21:20:14: Determine pass-through mode after receiving response

[8] 2011/02/09 21:20:14: Call state for call object 5166: connected

[8] 2011/02/09 21:20:15: Packet authenticated by transport layer

[8] 2011/02/09 21:20:23: Last message repeated 4 times

[8] 2011/02/09 21:20:23: Trunk 32 (507114) is associated with the following addresses: udp:myproxyip:5060

[8] 2011/02/09 21:20:26: Packet authenticated by transport layer

[8] 2011/02/09 21:20:30: Last message repeated 3 times

[7] 2011/02/09 21:20:30: 5e6e8de4@pbx: Media-aware pass-through mode

[8] 2011/02/09 21:20:30: Hangup: Call 80 not found

[8] 2011/02/09 21:20:30: Last message repeated 2 times

[7] 2011/02/09 21:20:30: Call 5e6e8de4@pbx: Clear last request

[5] 2011/02/09 21:20:30: BYE Response: Terminate 5e6e8de4@pbx

[8] 2011/02/09 21:20:30: Packet authenticated by transport layer

[8] 2011/02/09 21:20:31: Trunk 39 (507183) is associated with the following addresses: udp:myproxyip:5060

[8] 2011/02/09 21:20:31: Trunk 46 (506040) is associated with the following addresses: udp:myproxyip:5060

[8] 2011/02/09 21:20:31: Trunk 48 (502156) is associated with the following addresses: udp:myproxyip:5060

[8] 2011/02/09 21:20:31: Trunk 50 (507227) is associated with the following addresses: udp:myproxyip:5060

[8] 2011/02/09 21:20:31: Trunk 41 (507218) is associated with the following addresses: udp:myproxyip:5060

[8] 2011/02/09 21:20:31: Trunk 49 (507244) is associated with the following addresses: udp:myproxyip:5060

[8] 2011/02/09 21:20:31: Trunk 47 (506710) is associated with the following addresses: udp:myproxyip:5060

[8] 2011/02/09 21:20:32: Packet authenticated by transport layer

 

 

I did about 5 tests and checked the recording directory and the call was not recorded.

 

I think this is a bug.

Share this post


Link to post
Share on other sites

I did not see the log line showing the call is bing recorded. We will retest it and see if there is any issue in that area.

 

 

Can you confirm this will be fixed soon?

 

Thanks

Share this post


Link to post
Share on other sites

It was a bug and next release will have the fix for it. Forgot to update the post. Thanks for the 'bump'

 

I can confirm this has been fixed in ver 4.2.1.4001

 

Thanks

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...