Jump to content

Fax problem (Zoiper, external extension)


lionfort
 Share

Recommended Posts

Dear Snom-Community,

 

I have been setting up snomOne free now for about 10 days and I have been playing around with some preferences and features. I have also tested auto attendant and such very nice features...my SIP trunk provider also told me to support all necessary fax codecs (like T.38) which Zoiper and other external fax devices need to support.

 

Now that I have been trying all the other things, I have decided to test the very last thing...the fax-feature...unfortunately non of my tries worked:

 

1. I have tried to register a ZoiPer SIP Client as a fax .... not working (I thought because it was a free version)

2. I have tried to send the call to an external fax device ... not working

3. I have tried to send the fax-call to another (knowingly working) fax-machine ... not receiving the fax

 

How can I finally manage to receive faxes IF my SIP trunk provider guarantees to have T.38 turned on?

Link to comment
Share on other sites

Hi,

 

I have tried that and the result did not satisfy me...indeed it did not work for me!

 


[7] 2012/06/24 23:40:49:	SIP Tx udp:127.0.0.1:35211:
SIP/2.0 200 Ok
v: SIP/2.0/UDP 178.189.81.234:38922;branch=z9hG4bK-d8754z-f5213011ffe72227-1---d8754z-;rport=35211;received=127.0.0.1
f: "269" <sip:269@localhost;transport=UDP>;tag=f4f4a976
t: "269" <sip:269@localhost;transport=UDP>;tag=1b295e111e
i: NjhjN2QyMDVkZjBjYjc1MTMzNTAzYzdjZTVlYjM2YTA.
CSeq: 1752 REGISTER
m: <sip:269@178.189.81.234:38922;rinstance=89bb46f3c21d0520;transport=UDP>;expires=32
l: 0

[6] 2012/06/24 23:40:57:	Received DTMF F
[7] 2012/06/24 23:41:01:	Call 5518e16d@pbx: Clear last request
[5] 2012/06/24 23:41:01:	BYE Response: Terminate 5518e16d@pbx
[7] 2012/06/24 23:41:16:	SIP Rx udp:127.0.0.1:35211:
REGISTER sip:localhost;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 178.189.81.234:38922;branch=z9hG4bK-d8754z-7ec940d292eff491-1---d8754z-
Max-Forwards: 70
Contact: <sip:269@178.189.81.234:38922;rinstance=89bb46f3c21d0520;transport=UDP>
To: "269"<sip:269@localhost;transport=UDP>
From: "269"<sip:269@localhost;transport=UDP>;tag=f4f4a976
Call-ID: NjhjN2QyMDVkZjBjYjc1MTMzNTAzYzdjZTVlYjM2YTA.
CSeq: 1753 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, X-cisco-serviceuri
User-Agent: Zoiper Communicator 2.05.11136 rev.11135
Authorization: Digest username="269",realm="localhost",nonce="0f66f28d88ab8bec3d51c1e1126ee647",uri="sip:localhost;transport=UDP",response="dead0882ec273b2c909e1be1d3632a49",algorithm=MD5
Allow-Events: presence, kpml
Content-Length: 0

[7] 2012/06/24 23:41:16:	SIP Tx udp:127.0.0.1:35211:
SIP/2.0 200 Ok
v: SIP/2.0/UDP 178.189.81.234:38922;branch=z9hG4bK-d8754z-7ec940d292eff491-1---d8754z-;rport=35211;received=127.0.0.1
f: "269" <sip:269@localhost;transport=UDP>;tag=f4f4a976
t: "269" <sip:269@localhost;transport=UDP>;tag=1b295e111e
i: NjhjN2QyMDVkZjBjYjc1MTMzNTAzYzdjZTVlYjM2YTA.
CSeq: 1753 REGISTER
m: <sip:269@178.189.81.234:38922;rinstance=89bb46f3c21d0520;transport=UDP>;expires=31
l: 0

