Sponsor: VoiceMeUp - Corporate & Wholesale VoIP Services

VoIP Mailing List Archives
Mailing list archives for the VoIP community
 SearchSearch 

[Freeswitch-users] T.38 via UPDATE request


 
Post new topic   Reply to topic    VoIP Mailing List Archives Forum Index -> freeSWITCH Users
View previous topic :: View next topic  
Author Message
Prometheus001 at gmx.net
Guest





PostPosted: Wed Oct 14, 2009 6:05 am    Post subject: [Freeswitch-users] T.38 via UPDATE request Reply with quote

Hello,

we have the following problem.
2 Fax machines are communicating via Freeswitch. One is externally
attached via a Telco who is able to handle T.38. The other one is
attached locally.

When 2 Fax machines start syncing each other, the Telco sends a SIP
UPDATE message with T.38 SDP, as it detects fax during the fax negociations.
Freeswitch answers with an SIP OK message back to the telco, and I can
see the T.38 SDP on the debug console of freeswitch.
Then nothing happens any more until one of fax machines detects timeout.

We have set proxy-media to true. However is was done during call setup
when both machines communicated with G711 SDP.
The UPDATE message was commited by FS to the telco, but was not sent to
the other fax, so I think in this case Freeswitch is supposed to
transcode between T.38 and G711 which it cannot do, as we know.

How can I overcome this scenario? Is this a defect, should freeswitch
send the UPDATE message to the other fax? Or is there a workaround?

Best regards
Peter

Here's the UPDATE message:
UPDATE sip:mod_sofia@82.115.xx.xxx:5080 SIP/2.0.
Call-ID: 5283fe4e-334f-122d-d1b9-001517956764.
Contact: <sip:212.91.xxx.xxx:5060>.
Content-Type: application/sdp.
CSeq: 16340063 UPDATE.
From: <sip:06912345678@sip.telco.de>;tag=00-08135-017e041a-4d21f6037.
Max-Forwards: 31.
Route: <sip:82.115.96.165;lr;ftag=pH663F4S02erm>.
To: "030987654321" <sip:030987654321@82.115.xx.xxx>;tag=pH663F4S02erm.
User-Agent: Cirpack/v4.41e (gw_sip).
Via: SIP/2.0/UDP 212.91.xxx.xxx:5060;branch=z9hG4bK-178C-1923B31.
Content-Length: 300.
.
v=0.
o=cp10 125551618103 125551618105 IN IP4 212.91.xxx.xx.
s=SIP Call.
c=IN IP4 212.91.xxx.xx.
t=0 0.
m=image 6860 udptl t38.
a=sendrecv.
a=T38FaxVersion:0.
a=T38MaxBitRate:9600.
a=T38FaxRateManagement:transferredTCF.
a=T38FaxMaxBuffer:1000.
a=T38FaxMaxDatagram:200.
a=T38FaxUdpEC:t38UDPRedundancy.

_______________________________________________
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
Back to top
mike at jerris.com
Guest





PostPosted: Fri Oct 16, 2009 8:42 am    Post subject: [Freeswitch-users] T.38 via UPDATE request Reply with quote

There was just a bunch of work on UPDATE, can you confirm this is the
same behavior with trunk?

On Oct 14, 2009, at 6:55 AM, Peter P GMX wrote:

Quote:
Hello,

we have the following problem.
2 Fax machines are communicating via Freeswitch. One is externally
attached via a Telco who is able to handle T.38. The other one is
attached locally.

When 2 Fax machines start syncing each other, the Telco sends a SIP
UPDATE message with T.38 SDP, as it detects fax during the fax
negociations.
Freeswitch answers with an SIP OK message back to the telco, and I can
see the T.38 SDP on the debug console of freeswitch.
Then nothing happens any more until one of fax machines detects
timeout.

We have set proxy-media to true. However is was done during call setup
when both machines communicated with G711 SDP.
The UPDATE message was commited by FS to the telco, but was not sent
to
the other fax, so I think in this case Freeswitch is supposed to
transcode between T.38 and G711 which it cannot do, as we know.

How can I overcome this scenario? Is this a defect, should freeswitch
send the UPDATE message to the other fax? Or is there a workaround?

Best regards
Peter


_______________________________________________
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
Back to top
Prometheus001 at gmx.net
Guest





