Sending and Receiving faxes - freeswitch
Hello Everyone, I am trying to send and receive faxes. I have assigned the number 4302050 for receiving faxes, and the use configuration is given below: <include> <user id="1050"> <params> <param name="password" value="$${default_password}"/> <param name="vm-password" value="1050"/> </params> <variables> <variable name="toll_allow" value="domestic,international,local"/> <variable name="accountcode" value="1050"/> <variable name="user_context" value="default"/> <variable name="effective_caller_id_name" value="Extension 1050"/> <variable name="effective_caller_id_number" value="1050"/> <variable name="outbound_caller_id_name" value="$${outbound_caller_name}"/> <variable name="outbound_caller_id_number" value="$${outbound_caller_id}"/> <variable name="callgroup" value="techsupport"/> </variables> </user> </include> The dial plan that I have in place to receive faxes is given below: <extension name="fax_receive"> <condition field="destination_number" expression="^(050$)"> <action application="set" data="ignore_early_media=true"/> <action application="answer" /> <action application="playback" data="silence_stream://2000"/> <action application="rxfax" data="$${base_dir}/faxes/${caller_id_number}.tif"/> <action application="hangup"/> </condition> </extension> When this fax number is called from another telephone, I hear the fax dialtone. But when the fax number is called from any fax machine and try to send a fax, it gives a number not available message. I do not recieve this call in the freeswitch server as well. Would really appreciate if anyone could help me in this, to let me know if I am missing something. Thanks in advance. Ravi
How exactly is this number routed to you and via what provider? Have you verified firewall and nat setting to make sure you actually receiving the INVITE? On Sep 8, 2013, at 12:53 PM, Ravi <sravi123@yahoo.com> wrote:
When this fax number is called from another telephone, I hear the fax dialtone. But when the fax number is called from any fax machine and try to send a fax, it gives a number not available message. I do not recieve this call in the freeswitch server as well.
-- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH_Wire , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED)
Brian, Firstly, many congratulations on your wedding ! My best wishes !! Secondly, I am trying to learn Freeswitch and I have made considerable progress, with help from the mailing list :) The configuration that I have is a PRI line, and a Sangoma A101DE card, with Cent OS. I am based out of India and the service provider is called Bharti Airtel. I have setup the system so it works and I can make and receive calls through Freeswitch. The firewall in the machine that runs the freeswitch server is disabled. As far as NAT settings, this is the log that I have when Freeswitch server is started. 2013-09-11 21:55:30.737518 [INFO] switch_nat.c:420 Scanning for NAT 2013-09-11 21:55:30.737699 [DEBUG] switch_nat.c:170 Checking for PMP 1/5 2013-09-11 21:55:30.738500 [ERR] switch_nat.c:201 Error checking for PMP [general error] 2013-09-11 21:55:30.738513 [DEBUG] switch_nat.c:425 Checking for UPnP 2013-09-11 21:55:34.339478 [INFO] switch_nat.c:434 NAT detected type: upnp, ExtIP: '123.236.215.39' 2013-09-11 21:55:34.340174 [DEBUG] switch_nat.c:264 NAT thread configured 2013-09-11 21:55:34.340501 [DEBUG] switch_nat.c:275 NAT thread started The log when I call the fax number (4302050) from a landline is included in pastebin with link given below: http://pastebin.freeswitch.org/21396 I hope I have answered your questions. I am not sure if you mean that the number 4302050 receives the call, by the term INVITE. Please let me know what I am missing in this, or if any additional information is required. Many Thanks ! Ravi ________________________________ From: Brian West <brian@freeswitch.org> To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Sent: Sunday, September 8, 2013 11:30 PM Subject: Re: [Freeswitch-users] Sending and Receiving faxes - freeswitch How exactly is this number routed to you and via what provider? Have you verified firewall and nat setting to make sure you actually receiving the INVITE? On Sep 8, 2013, at 12:53 PM, Ravi <sravi123@yahoo.com> wrote:
When this fax number is called from another telephone, I hear the fax dialtone. But when the fax number is called from any fax machine and try to send a fax, it gives a number not available message. I do not recieve this call in the freeswitch server as well.
-- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH_Wire , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED) _________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Hello Everyone ! I hope, this time some one could help me resolve setting up faxes through Freeswitch. I need some help with setting up faxes. Can anyone in this mailing list offer some help to fix this ? Thanks. Ravi On 11/09/13 10:08 PM, Ravi wrote:
Brian,
Firstly, many congratulations on your wedding ! My best wishes !!
Secondly, I am trying to learn Freeswitch and I have made considerable progress, with help from the mailing list :)
The configuration that I have is a PRI line, and a Sangoma A101DE card, with Cent OS. I am based out of India and the service provider is called Bharti Airtel. I have setup the system so it works and I can make and receive calls through Freeswitch.
The firewall in the machine that runs the freeswitch server is disabled. As far as NAT settings, this is the log that I have when Freeswitch server is started.
2013-09-11 21:55:30.737518 [INFO] switch_nat.c:420 Scanning for NAT 2013-09-11 21:55:30.737699 [DEBUG] switch_nat.c:170 Checking for PMP 1/5 2013-09-11 21:55:30.738500 [ERR] switch_nat.c:201 Error checking for PMP [general error] 2013-09-11 21:55:30.738513 [DEBUG] switch_nat.c:425 Checking for UPnP 2013-09-11 21:55:34.339478 [INFO] switch_nat.c:434 NAT detected type: upnp, ExtIP: '123.236.215.39' 2013-09-11 21:55:34.340174 [DEBUG] switch_nat.c:264 NAT thread configured 2013-09-11 21:55:34.340501 [DEBUG] switch_nat.c:275 NAT thread started
The log when I call the fax number (4302050) from a landline is included in pastebin with link given below:
http://pastebin.freeswitch.org/21396
I hope I have answered your questions. I am not sure if you mean that the number 4302050 receives the call, by the term INVITE. Please let me know what I am missing in this, or if any additional information is required.
Many Thanks ! Ravi
------------------------------------------------------------------------ *From:* Brian West <brian@freeswitch.org> *To:* FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> *Sent:* Sunday, September 8, 2013 11:30 PM *Subject:* Re: [Freeswitch-users] Sending and Receiving faxes - freeswitch
How exactly is this number routed to you and via what provider? Have you verified firewall and nat setting to make sure you actually receiving the INVITE?
On Sep 8, 2013, at 12:53 PM, Ravi <sravi123@yahoo.com <mailto:sravi123@yahoo.com>> wrote:
When this fax number is called from another telephone, I hear the fax dialtone. But when the fax number is called from any fax machine and try to send a fax, it gives a number not available message. I do not recieve this call in the freeswitch server as well.
-- Brian West brian@freeswitch.org <mailto:brian@freeswitch.org> FreeSWITCH Solutions, LLC PO BOX PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH_Wire , @briankwest http://www.freeswitchbook.com <http://www.freeswitchbook.com/> http://www.freeswitchcookbook.com <http://www.freeswitchcookbook.com/>
T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED)
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org <mailto:consulting@freeswitch.org> http://www.freeswitchsolutions.com <http://www.freeswitchsolutions.com/>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com <http://www.cudatel.com/>
Official FreeSWITCH Sites http://www.freeswitch.org <http://www.freeswitch.org/> http://wiki.freeswitch.org <http://wiki.freeswitch.org/> http://www.cluecon.com <http://www.cluecon.com/>
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org <mailto:FreeSWITCH-users@lists.freeswitch.org> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org <http://www.freeswitch.org/>
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Hi, I am seeing periodic RTP Wrong Timestamps and audio hiccups when using conferencing. I am calling in from two phones on the local LAN, and playing a 440-Hz tone into the conference on one of the phones. On the receiving phone, I hear an audio hiccup (and the server-side Wireshark trace shows a Wrong Timestamp) about once every 750 ms. It is very regular on the output from the conference. The server-side Wireshark of the input RTP stream looks fine -- there are no anomalies. I am seeing this problem on version 1.2.10 and 1.5.5b. Is this something I need to report as a bug? Thanks, David
in what way is the timestamp "wrong"? On Sep 24, 2013, at 3:30 PM, D D <tru083@yahoo.com> wrote:
Hi,
I am seeing periodic RTP Wrong Timestamps and audio hiccups when using conferencing.
I am calling in from two phones on the local LAN, and playing a 440-Hz tone into the conference on one of the phones.
On the receiving phone, I hear an audio hiccup (and the server-side Wireshark trace shows a Wrong Timestamp) about once every 750 ms. It is very regular on the output from the conference.
The server-side Wireshark of the input RTP stream looks fine -- there are no anomalies.
I am seeing this problem on version 1.2.10 and 1.5.5b.
Is this something I need to report as a bug?
Thanks, David
They are flagged as wrong by Wireshark, in the VoIP RTP Player. Unfortunately, Wireshark does not allow me to get from the 'W' in player back to the packets it thinks are wrong in the detailed view. ________________________________ From: Michael Jerris <mike@jerris.com> To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Sent: Tuesday, September 24, 2013 2:49 PM Subject: Re: [Freeswitch-users] RTP Wrong Timestamps and audio hiccups in conferencing output in what way is the timestamp "wrong"? On Sep 24, 2013, at 3:30 PM, D D <tru083@yahoo.com> wrote: Hi,
I am seeing periodic RTP Wrong Timestamps and audio hiccups when using conferencing.
I am calling in from two phones on the local LAN, and playing a 440-Hz tone into the conference on one of the phones.
On the receiving phone, I hear an audio hiccup (and the server-side Wireshark trace shows a Wrong Timestamp) about once every 750 ms. It is very regular on the output from the conference.
The server-side Wireshark of the input RTP stream looks fine -- there are no anomalies.
I am seeing this problem on version 1.2.10 and 1.5.5b.
Is this something I need to report as a bug?
Thanks, David
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Try looking at the time into the call to find the right packets. Without seeing what exactly is wrong, we are not going to be able to guess what might be going on. On Sep 24, 2013, at 1:29 PM, D D <tru083@yahoo.com> wrote:
They are flagged as wrong by Wireshark, in the VoIP RTP Player.
Unfortunately, Wireshark does not allow me to get from the 'W' in player back to the packets it thinks are wrong in the detailed view.
From: Michael Jerris <mike@jerris.com> To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Sent: Tuesday, September 24, 2013 2:49 PM Subject: Re: [Freeswitch-users] RTP Wrong Timestamps and audio hiccups in conferencing output
in what way is the timestamp "wrong"?
On Sep 24, 2013, at 3:30 PM, D D <tru083@yahoo.com> wrote:
Hi,
I am seeing periodic RTP Wrong Timestamps and audio hiccups when using conferencing.
I am calling in from two phones on the local LAN, and playing a 440-Hz tone into the conference on one of the phones.
On the receiving phone, I hear an audio hiccup (and the server-side Wireshark trace shows a Wrong Timestamp) about once every 750 ms. It is very regular on the output from the conference.
The server-side Wireshark of the input RTP stream looks fine -- there are no anomalies.
I am seeing this problem on version 1.2.10 and 1.5.5b.
Is this something I need to report as a bug?
Thanks, David
As mentioned by Michael, without seeing the wireshark dumps it will be difficult to diagnose what is happening (however even if you upload the dump, it will require someone to take time out to review and analyse). Best thing to do is analyse the wireshark and try everything you can think of to diagnose/debug the problem, then upload the logs+wireshark along with a full debrief of what you have tried so far. This will greatly increase the chance of others taking time out to help you with this. Cal On Wed, Sep 25, 2013 at 10:45 PM, Michael Jerris <mike@jerris.com> wrote:
Try looking at the time into the call to find the right packets. Without seeing what exactly is wrong, we are not going to be able to guess what might be going on.
On Sep 24, 2013, at 1:29 PM, D D <tru083@yahoo.com> wrote:
They are flagged as wrong by Wireshark, in the VoIP RTP Player.
Unfortunately, Wireshark does not allow me to get from the 'W' in player back to the packets it thinks are wrong in the detailed view.
------------------------------ *From:* Michael Jerris <mike@jerris.com> *To:* FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> *Sent:* Tuesday, September 24, 2013 2:49 PM *Subject:* Re: [Freeswitch-users] RTP Wrong Timestamps and audio hiccups in conferencing output
in what way is the timestamp "wrong"?
On Sep 24, 2013, at 3:30 PM, D D <tru083@yahoo.com> wrote:
Hi,
I am seeing periodic RTP Wrong Timestamps and audio hiccups when using conferencing.
I am calling in from two phones on the local LAN, and playing a 440-Hz tone into the conference on one of the phones.
On the receiving phone, I hear an audio hiccup (and the server-side Wireshark trace shows a Wrong Timestamp) about once every 750 ms. It is very regular on the output from the conference.
The server-side Wireshark of the input RTP stream looks fine -- there are no anomalies.
I am seeing this problem on version 1.2.10 and 1.5.5b.
Is this something I need to report as a bug?
Thanks, David
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Hi, I have an example of a wrong timestamp below. It begins in packet 3563. What do you think? Thanks, David No. Time Source src port Destination dst port Protocol Info New Column 3505 13:39:29.130487 10.1.1.226 22776 10.1.1.1 18384 RTP PT=ITU-T G.711 PCMU, SSRC=0x7D5DC9C, Seq=16396, Time=32000 214 Frame 3505: 214 bytes on wire (1712 bits), 214 bytes captured (1712 bits) WTAP_ENCAP: 1 Arrival Time: Sep 24, 2013 13:39:29.130487000 CDT [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1380047969.130487000 seconds [Time delta from previous captured frame: 0.002441000 seconds] [Time delta from previous displayed frame: 0.020005000 seconds] [Time since reference or first frame: 30.185993000 seconds] Frame Number: 3505 Frame Length: 214 bytes (1712 bits) Capture Length: 214 bytes (1712 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ip:udp:rtp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Src: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a), Dst: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Destination: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Address: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Source: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) Address: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Type: IP (0x0800) Internet Protocol Version 4, Src: 10.1.1.226 (10.1.1.226), Dst: 10.1.1.1 (10.1.1.1) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport)) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..00 = Explicit Congestion Notification: Not-ECT (Not ECN-Capable Transport) (0x00) Total Length: 200 Identification: 0x0000 (0) Flags: 0x02 (Don't Fragment) 0... .... = Reserved bit: Not set .1.. .... = Don't fragment: Set ..0. .... = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (17) Header checksum: 0x2341 [correct] [Good: True] [Bad: False] Source: 10.1.1.226 (10.1.1.226) Destination: 10.1.1.1 (10.1.1.1) User Datagram Protocol, Src Port: 22776 (22776), Dst Port: 18384 (18384) Source port: 22776 (22776) Destination port: 18384 (18384) Length: 180 Checksum: 0x17aa [validation disabled] [Good Checksum: False] [Bad Checksum: False] Real-Time Transport Protocol [Stream setup by SDP (frame 2754)] [Setup frame: 2754] [Setup Method: SDP] 10.. .... = Version: RFC 1889 Version (2) ..0. .... = Padding: False ...0 .... = Extension: False .... 0000 = Contributing source identifiers count: 0 0... .... = Marker: False Payload type: ITU-T G.711 PCMU (0) Sequence number: 16396 [Extended sequence number: 81932] Timestamp: 32000 Synchronization Source identifier: 0x07d5dc9c (131456156) Payload: ffeeebf2776c6c79f0ebee7d6d6b74f5ebedfb6f6b6ffbed... No. Time Source src port Destination dst port Protocol Info New Column 3509 13:39:29.150492 10.1.1.226 22776 10.1.1.1 18384 RTP PT=ITU-T G.711 PCMU, SSRC=0x7D5DC9C, Seq=16397, Time=32160 214 Frame 3509: 214 bytes on wire (1712 bits), 214 bytes captured (1712 bits) WTAP_ENCAP: 1 Arrival Time: Sep 24, 2013 13:39:29.150492000 CDT [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1380047969.150492000 seconds [Time delta from previous captured frame: 0.002365000 seconds] [Time delta from previous displayed frame: 0.020005000 seconds] [Time since reference or first frame: 30.205998000 seconds] Frame Number: 3509 Frame Length: 214 bytes (1712 bits) Capture Length: 214 bytes (1712 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ip:udp:rtp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Src: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a), Dst: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Destination: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Address: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Source: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) Address: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Type: IP (0x0800) Internet Protocol Version 4, Src: 10.1.1.226 (10.1.1.226), Dst: 10.1.1.1 (10.1.1.1) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport)) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..00 = Explicit Congestion Notification: Not-ECT (Not ECN-Capable Transport) (0x00) Total Length: 200 Identification: 0x0000 (0) Flags: 0x02 (Don't Fragment) 0... .... = Reserved bit: Not set .1.. .... = Don't fragment: Set ..0. .... = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (17) Header checksum: 0x2341 [correct] [Good: True] [Bad: False] Source: 10.1.1.226 (10.1.1.226) Destination: 10.1.1.1 (10.1.1.1) User Datagram Protocol, Src Port: 22776 (22776), Dst Port: 18384 (18384) Source port: 22776 (22776) Destination port: 18384 (18384) Length: 180 Checksum: 0x17aa [validation disabled] [Good Checksum: False] [Bad Checksum: False] Real-Time Transport Protocol [Stream setup by SDP (frame 2754)] [Setup frame: 2754] [Setup Method: SDP] 10.. .... = Version: RFC 1889 Version (2) ..0. .... = Padding: False ...0 .... = Extension: False .... 0000 = Contributing source identifiers count: 0 0... .... = Marker: False Payload type: ITU-T G.711 PCMU (0) Sequence number: 16397 [Extended sequence number: 81933] Timestamp: 32160 Synchronization Source identifier: 0x07d5dc9c (131456156) Payload: fff0edf4796e6e7af3edf17d6f6e76f7eeeffc726d72fcef... No. Time Source src port Destination dst port Protocol Info New Column 3513 13:39:29.170502 10.1.1.226 22776 10.1.1.1 18384 RTP PT=ITU-T G.711 PCMU, SSRC=0x7D5DC9C, Seq=16398, Time=32320 214 Frame 3513: 214 bytes on wire (1712 bits), 214 bytes captured (1712 bits) WTAP_ENCAP: 1 Arrival Time: Sep 24, 2013 13:39:29.170502000 CDT [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1380047969.170502000 seconds [Time delta from previous captured frame: 0.002428000 seconds] [Time delta from previous displayed frame: 0.020010000 seconds] [Time since reference or first frame: 30.226008000 seconds] Frame Number: 3513 Frame Length: 214 bytes (1712 bits) Capture Length: 214 bytes (1712 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ip:udp:rtp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Src: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a), Dst: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Destination: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Address: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Source: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) Address: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Type: IP (0x0800) Internet Protocol Version 4, Src: 10.1.1.226 (10.1.1.226), Dst: 10.1.1.1 (10.1.1.1) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport)) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..00 = Explicit Congestion Notification: Not-ECT (Not ECN-Capable Transport) (0x00) Total Length: 200 Identification: 0x0000 (0) Flags: 0x02 (Don't Fragment) 0... .... = Reserved bit: Not set .1.. .... = Don't fragment: Set ..0. .... = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (17) Header checksum: 0x2341 [correct] [Good: True] [Bad: False] Source: 10.1.1.226 (10.1.1.226) Destination: 10.1.1.1 (10.1.1.1) User Datagram Protocol, Src Port: 22776 (22776), Dst Port: 18384 (18384) Source port: 22776 (22776) Destination port: 18384 (18384) Length: 180 Checksum: 0x17aa [validation disabled] [Good Checksum: False] [Bad Checksum: False] Real-Time Transport Protocol [Stream setup by SDP (frame 2754)] [Setup frame: 2754] [Setup Method: SDP] 10.. .... = Version: RFC 1889 Version (2) ..0. .... = Padding: False ...0 .... = Extension: False .... 0000 = Contributing source identifiers count: 0 0... .... = Marker: False Payload type: ITU-T G.711 PCMU (0) Sequence number: 16398 [Extended sequence number: 81934] Timestamp: 32320 Synchronization Source identifier: 0x07d5dc9c (131456156) Payload: fff3eff77a71717bf6eff47e727078f9f0f2fd757075fdf2... No. Time Source src port Destination dst port Protocol Info New Column 3563 13:39:29.490508 10.1.1.226 22776 10.1.1.1 18384 RTP PT=ITU-T G.711 PCMU, SSRC=0x7D5DC9C, Seq=16399, Time=480, Mark 214 Frame 3563: 214 bytes on wire (1712 bits), 214 bytes captured (1712 bits) WTAP_ENCAP: 1 Arrival Time: Sep 24, 2013 13:39:29.490508000 CDT [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1380047969.490508000 seconds [Time delta from previous captured frame: 0.002419000 seconds] [Time delta from previous displayed frame: 0.320006000 seconds] [Time since reference or first frame: 30.546014000 seconds] Frame Number: 3563 Frame Length: 214 bytes (1712 bits) Capture Length: 214 bytes (1712 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ip:udp:rtp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Src: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a), Dst: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Destination: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Address: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Source: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) Address: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Type: IP (0x0800) Internet Protocol Version 4, Src: 10.1.1.226 (10.1.1.226), Dst: 10.1.1.1 (10.1.1.1) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport)) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..00 = Explicit Congestion Notification: Not-ECT (Not ECN-Capable Transport) (0x00) Total Length: 200 Identification: 0x0000 (0) Flags: 0x02 (Don't Fragment) 0... .... = Reserved bit: Not set .1.. .... = Don't fragment: Set ..0. .... = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (17) Header checksum: 0x2341 [correct] [Good: True] [Bad: False] Source: 10.1.1.226 (10.1.1.226) Destination: 10.1.1.1 (10.1.1.1) User Datagram Protocol, Src Port: 22776 (22776), Dst Port: 18384 (18384) Source port: 22776 (22776) Destination port: 18384 (18384) Length: 180 Checksum: 0x17aa [validation disabled] [Good Checksum: False] [Bad Checksum: False] Real-Time Transport Protocol [Stream setup by SDP (frame 2754)] [Setup frame: 2754] [Setup Method: SDP] 10.. .... = Version: RFC 1889 Version (2) ..0. .... = Padding: False ...0 .... = Extension: False .... 0000 = Contributing source identifiers count: 0 1... .... = Marker: True Payload type: ITU-T G.711 PCMU (0) Sequence number: 16399 [Extended sequence number: 81935] Timestamp: 480 Synchronization Source identifier: 0x07d5dc9c (131456156) Payload: 4f3e352d2b2f42f9dbd2c0b6adaaaec076595241372e2b2e... No. Time Source src port Destination dst port Protocol Info New Column 3567 13:39:29.510447 10.1.1.226 22776 10.1.1.1 18384 RTP PT=ITU-T G.711 PCMU, SSRC=0x7D5DC9C, Seq=16400, Time=640 214 Frame 3567: 214 bytes on wire (1712 bits), 214 bytes captured (1712 bits) WTAP_ENCAP: 1 Arrival Time: Sep 24, 2013 13:39:29.510447000 CDT [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1380047969.510447000 seconds [Time delta from previous captured frame: 0.002292000 seconds] [Time delta from previous displayed frame: 0.019939000 seconds] [Time since reference or first frame: 30.565953000 seconds] Frame Number: 3567 Frame Length: 214 bytes (1712 bits) Capture Length: 214 bytes (1712 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ip:udp:rtp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Src: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a), Dst: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Destination: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Address: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Source: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) Address: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Type: IP (0x0800) Internet Protocol Version 4, Src: 10.1.1.226 (10.1.1.226), Dst: 10.1.1.1 (10.1.1.1) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport)) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..00 = Explicit Congestion Notification: Not-ECT (Not ECN-Capable Transport) (0x00) Total Length: 200 Identification: 0x0000 (0) Flags: 0x02 (Don't Fragment) 0... .... = Reserved bit: Not set .1.. .... = Don't fragment: Set ..0. .... = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (17) Header checksum: 0x2341 [correct] [Good: True] [Bad: False] Source: 10.1.1.226 (10.1.1.226) Destination: 10.1.1.1 (10.1.1.1) User Datagram Protocol, Src Port: 22776 (22776), Dst Port: 18384 (18384) Source port: 22776 (22776) Destination port: 18384 (18384) Length: 180 Checksum: 0x17aa [validation disabled] [Good Checksum: False] [Bad Checksum: False] Real-Time Transport Protocol [Stream setup by SDP (frame 2754)] [Setup frame: 2754] [Setup Method: SDP] 10.. .... = Version: RFC 1889 Version (2) ..0. .... = Padding: False ...0 .... = Extension: False .... 0000 = Contributing source identifiers count: 0 0... .... = Marker: False Payload type: ITU-T G.711 PCMU (0) Sequence number: 16400 [Extended sequence number: 81936] Timestamp: 640 Synchronization Source identifier: 0x07d5dc9c (131456156) Payload: b6d65c58493b312c2c354fe2daccbcb2abaab3cd5f584c3d... ________________________________ From: Michael Jerris <mike@jerris.com> To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Sent: Wednesday, September 25, 2013 4:45 PM Subject: Re: [Freeswitch-users] RTP Wrong Timestamps and audio hiccups in conferencing output Try looking at the time into the call to find the right packets. Without seeing what exactly is wrong, we are not going to be able to guess what might be going on. On Sep 24, 2013, at 1:29 PM, D D <tru083@yahoo.com> wrote: They are flagged as wrong by Wireshark, in the VoIP RTP Player.
Unfortunately, Wireshark does not allow me to get from the 'W' in player back to the packets it thinks are wrong in the detailed view.
________________________________ From: Michael Jerris <mike@jerris.com> To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Sent: Tuesday, September 24, 2013 2:49 PM Subject: Re: [Freeswitch-users] RTP Wrong Timestamps and audio hiccups in conferencing output
in what way is the timestamp "wrong"?
On Sep 24, 2013, at 3:30 PM, D D <tru083@yahoo.com> wrote:
Hi,
I am seeing periodic RTP Wrong Timestamps and audio hiccups when using conferencing.
I am calling in from two phones on the local LAN, and playing a 440-Hz tone into the conference on one of the phones.
On the receiving phone, I hear an audio hiccup (and the server-side Wireshark trace shows a Wrong Timestamp) about once every 750 ms. It is very regular on the output from the conference.
The server-side Wireshark of the input RTP stream looks fine -- there are no anomalies.
I am seeing this problem on version 1.2.10 and 1.5.5b.
Is this something I need to report as a bug?
Thanks, David
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
This looks like its a timestamp rollover maybe.. in other places this happens, whats the timestamp before and after? in this case, before: 32320, after: 480 (marker bit set). Mike On Sep 26, 2013, at 4:52 PM, D D <tru083@yahoo.com> wrote:
Hi,
I have an example of a wrong timestamp below. It begins in packet 3563. What do you think?
Thanks, David
No. Time Source src port Destination dst port Protocol Info New Column 3505 13:39:29.130487 10.1.1.226 22776 10.1.1.1 18384 RTP PT=ITU-T G.711 PCMU, SSRC=0x7D5DC9C, Seq=16396, Time=32000 214
Frame 3505: 214 bytes on wire (1712 bits), 214 bytes captured (1712 bits) WTAP_ENCAP: 1 Arrival Time: Sep 24, 2013 13:39:29.130487000 CDT [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1380047969.130487000 seconds [Time delta from previous captured frame: 0.002441000 seconds] [Time delta from previous displayed frame: 0.020005000 seconds] [Time since reference or first frame: 30.185993000 seconds] Frame Number: 3505 Frame Length: 214 bytes (1712 bits) Capture Length: 214 bytes (1712 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ip:udp:rtp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Src: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a), Dst: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Destination: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Address: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Source: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) Address: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Type: IP (0x0800) Internet Protocol Version 4, Src: 10.1.1.226 (10.1.1.226), Dst: 10.1.1.1 (10.1.1.1) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport)) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..00 = Explicit Congestion Notification: Not-ECT (Not ECN-Capable Transport) (0x00) Total Length: 200 Identification: 0x0000 (0) Flags: 0x02 (Don't Fragment) 0... .... = Reserved bit: Not set .1.. .... = Don't fragment: Set ..0. .... = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (17) Header checksum: 0x2341 [correct] [Good: True] [Bad: False] Source: 10.1.1.226 (10.1.1.226) Destination: 10.1.1.1 (10.1.1.1) User Datagram Protocol, Src Port: 22776 (22776), Dst Port: 18384 (18384) Source port: 22776 (22776) Destination port: 18384 (18384) Length: 180 Checksum: 0x17aa [validation disabled] [Good Checksum: False] [Bad Checksum: False] Real-Time Transport Protocol [Stream setup by SDP (frame 2754)] [Setup frame: 2754] [Setup Method: SDP] 10.. .... = Version: RFC 1889 Version (2) ..0. .... = Padding: False ...0 .... = Extension: False .... 0000 = Contributing source identifiers count: 0 0... .... = Marker: False Payload type: ITU-T G.711 PCMU (0) Sequence number: 16396 [Extended sequence number: 81932] Timestamp: 32000 Synchronization Source identifier: 0x07d5dc9c (131456156) Payload: ffeeebf2776c6c79f0ebee7d6d6b74f5ebedfb6f6b6ffbed...
No. Time Source src port Destination dst port Protocol Info New Column 3509 13:39:29.150492 10.1.1.226 22776 10.1.1.1 18384 RTP PT=ITU-T G.711 PCMU, SSRC=0x7D5DC9C, Seq=16397, Time=32160 214
Frame 3509: 214 bytes on wire (1712 bits), 214 bytes captured (1712 bits) WTAP_ENCAP: 1 Arrival Time: Sep 24, 2013 13:39:29.150492000 CDT [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1380047969.150492000 seconds [Time delta from previous captured frame: 0.002365000 seconds] [Time delta from previous displayed frame: 0.020005000 seconds] [Time since reference or first frame: 30.205998000 seconds] Frame Number: 3509 Frame Length: 214 bytes (1712 bits) Capture Length: 214 bytes (1712 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ip:udp:rtp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Src: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a), Dst: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Destination: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Address: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Source: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) Address: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Type: IP (0x0800) Internet Protocol Version 4, Src: 10.1.1.226 (10.1.1.226), Dst: 10.1.1.1 (10.1.1.1) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport)) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..00 = Explicit Congestion Notification: Not-ECT (Not ECN-Capable Transport) (0x00) Total Length: 200 Identification: 0x0000 (0) Flags: 0x02 (Don't Fragment) 0... .... = Reserved bit: Not set .1.. .... = Don't fragment: Set ..0. .... = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (17) Header checksum: 0x2341 [correct] [Good: True] [Bad: False] Source: 10.1.1.226 (10.1.1.226) Destination: 10.1.1.1 (10.1.1.1) User Datagram Protocol, Src Port: 22776 (22776), Dst Port: 18384 (18384) Source port: 22776 (22776) Destination port: 18384 (18384) Length: 180 Checksum: 0x17aa [validation disabled] [Good Checksum: False] [Bad Checksum: False] Real-Time Transport Protocol [Stream setup by SDP (frame 2754)] [Setup frame: 2754] [Setup Method: SDP] 10.. .... = Version: RFC 1889 Version (2) ..0. .... = Padding: False ...0 .... = Extension: False .... 0000 = Contributing source identifiers count: 0 0... .... = Marker: False Payload type: ITU-T G.711 PCMU (0) Sequence number: 16397 [Extended sequence number: 81933] Timestamp: 32160 Synchronization Source identifier: 0x07d5dc9c (131456156) Payload: fff0edf4796e6e7af3edf17d6f6e76f7eeeffc726d72fcef...
No. Time Source src port Destination dst port Protocol Info New Column 3513 13:39:29.170502 10.1.1.226 22776 10.1.1.1 18384 RTP PT=ITU-T G.711 PCMU, SSRC=0x7D5DC9C, Seq=16398, Time=32320 214
Frame 3513: 214 bytes on wire (1712 bits), 214 bytes captured (1712 bits) WTAP_ENCAP: 1 Arrival Time: Sep 24, 2013 13:39:29.170502000 CDT [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1380047969.170502000 seconds [Time delta from previous captured frame: 0.002428000 seconds] [Time delta from previous displayed frame: 0.020010000 seconds] [Time since reference or first frame: 30.226008000 seconds] Frame Number: 3513 Frame Length: 214 bytes (1712 bits) Capture Length: 214 bytes (1712 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ip:udp:rtp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Src: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a), Dst: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Destination: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Address: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Source: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) Address: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Type: IP (0x0800) Internet Protocol Version 4, Src: 10.1.1.226 (10.1.1.226), Dst: 10.1.1.1 (10.1.1.1) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport)) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..00 = Explicit Congestion Notification: Not-ECT (Not ECN-Capable Transport) (0x00) Total Length: 200 Identification: 0x0000 (0) Flags: 0x02 (Don't Fragment) 0... .... = Reserved bit: Not set .1.. .... = Don't fragment: Set ..0. .... = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (17) Header checksum: 0x2341 [correct] [Good: True] [Bad: False] Source: 10.1.1.226 (10.1.1.226) Destination: 10.1.1.1 (10.1.1.1) User Datagram Protocol, Src Port: 22776 (22776), Dst Port: 18384 (18384) Source port: 22776 (22776) Destination port: 18384 (18384) Length: 180 Checksum: 0x17aa [validation disabled] [Good Checksum: False] [Bad Checksum: False] Real-Time Transport Protocol [Stream setup by SDP (frame 2754)] [Setup frame: 2754] [Setup Method: SDP] 10.. .... = Version: RFC 1889 Version (2) ..0. .... = Padding: False ...0 .... = Extension: False .... 0000 = Contributing source identifiers count: 0 0... .... = Marker: False Payload type: ITU-T G.711 PCMU (0) Sequence number: 16398 [Extended sequence number: 81934] Timestamp: 32320 Synchronization Source identifier: 0x07d5dc9c (131456156) Payload: fff3eff77a71717bf6eff47e727078f9f0f2fd757075fdf2...
No. Time Source src port Destination dst port Protocol Info New Column 3563 13:39:29.490508 10.1.1.226 22776 10.1.1.1 18384 RTP PT=ITU-T G.711 PCMU, SSRC=0x7D5DC9C, Seq=16399, Time=480, Mark 214
Frame 3563: 214 bytes on wire (1712 bits), 214 bytes captured (1712 bits) WTAP_ENCAP: 1 Arrival Time: Sep 24, 2013 13:39:29.490508000 CDT [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1380047969.490508000 seconds [Time delta from previous captured frame: 0.002419000 seconds] [Time delta from previous displayed frame: 0.320006000 seconds] [Time since reference or first frame: 30.546014000 seconds] Frame Number: 3563 Frame Length: 214 bytes (1712 bits) Capture Length: 214 bytes (1712 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ip:udp:rtp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Src: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a), Dst: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Destination: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Address: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Source: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) Address: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Type: IP (0x0800) Internet Protocol Version 4, Src: 10.1.1.226 (10.1.1.226), Dst: 10.1.1.1 (10.1.1.1) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport)) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..00 = Explicit Congestion Notification: Not-ECT (Not ECN-Capable Transport) (0x00) Total Length: 200 Identification: 0x0000 (0) Flags: 0x02 (Don't Fragment) 0... .... = Reserved bit: Not set .1.. .... = Don't fragment: Set ..0. .... = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (17) Header checksum: 0x2341 [correct] [Good: True] [Bad: False] Source: 10.1.1.226 (10.1.1.226) Destination: 10.1.1.1 (10.1.1.1) User Datagram Protocol, Src Port: 22776 (22776), Dst Port: 18384 (18384) Source port: 22776 (22776) Destination port: 18384 (18384) Length: 180 Checksum: 0x17aa [validation disabled] [Good Checksum: False] [Bad Checksum: False] Real-Time Transport Protocol [Stream setup by SDP (frame 2754)] [Setup frame: 2754] [Setup Method: SDP] 10.. .... = Version: RFC 1889 Version (2) ..0. .... = Padding: False ...0 .... = Extension: False .... 0000 = Contributing source identifiers count: 0 1... .... = Marker: True Payload type: ITU-T G.711 PCMU (0) Sequence number: 16399 [Extended sequence number: 81935] Timestamp: 480 Synchronization Source identifier: 0x07d5dc9c (131456156) Payload: 4f3e352d2b2f42f9dbd2c0b6adaaaec076595241372e2b2e...
No. Time Source src port Destination dst port Protocol Info New Column 3567 13:39:29.510447 10.1.1.226 22776 10.1.1.1 18384 RTP PT=ITU-T G.711 PCMU, SSRC=0x7D5DC9C, Seq=16400, Time=640 214
Frame 3567: 214 bytes on wire (1712 bits), 214 bytes captured (1712 bits) WTAP_ENCAP: 1 Arrival Time: Sep 24, 2013 13:39:29.510447000 CDT [Time shift for this packet: 0.000000000 seconds] Epoch Time: 1380047969.510447000 seconds [Time delta from previous captured frame: 0.002292000 seconds] [Time delta from previous displayed frame: 0.019939000 seconds] [Time since reference or first frame: 30.565953000 seconds] Frame Number: 3567 Frame Length: 214 bytes (1712 bits) Capture Length: 214 bytes (1712 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ip:udp:rtp] [Coloring Rule Name: UDP] [Coloring Rule String: udp] Ethernet II, Src: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a), Dst: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Destination: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) Address: Cisco_e8:a0:11 (00:09:e8:e8:a0:11) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Source: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) Address: Hewlett-_b1:3c:0a (00:13:21:b1:3c:0a) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) Type: IP (0x0800) Internet Protocol Version 4, Src: 10.1.1.226 (10.1.1.226), Dst: 10.1.1.1 (10.1.1.1) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport)) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..00 = Explicit Congestion Notification: Not-ECT (Not ECN-Capable Transport) (0x00) Total Length: 200 Identification: 0x0000 (0) Flags: 0x02 (Don't Fragment) 0... .... = Reserved bit: Not set .1.. .... = Don't fragment: Set ..0. .... = More fragments: Not set Fragment offset: 0 Time to live: 64 Protocol: UDP (17) Header checksum: 0x2341 [correct] [Good: True] [Bad: False] Source: 10.1.1.226 (10.1.1.226) Destination: 10.1.1.1 (10.1.1.1) User Datagram Protocol, Src Port: 22776 (22776), Dst Port: 18384 (18384) Source port: 22776 (22776) Destination port: 18384 (18384) Length: 180 Checksum: 0x17aa [validation disabled] [Good Checksum: False] [Bad Checksum: False] Real-Time Transport Protocol [Stream setup by SDP (frame 2754)] [Setup frame: 2754] [Setup Method: SDP] 10.. .... = Version: RFC 1889 Version (2) ..0. .... = Padding: False ...0 .... = Extension: False .... 0000 = Contributing source identifiers count: 0 0... .... = Marker: False Payload type: ITU-T G.711 PCMU (0) Sequence number: 16400 [Extended sequence number: 81936] Timestamp: 640 Synchronization Source identifier: 0x07d5dc9c (131456156) Payload: b6d65c58493b312c2c354fe2daccbcb2abaab3cd5f584c3d...
From: Michael Jerris <mike@jerris.com> To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Sent: Wednesday, September 25, 2013 4:45 PM Subject: Re: [Freeswitch-users] RTP Wrong Timestamps and audio hiccups in conferencing output
Try looking at the time into the call to find the right packets. Without seeing what exactly is wrong, we are not going to be able to guess what might be going on.
On Sep 24, 2013, at 1:29 PM, D D <tru083@yahoo.com> wrote:
They are flagged as wrong by Wireshark, in the VoIP RTP Player.
Unfortunately, Wireshark does not allow me to get from the 'W' in player back to the packets it thinks are wrong in the detailed view.
From: Michael Jerris <mike@jerris.com> To: FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org> Sent: Tuesday, September 24, 2013 2:49 PM Subject: Re: [Freeswitch-users] RTP Wrong Timestamps and audio hiccups in conferencing output
in what way is the timestamp "wrong"?
On Sep 24, 2013, at 3:30 PM, D D <tru083@yahoo.com> wrote:
Hi,
I am seeing periodic RTP Wrong Timestamps and audio hiccups when using conferencing.
I am calling in from two phones on the local LAN, and playing a 440-Hz tone into the conference on one of the phones.
On the receiving phone, I hear an audio hiccup (and the server-side Wireshark trace shows a Wrong Timestamp) about once every 750 ms. It is very regular on the output from the conference.
The server-side Wireshark of the input RTP stream looks fine -- there are no anomalies.
I am seeing this problem on version 1.2.10 and 1.5.5b.
Is this something I need to report as a bug?
Thanks, David
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Hi Ravi, You have provided very little info. It's not clear if it is a dialplan problem or a fax problem. I tried to access your logs on paste bin and it requires a username and password and I don't know how to get one. I do faxes with freeswitch and it is working pretty well for me. Regards, Ali Pey On Tue, Sep 24, 2013 at 2:02 PM, Ravi <sravi123@yahoo.com> wrote:
Hello Everyone !
I hope, this time some one could help me resolve setting up faxes through Freeswitch. I need some help with setting up faxes. Can anyone in this mailing list offer some help to fix this ?
Thanks. Ravi
On 11/09/13 10:08 PM, Ravi wrote:
Brian,
Firstly, many congratulations on your wedding ! My best wishes !!
Secondly, I am trying to learn Freeswitch and I have made considerable progress, with help from the mailing list :)
The configuration that I have is a PRI line, and a Sangoma A101DE card, with Cent OS. I am based out of India and the service provider is called Bharti Airtel. I have setup the system so it works and I can make and receive calls through Freeswitch.
The firewall in the machine that runs the freeswitch server is disabled. As far as NAT settings, this is the log that I have when Freeswitch server is started.
2013-09-11 21:55:30.737518 [INFO] switch_nat.c:420 Scanning for NAT 2013-09-11 21:55:30.737699 [DEBUG] switch_nat.c:170 Checking for PMP 1/5 2013-09-11 21:55:30.738500 [ERR] switch_nat.c:201 Error checking for PMP [general error] 2013-09-11 21:55:30.738513 [DEBUG] switch_nat.c:425 Checking for UPnP 2013-09-11 21:55:34.339478 [INFO] switch_nat.c:434 NAT detected type: upnp, ExtIP: '123.236.215.39' 2013-09-11 21:55:34.340174 [DEBUG] switch_nat.c:264 NAT thread configured 2013-09-11 21:55:34.340501 [DEBUG] switch_nat.c:275 NAT thread started
The log when I call the fax number (4302050) from a landline is included in pastebin with link given below:
http://pastebin.freeswitch.org/21396
I hope I have answered your questions. I am not sure if you mean that the number 4302050 receives the call, by the term INVITE. Please let me know what I am missing in this, or if any additional information is required.
Many Thanks ! Ravi
------------------------------ *From:* Brian West <brian@freeswitch.org> <brian@freeswitch.org> *To:* FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org><freeswitch-users@lists.freeswitch.org> *Sent:* Sunday, September 8, 2013 11:30 PM *Subject:* Re: [Freeswitch-users] Sending and Receiving faxes - freeswitch
How exactly is this number routed to you and via what provider? Have you verified firewall and nat setting to make sure you actually receiving the INVITE?
On Sep 8, 2013, at 12:53 PM, Ravi <sravi123@yahoo.com> wrote:
When this fax number is called from another telephone, I hear the fax dialtone. But when the fax number is called from any fax machine and try to send a fax, it gives a number not available message. I do not recieve this call in the freeswitch server as well.
-- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH_Wire , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com
T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED)
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services:consulting@freeswitch.orghttp://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Serverhttp://www.cudatel.com
Official FreeSWITCH Siteshttp://www.freeswitch.orghttp://wiki.freeswitch.orghttp://www.cluecon.com
FreeSWITCH-users mailing listFreeSWITCH-users@lists.freeswitch.orghttp://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-usershttp://www.frees...
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Ali, that's the standard FS pastebin, the username and password are in the challenge dialog. Would be nice if the log colouring stuff was simply submitted to Github for inclusion in Gist... On 30 September 2013 13:48, Ali Pey <alipey@gmail.com> wrote:
Hi Ravi,
You have provided very little info. It's not clear if it is a dialplan problem or a fax problem. I tried to access your logs on paste bin and it requires a username and password and I don't know how to get one.
I do faxes with freeswitch and it is working pretty well for me.
Regards, Ali Pey
On Tue, Sep 24, 2013 at 2:02 PM, Ravi <sravi123@yahoo.com> wrote:
Hello Everyone !
I hope, this time some one could help me resolve setting up faxes through Freeswitch. I need some help with setting up faxes. Can anyone in this mailing list offer some help to fix this ?
Thanks. Ravi
On 11/09/13 10:08 PM, Ravi wrote:
Brian,
Firstly, many congratulations on your wedding ! My best wishes !!
Secondly, I am trying to learn Freeswitch and I have made considerable progress, with help from the mailing list :)
The configuration that I have is a PRI line, and a Sangoma A101DE card, with Cent OS. I am based out of India and the service provider is called Bharti Airtel. I have setup the system so it works and I can make and receive calls through Freeswitch.
The firewall in the machine that runs the freeswitch server is disabled. As far as NAT settings, this is the log that I have when Freeswitch server is started.
2013-09-11 21:55:30.737518 [INFO] switch_nat.c:420 Scanning for NAT 2013-09-11 21:55:30.737699 [DEBUG] switch_nat.c:170 Checking for PMP 1/5 2013-09-11 21:55:30.738500 [ERR] switch_nat.c:201 Error checking for PMP [general error] 2013-09-11 21:55:30.738513 [DEBUG] switch_nat.c:425 Checking for UPnP 2013-09-11 21:55:34.339478 [INFO] switch_nat.c:434 NAT detected type: upnp, ExtIP: '123.236.215.39' 2013-09-11 21:55:34.340174 [DEBUG] switch_nat.c:264 NAT thread configured 2013-09-11 21:55:34.340501 [DEBUG] switch_nat.c:275 NAT thread started
The log when I call the fax number (4302050) from a landline is included in pastebin with link given below:
http://pastebin.freeswitch.org/21396
I hope I have answered your questions. I am not sure if you mean that the number 4302050 receives the call, by the term INVITE. Please let me know what I am missing in this, or if any additional information is required.
Many Thanks ! Ravi
------------------------------ *From:* Brian West <brian@freeswitch.org> <brian@freeswitch.org> *To:* FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org><freeswitch-users@lists.freeswitch.org> *Sent:* Sunday, September 8, 2013 11:30 PM *Subject:* Re: [Freeswitch-users] Sending and Receiving faxes - freeswitch
How exactly is this number routed to you and via what provider? Have you verified firewall and nat setting to make sure you actually receiving the INVITE?
On Sep 8, 2013, at 12:53 PM, Ravi <sravi123@yahoo.com> wrote:
When this fax number is called from another telephone, I hear the fax dialtone. But when the fax number is called from any fax machine and try to send a fax, it gives a number not available message. I do not recieve this call in the freeswitch server as well.
-- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH_Wire , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com
T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED)
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services:consulting@freeswitch.orghttp://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Serverhttp://www.cudatel.com
Official FreeSWITCH Siteshttp://www.freeswitch.orghttp://wiki.freeswitch.orghttp://www.cluecon.com
FreeSWITCH-users mailing listFreeSWITCH-users@lists.freeswitch.orghttp://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-usershttp://www.frees...
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Thank you Ben. I see it now and was able to see the logs. It does detect the fax but it seems that the fax signalling doesn't go through and the call is dropped: Fax processing not successful - result (49) The call dropped prematurely. I would try to test with a different fax machine or fax software. Or maybe the line is bad and there is some packet loss or jitter. Fax is very sensitive to media. Regards, Ali Pey On Mon, Sep 30, 2013 at 2:03 PM, Ben Langfeld <ben@langfeld.co.uk> wrote:
Ali, that's the standard FS pastebin, the username and password are in the challenge dialog.
Would be nice if the log colouring stuff was simply submitted to Github for inclusion in Gist...
On 30 September 2013 13:48, Ali Pey <alipey@gmail.com> wrote:
Hi Ravi,
You have provided very little info. It's not clear if it is a dialplan problem or a fax problem. I tried to access your logs on paste bin and it requires a username and password and I don't know how to get one.
I do faxes with freeswitch and it is working pretty well for me.
Regards, Ali Pey
On Tue, Sep 24, 2013 at 2:02 PM, Ravi <sravi123@yahoo.com> wrote:
Hello Everyone !
I hope, this time some one could help me resolve setting up faxes through Freeswitch. I need some help with setting up faxes. Can anyone in this mailing list offer some help to fix this ?
Thanks. Ravi
On 11/09/13 10:08 PM, Ravi wrote:
Brian,
Firstly, many congratulations on your wedding ! My best wishes !!
Secondly, I am trying to learn Freeswitch and I have made considerable progress, with help from the mailing list :)
The configuration that I have is a PRI line, and a Sangoma A101DE card, with Cent OS. I am based out of India and the service provider is called Bharti Airtel. I have setup the system so it works and I can make and receive calls through Freeswitch.
The firewall in the machine that runs the freeswitch server is disabled. As far as NAT settings, this is the log that I have when Freeswitch server is started.
2013-09-11 21:55:30.737518 [INFO] switch_nat.c:420 Scanning for NAT 2013-09-11 21:55:30.737699 [DEBUG] switch_nat.c:170 Checking for PMP 1/5 2013-09-11 21:55:30.738500 [ERR] switch_nat.c:201 Error checking for PMP [general error] 2013-09-11 21:55:30.738513 [DEBUG] switch_nat.c:425 Checking for UPnP 2013-09-11 21:55:34.339478 [INFO] switch_nat.c:434 NAT detected type: upnp, ExtIP: '123.236.215.39' 2013-09-11 21:55:34.340174 [DEBUG] switch_nat.c:264 NAT thread configured 2013-09-11 21:55:34.340501 [DEBUG] switch_nat.c:275 NAT thread started
The log when I call the fax number (4302050) from a landline is included in pastebin with link given below:
http://pastebin.freeswitch.org/21396
I hope I have answered your questions. I am not sure if you mean that the number 4302050 receives the call, by the term INVITE. Please let me know what I am missing in this, or if any additional information is required.
Many Thanks ! Ravi
------------------------------ *From:* Brian West <brian@freeswitch.org> <brian@freeswitch.org> *To:* FreeSWITCH Users Help <freeswitch-users@lists.freeswitch.org><freeswitch-users@lists.freeswitch.org> *Sent:* Sunday, September 8, 2013 11:30 PM *Subject:* Re: [Freeswitch-users] Sending and Receiving faxes - freeswitch
How exactly is this number routed to you and via what provider? Have you verified firewall and nat setting to make sure you actually receiving the INVITE?
On Sep 8, 2013, at 12:53 PM, Ravi <sravi123@yahoo.com> wrote:
When this fax number is called from another telephone, I hear the fax dialtone. But when the fax number is called from any fax machine and try to send a fax, it gives a number not available message. I do not recieve this call in the freeswitch server as well.
-- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH_Wire , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com
T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED)
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services:consulting@freeswitch.orghttp://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Serverhttp://www.cudatel.com
Official FreeSWITCH Siteshttp://www.freeswitch.orghttp://wiki.freeswitch.orghttp://www.cluecon.com
FreeSWITCH-users mailing listFreeSWITCH-users@lists.freeswitch.orghttp://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-usershttp://www.frees...
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Did you map the DID to your fax extension properly? Look at the log files or the console and it'll tell you if you did it correctly or not. From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Ravi Sent: Sunday, September 8, 2013 10:54 AM To: FreeSWITCH Help Subject: [Freeswitch-users] Sending and Receiving faxes - freeswitch Hello Everyone, I am trying to send and receive faxes. I have assigned the number 4302050 for receiving faxes, and the use configuration is given below: <include> <user id="1050"> <params> <param name="password" value="$${default_password}"/> <param name="vm-password" value="1050"/> </params> <variables> <variable name="toll_allow" value="domestic,international,local"/> <variable name="accountcode" value="1050"/> <variable name="user_context" value="default"/> <variable name="effective_caller_id_name" value="Extension 1050"/> <variable name="effective_caller_id_number" value="1050"/> <variable name="outbound_caller_id_name" value="$${outbound_caller_name}"/> <variable name="outbound_caller_id_number" value="$${outbound_caller_id}"/> <variable name="callgroup" value="techsupport"/> </variables> </user> </include> The dial plan that I have in place to receive faxes is given below: <extension name="fax_receive"> <condition field="destination_number" expression="^(050$)"> <action application="set" data="ignore_early_media=true"/> <action application="answer" /> <action application="playback" data="silence_stream://2000"/> <action application="rxfax" data="$${base_dir}/faxes/${caller_id_number}.tif"/> <action application="hangup"/> </condition> </extension> When this fax number is called from another telephone, I hear the fax dialtone. But when the fax number is called from any fax machine and try to send a fax, it gives a number not available message. I do not recieve this call in the freeswitch server as well. Would really appreciate if anyone could help me in this, to let me know if I am missing something. Thanks in advance. Ravi
participants (8)
-
Ali Pey
-
Ben Langfeld
-
Brian West
-
Cal Leeming [Simplicity Media Ltd]
-
D D
-
Jeff Leung
-
Michael Jerris
-
Ravi