[6] 2012/06/24 23:41:18:	Received DTMF F
[7] 2012/06/24 23:41:22:	54c9b654@pbx: Media-aware pass-through mode
[7] 2012/06/24 23:41:22:	Call 54c9b654@pbx: Clear last request
[5] 2012/06/24 23:41:22:	BYE Response: Terminate 54c9b654@pbx
[6] 2012/06/24 23:41:24:	Received DTMF 2
[1] 2012/06/24 23:41:35:	UDP: TOS could not be set
[1] 2012/06/24 23:41:35:	Last message repeated 2 times
[5] 2012/06/24 23:41:35:	Identify trunk (IP address/port and domain match) 2
[7] 2012/06/24 23:41:35:	Set packet length to 20
[6] 2012/06/24 23:41:35:	Sending RTP for 6c4c545c1f5b115f40b037da6c0507b0@sgw2.at.telgo.cc to 91.211.35.233:28060, codec not set yet
[5] 2012/06/24 23:41:35:	Domain trunk 0043720005761@pbx.company.com sends call to 269 in domain pbx.company.com
[7] 2012/06/24 23:41:35:	set_codecs: for 6c4c545c1f5b115f40b037da6c0507b0@sgw2.at.telgo.cc codecs "8 0", codec_preference count 3
[1] 2012/06/24 23:41:35:	UDP: TOS could not be set
[1] 2012/06/24 23:41:35:	Last message repeated 2 times
[7] 2012/06/24 23:41:35:	set_codecs: for 4d4fc56f@pbx codecs "", codec_preference count 6
[7] 2012/06/24 23:41:35:	Set packet length to 20
[6] 2012/06/24 23:41:35:	Codec pcma/8000 is chosen for call id 6c4c545c1f5b115f40b037da6c0507b0@sgw2.at.telgo.cc
[6] 2012/06/24 23:41:38:	Sending RTP for 4d4fc56f@pbx to 127.0.0.1:8000, codec not set yet
[7] 2012/06/24 23:41:38:	Call 4d4fc56f@pbx: Clear last INVITE
[6] 2012/06/24 23:41:38:	Codec pcmu/8000 is chosen for call id 4d4fc56f@pbx
[7] 2012/06/24 23:41:38:	Determine pass-through mode after receiving response
[6] 2012/06/24 23:41:38:	Codec pcmu/8000 is chosen for call id 32a2e112@pbx
[7] 2012/06/24 23:41:38:	6c4c545c1f5b115f40b037da6c0507b0@sgw2.at.telgo.cc: RTP pass-through mode
[7] 2012/06/24 23:41:38:	4d4fc56f@pbx: RTP pass-through mode
[7] 2012/06/24 23:41:38:	2a86e7d22fd8dcd42dbe6d795eda699f@sgw2.at.telgo.cc: Media-aware pass-through mode
[6] 2012/06/24 23:41:38:	Different Codecs (local pcma/8000, remote pcmu/8000), callid 6c4c545c1f5b115f40b037da6c0507b0@sgw2.at.telgo.cc, falling back to transcoding
[7] 2012/06/24 23:41:42:	SIP Rx udp:127.0.0.1:35211:
REGISTER sip:localhost;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 178.189.81.234:38922;branch=z9hG4bK-d8754z-3f2e8d8a03560671-1---d8754z-
Max-Forwards: 70
Contact: <sip:269@178.189.81.234:38922;rinstance=89bb46f3c21d0520;transport=UDP>
To: "269"<sip:269@localhost;transport=UDP>
From: "269"<sip:269@localhost;transport=UDP>;tag=f4f4a976
Call-ID: NjhjN2QyMDVkZjBjYjc1MTMzNTAzYzdjZTVlYjM2YTA.
CSeq: 1754 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, X-cisco-serviceuri
User-Agent: Zoiper Communicator 2.05.11136 rev.11135
Authorization: Digest username="269",realm="localhost",nonce="0f66f28d88ab8bec3d51c1e1126ee647",uri="sip:localhost;transport=UDP",response="dead0882ec273b2c909e1be1d3632a49",algorithm=MD5
Allow-Events: presence, kpml
Content-Length: 0