PostPosted: Fri Oct 16, 2009 9:47 am    Post subject: [Freeswitch-users] T.38 via UPDATE request Reply with quote

Hello Michael

this is a productive system, so I can currently not update to the
current trunk.
But the installed SVN is 14741. Were those changes after 14741? Then
I'll try to find a timeslot at night in order to update freeswitch.

But Freeswitch should forward the UPDATE request in proxy-media mode, right?

Best regards
Peter

Michael Jerris schrieb:
Quote:
There was just a bunch of work on UPDATE, can you confirm this is the
same behavior with trunk?

On Oct 14, 2009, at 6:55 AM, Peter P GMX wrote:


Quote:
Hello,

we have the following problem.
2 Fax machines are communicating via Freeswitch. One is externally
attached via a Telco who is able to handle T.38. The other one is
attached locally.

When 2 Fax machines start syncing each other, the Telco sends a SIP
UPDATE message with T.38 SDP, as it detects fax during the fax
negociations.
Freeswitch answers with an SIP OK message back to the telco, and I can
see the T.38 SDP on the debug console of freeswitch.
Then nothing happens any more until one of fax machines detects
timeout.

We have set proxy-media to true. However is was done during call setup
when both machines communicated with G711 SDP.
The UPDATE message was commited by FS to the telco, but was not sent
to
the other fax, so I think in this case Freeswitch is supposed to
transcode between T.38 and G711 which it cannot do, as we know.

How can I overcome this scenario? Is this a defect, should freeswitch
send the UPDATE message to the other fax? Or is there a workaround?

Best regards
Peter



_______________________________________________
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



_______________________________________________
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
Back to top
anthony.minessale at g...
Guest





PostPosted: Fri Oct 16, 2009 5:08 pm    Post subject: [Freeswitch-users] T.38 via UPDATE request Reply with quote

I'm sure it won't work because we only implemented forwarding t38 with invite
it would require adding code to say the least.


On Fri, Oct 16, 2009 at 9:35 AM, Peter P GMX <Prometheus001@gmx.net (Prometheus001@gmx.net)> wrote:
Quote:
Hello Michael

this is a productive system, so I can currently not update to the
current trunk.
But the installed SVN is 14741. Were those changes after 14741? Then
I'll try to find a timeslot at night in order to update freeswitch.

But Freeswitch should forward the UPDATE request in proxy-media mode, right?

Best regards
Peter

Michael Jerris schrieb:

Quote:
There was just a bunch of work on UPDATE, can you confirm this is the
same behavior with trunk?

On Oct 14, 2009, at 6:55 AM, Peter P GMX wrote:


Quote:
Hello,

we have the following problem.
2 Fax machines are communicating via Freeswitch. One is externally
attached via a Telco who is able to handle T.38. The other one is
attached locally.

When 2 Fax machines start syncing each other, the Telco sends a SIP
UPDATE message with T.38 SDP, as it detects fax during the fax
negociations.
Freeswitch answers with an SIP OK message back to the telco, and I can
see the T.38 SDP on the debug console of freeswitch.
Then nothing happens any more until one of fax machines detects
timeout.

We have set proxy-media to true. However is was done during call setup
when both machines communicated with G711 SDP.
The UPDATE message was commited by FS to the telco, but was not sent
to
the other fax, so I think in this case Freeswitch is supposed to
transcode between T.38 and G711 which it cannot do, as we know.

How can I overcome this scenario? Is this a defect, should freeswitch
send the UPDATE message to the other fax?  Or is there a workaround?

Best regards
Peter



_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org (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



_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org (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





--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale@hotmail.com ([email]MSN%3Aanthony_minessale@hotmail.com[/email])
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com ([email]PAYPAL%3Aanthony.minessale@gmail.com[/email])
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org ([email]sip%3A888@conference.freeswitch.org[/email])
iax:guest@conference.freeswitch.org/888
googletalk:conf+888@conference.freeswitch.org ([email]googletalk%3Aconf%2B888@conference.freeswitch.org[/email])
pstn:213-799-1400
Back to top
Display posts from previous:   
Post new topic   Reply to topic    VoIP Mailing List Archives Forum Index -> freeSWITCH Users All times are GMT - 5 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group

VoiceMeUp - Corporate & Wholesale VoIP Services