[7] 2012/06/24 23:41:42:	SIP Tx udp:127.0.0.1:35211:
SIP/2.0 200 Ok
v: SIP/2.0/UDP 178.189.81.234:38922;branch=z9hG4bK-d8754z-3f2e8d8a03560671-1---d8754z-;rport=35211;received=127.0.0.1
f: "269" <sip:269@localhost;transport=UDP>;tag=f4f4a976
t: "269" <sip:269@localhost;transport=UDP>;tag=1b295e111e
i: NjhjN2QyMDVkZjBjYjc1MTMzNTAzYzdjZTVlYjM2YTA.
CSeq: 1754 REGISTER
m: <sip:269@178.189.81.234:38922;rinstance=89bb46f3c21d0520;transport=UDP>;expires=28
l: 0

[7] 2012/06/24 23:41:44:	Call 32a2e112@pbx: Clear last request
[5] 2012/06/24 23:41:44:	BYE Response: Terminate 32a2e112@pbx
[6] 2012/06/24 23:41:46:	Received DTMF 0
[6] 2012/06/24 23:41:47:	Received DTMF 8
[7] 2012/06/24 23:42:05:	SIP Rx udp:127.0.0.1:35211:
REGISTER sip:localhost;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 178.189.81.234:38922;branch=z9hG4bK-d8754z-6858c319a1df1e8b-1---d8754z-
Max-Forwards: 70
Contact: <sip:269@178.189.81.234:38922;rinstance=89bb46f3c21d0520;transport=UDP>
To: "269"<sip:269@localhost;transport=UDP>
From: "269"<sip:269@localhost;transport=UDP>;tag=f4f4a976
Call-ID: NjhjN2QyMDVkZjBjYjc1MTMzNTAzYzdjZTVlYjM2YTA.
CSeq: 1755 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, X-cisco-serviceuri
User-Agent: Zoiper Communicator 2.05.11136 rev.11135
Authorization: Digest username="269",realm="localhost",nonce="0f66f28d88ab8bec3d51c1e1126ee647",uri="sip:localhost;transport=UDP",response="dead0882ec273b2c909e1be1d3632a49",algorithm=MD5
Allow-Events: presence, kpml
Content-Length: 0

[7] 2012/06/24 23:42:05:	SIP Tx udp:127.0.0.1:35211:
SIP/2.0 200 Ok
v: SIP/2.0/UDP 178.189.81.234:38922;branch=z9hG4bK-d8754z-6858c319a1df1e8b-1---d8754z-;rport=35211;received=127.0.0.1
f: "269" <sip:269@localhost;transport=UDP>;tag=f4f4a976
t: "269" <sip:269@localhost;transport=UDP>;tag=1b295e111e
i: NjhjN2QyMDVkZjBjYjc1MTMzNTAzYzdjZTVlYjM2YTA.
CSeq: 1755 REGISTER
m: <sip:269@178.189.81.234:38922;rinstance=89bb46f3c21d0520;transport=UDP>;expires=30
l: 0

[1] 2012/06/24 23:42:18:	UDP: TOS could not be set
[1] 2012/06/24 23:42:18:	Last message repeated 2 times
[5] 2012/06/24 23:42:18:	Identify trunk (IP address/port and domain match) 2
[7] 2012/06/24 23:42:18:	Set packet length to 20
[6] 2012/06/24 23:42:18:	Sending RTP for 53cb70c73d7d987173e0d5be4694ae28@sgw2.at.telgo.cc to 91.211.35.233:11206, codec not set yet
[5] 2012/06/24 23:42:18:	Domain trunk 0043720005761@pbx.company.com sends call to 123 in domain pbx.company.com
[7] 2012/06/24 23:42:18:	set_codecs: for 53cb70c73d7d987173e0d5be4694ae28@sgw2.at.telgo.cc codecs "8 0", codec_preference count 3
[7] 2012/06/24 23:42:18:	Set packet length to 20
[6] 2012/06/24 23:42:18:	Codec pcma/8000 is chosen for call id 53cb70c73d7d987173e0d5be4694ae28@sgw2.at.telgo.cc
[6] 2012/06/24 23:42:20:	Received DTMF F
[1] 2012/06/24 23:42:20:	UDP: TOS could not be set
[1] 2012/06/24 23:42:20:	Last message repeated 2 times
[7] 2012/06/24 23:42:20:	set_codecs: for e3a10dbc@pbx codecs "", codec_preference count 6
[6] 2012/06/24 23:42:23:	Sending RTP for e3a10dbc@pbx to 127.0.0.1:8004, codec not set yet
[7] 2012/06/24 23:42:24:	Call e3a10dbc@pbx: Clear last INVITE
[6] 2012/06/24 23:42:24:	Codec pcmu/8000 is chosen for call id e3a10dbc@pbx
[7] 2012/06/24 23:42:24:	Determine pass-through mode after receiving response
[6] 2012/06/24 23:42:24:	Codec pcmu/8000 is chosen for call id 4d4fc56f@pbx
[7] 2012/06/24 23:42:24:	53cb70c73d7d987173e0d5be4694ae28@sgw2.at.telgo.cc: RTP pass-through mode
[7] 2012/06/24 23:42:24:	e3a10dbc@pbx: RTP pass-through mode
[7] 2012/06/24 23:42:24:	6c4c545c1f5b115f40b037da6c0507b0@sgw2.at.telgo.cc: Media-aware pass-through mode
[6] 2012/06/24 23:42:24:	Different Codecs (local pcma/8000, remote pcmu/8000), callid 53cb70c73d7d987173e0d5be4694ae28@sgw2.at.telgo.cc, falling back to transcoding
[7] 2012/06/24 23:42:30:	SIP Rx udp:127.0.0.1:35211:
REGISTER sip:localhost;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 178.189.81.234:38922;branch=z9hG4bK-d8754z-975d23f984ae149d-1---d8754z-
Max-Forwards: 70
Contact: <sip:269@178.189.81.234:38922;rinstance=89bb46f3c21d0520;transport=UDP>
To: "269"<sip:269@localhost;transport=UDP>
From: "269"<sip:269@localhost;transport=UDP>;tag=f4f4a976
Call-ID: NjhjN2QyMDVkZjBjYjc1MTMzNTAzYzdjZTVlYjM2YTA.
CSeq: 1756 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, X-cisco-serviceuri
User-Agent: Zoiper Communicator 2.05.11136 rev.11135
Authorization: Digest username="269",realm="localhost",nonce="0f66f28d88ab8bec3d51c1e1126ee647",uri="sip:localhost;transport=UDP",response="dead0882ec273b2c909e1be1d3632a49",algorithm=MD5
Allow-Events: presence, kpml
Content-Length: 0

[7] 2012/06/24 23:42:30:	SIP Tx udp:127.0.0.1:35211:
SIP/2.0 200 Ok
v: SIP/2.0/UDP 178.189.81.234:38922;branch=z9hG4bK-d8754z-975d23f984ae149d-1---d8754z-;rport=35211;received=127.0.0.1
f: "269" <sip:269@localhost;transport=UDP>;tag=f4f4a976
t: "269" <sip:269@localhost;transport=UDP>;tag=1b295e111e
i: NjhjN2QyMDVkZjBjYjc1MTMzNTAzYzdjZTVlYjM2YTA.
CSeq: 1756 REGISTER
m: <sip:269@178.189.81.234:38922;rinstance=89bb46f3c21d0520;transport=UDP>;expires=28
l: 0

[6] 2012/06/24 23:42:36:	Received DTMF F
[7] 2012/06/24 23:42:38:	Call 4d4fc56f@pbx: Clear last request
[5] 2012/06/24 23:42:38:	BYE Response: Terminate 4d4fc56f@pbx
[6] 2012/06/24 23:42:39:	Received DTMF F
[6] 2012/06/24 23:42:43:	Received DTMF 4
[6] 2012/06/24 23:42:51:	Received DTMF F
[7] 2012/06/24 23:42:53:	SIP Rx udp:127.0.0.1:35211:
REGISTER sip:localhost;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 178.189.81.234:38922;branch=z9hG4bK-d8754z-4b54bab4fa2cf7a3-1---d8754z-
Max-Forwards: 70
Contact: <sip:269@178.189.81.234:38922;rinstance=89bb46f3c21d0520;transport=UDP>
To: "269"<sip:269@localhost;transport=UDP>
From: "269"<sip:269@localhost;transport=UDP>;tag=f4f4a976
Call-ID: NjhjN2QyMDVkZjBjYjc1MTMzNTAzYzdjZTVlYjM2YTA.
CSeq: 1757 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, NOTIFY, REFER, MESSAGE, OPTIONS, INFO, SUBSCRIBE
Supported: replaces, norefersub, extended-refer, X-cisco-serviceuri
User-Agent: Zoiper Communicator 2.05.11136 rev.11135
Authorization: Digest username="269",realm="localhost",nonce="0f66f28d88ab8bec3d51c1e1126ee647",uri="sip:localhost;transport=UDP",response="dead0882ec273b2c909e1be1d3632a49",algorithm=MD5
Allow-Events: presence, kpml
Content-Length: 0

[7] 2012/06/24 23:42:53:	SIP Tx udp:127.0.0.1:35211:
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 178.189.81.234:38922;branch=z9hG4bK-d8754z-4b54bab4fa2cf7a3-1---d8754z-;rport=35211;received=127.0.0.1
From: "269" <sip:269@localhost;transport=UDP>;tag=f4f4a976
To: "269" <sip:269@localhost;transport=UDP>;tag=1b295e111e
Call-ID: NjhjN2QyMDVkZjBjYjc1MTMzNTAzYzdjZTVlYjM2YTA.
CSeq: 1757 REGISTER
Contact: <sip:269@178.189.81.234:38922;rinstance=89bb46f3c21d0520;transport=UDP>;expires=32
Content-Length: 0

Link to comment
Share on other sites

Well, there is a BYE message in the trace and obviously a lot of RTP audio (non-T.38) with a service provider on public IP. The interesting part would have been the beginning of the call, where the PBX tries to send a Re-INVITE with the T.38 stuff in the SDP. Can you trya again and record from the begining?

Link to comment
Share on other sites

I am looking at some old posts in the forum about Zoiper... (http://forum.snomone.com/index.php?/topic/2256-fax-help/). It seems that Zoiper does not detect the fax tone in the regular RTP stream, so that yes the PBX will redirect the call to Zoiper when it detects fax in the media stream, but then Zoiper does not detect it and just sits there. The post is already a few years old, maybe Zoiper in the meantime has an option to detect the CNG tone; if not I am afraid Zoiper will not be the solution to your problem.

Link to comment
Share on other sites

Dear helpers,

 

I just tried the following setup:

 

Auto Attendant --> Forward with "F" to ZoiPer Extension (not possible)

Auto Attendant --> Forward with "F" to Fax Online fax number (not possible)

Auto Attendant --> Forward with "F" to PSNT old fashioned fax (not possible)

 

I assume that the PBX changes the codec to a non working tone :( so why is nothing here possible...I am kind of frustrated because it is not possible to receive a fax in any way...I must be able to receive a fax...

Link to comment
Share on other sites

I assume that the PBX changes the codec to a non working tone :( so why is nothing here possible...I am kind of frustrated because it is not possible to receive a fax in any way...I must be able to receive a fax...

 

Fax is not easy if you transmit the data over the public Internet. Because Fax is a modem, when you loose a single RTP packet, the fax transmission is over. That is why they invented T.38 (unfortunately it also solves only a part of the problem, thats why people move to https-based fax). First of all, your service provider msut support it; and then the connected device. Many people just use a ATA, with that it kind of stable works (e.g. AudioCodes ATA even support HTTPS Fax). There is also fax to email software available, but this is usually not so cheap. Modern Fax devices even support fax to email, the cheapest route might be to get a ATA then connect it over the cable with a 200 USD printer that support fax to email.

Link to comment
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.
Note: Your post will require moderator approval before it will be visible.

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...
 Share

×
×
  • Create New...