I have two types of devices, one supports text/html MESSAGE content and one that only supports text/plain MESSAGE content. When I send an IM from the first to the second, the second replies with 415 Unsupported Media Type (as shown below). Section 8.1.3.5 of RFC 3261 says the sender should retry using the media type acceptable to the receiver (in this case: plain/text). The problem I have is that Freeswitch doesn't pass the error back to the sender (nor does it retry itself using plain/text). So the IM is lost. Does anyone see the reason why the error is not being handled correctly? ------------------------------------------------------------------------ send 668 bytes to udp/[192.168.72.141]:5062 at 18:43:24.720446: ------------------------------------------------------------------------ MESSAGE sip:5398@192.168.72.141:5062 SIP/2.0 Via: SIP/2.0/UDP 192.168.72.141;rport;branch=z9hG4bKXg6SNUcQa5Kre Max-Forwards: 70 From: "5382 on 141" <sip:5382@192.168.72.141>;tag=66661130 To: "5398" <sip:5398@192.168.72.141:5062> Call-ID: a9891a15-9da9-122d-b3ad-003048d7e9f0 CSeq: 127444135 MESSAGE Contact: <sip:mod_sofia@192.168.72.141:5060> User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-32M Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, precondition, path, replaces Content-Type: text/html Content-Length: 63 <font size="2" face="Arial">hello this is Jerry from Teo</font> ------------------------------------------------------------------------ recv 459 bytes from udp/[192.168.72.141]:5062 at 18:43:24.728390: ------------------------------------------------------------------------ SIP/2.0 415 Unsupported media type Via: SIP/2.0/UDP 192.168.72.141;rport=5060;branch=z9hG4bKXg6SNUcQa5Kre;received=192.168.72.14 1 From: "5382 on 141" <sip:5382@192.168.72.141>;tag=66661130 To: "5398" <sip:5398@192.168.72.141:5062> Call-ID: a9891a15-9da9-122d-b3ad-003048d7e9f0 CSeq: 127444135 MESSAGE Date: Fri, 26 Feb 2010 18:43:24 GMT User-Agent: MobilityGateway-2.0.34078 Server: MobilityGateway-2.0.34078 Accept: text/plain Content-Length: 0 Best Regards, Jerry
Its really clear here you'll need to say text/plain in the content type their accept header says they only take text/plain. /b On Feb 26, 2010, at 12:57 PM, Jerry Richards wrote:
I have two types of devices, one supports text/html MESSAGE content and one that only supports text/plain MESSAGE content. When I send an IM from the first to the second, the second replies with 415 Unsupported Media Type (as shown below). Section 8.1.3.5 of RFC 3261 says the sender should retry using the media type acceptable to the receiver (in this case: plain/text).
The problem I have is that Freeswitch doesn't pass the error back to the sender (nor does it retry itself using plain/text). So the IM is lost. Does anyone see the reason why the error is not being handled correctly?
------------------------------------------------------------------------ send 668 bytes to udp/[192.168.72.141]:5062 at 18:43:24.720446: ------------------------------------------------------------------------ MESSAGE sip:5398@192.168.72.141:5062 SIP/2.0 Via: SIP/2.0/UDP 192.168.72.141;rport;branch=z9hG4bKXg6SNUcQa5Kre Max-Forwards: 70 From: "5382 on 141" <sip:5382@192.168.72.141>;tag=66661130 To: "5398" <sip:5398@192.168.72.141:5062> Call-ID: a9891a15-9da9-122d-b3ad-003048d7e9f0 CSeq: 127444135 MESSAGE Contact: <sip:mod_sofia@192.168.72.141:5060> User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-32M Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, precondition, path, replaces Content-Type: text/html Content-Length: 63
<font size="2" face="Arial">hello this is Jerry from Teo</font> ------------------------------------------------------------------------ recv 459 bytes from udp/[192.168.72.141]:5062 at 18:43:24.728390: ------------------------------------------------------------------------ SIP/2.0 415 Unsupported media type Via: SIP/2.0/UDP 192.168.72.141;rport=5060;branch=z9hG4bKXg6SNUcQa5Kre;received=192.168.72.14 1 From: "5382 on 141" <sip:5382@192.168.72.141>;tag=66661130 To: "5398" <sip:5398@192.168.72.141:5062> Call-ID: a9891a15-9da9-122d-b3ad-003048d7e9f0 CSeq: 127444135 MESSAGE Date: Fri, 26 Feb 2010 18:43:24 GMT User-Agent: MobilityGateway-2.0.34078 Server: MobilityGateway-2.0.34078 Accept: text/plain Content-Length: 0
Best Regards, Jerry
_______________________________________________ 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
I'm not sure I follow your comment. The first device prefers text/html so that's what it normally sets in the initial MESSAGE. Devices that support text/html will not generate this 415 error reply. It's only devices that don't support it that would send the 415 reply, so the issue is that the 415 is not getting passed back to the originator. Best Regards, Jerry -----Original Message----- From: Brian West [mailto:brian@freeswitch.org] Sent: Friday, February 26, 2010 11:01 AM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] 415 Unsupported Media Handling Its really clear here you'll need to say text/plain in the content type their accept header says they only take text/plain. /b On Feb 26, 2010, at 12:57 PM, Jerry Richards wrote:
I have two types of devices, one supports text/html MESSAGE content and one that only supports text/plain MESSAGE content. When I send an IM from the first to the second, the second replies with 415 Unsupported Media Type (as shown below). Section 8.1.3.5 of RFC 3261 says the sender should retry using the media type acceptable to the
receiver (in this case: plain/text).
The problem I have is that Freeswitch doesn't pass the error back to the sender (nor does it retry itself using plain/text). So the IM is
lost.
Does anyone see the reason why the error is not being handled correctly?
---------------------------------------------------------------------- -- send 668 bytes to udp/[192.168.72.141]:5062 at 18:43:24.720446: ------------------------------------------------------------------------ MESSAGE sip:5398@192.168.72.141:5062 SIP/2.0 Via: SIP/2.0/UDP 192.168.72.141;rport;branch=z9hG4bKXg6SNUcQa5Kre Max-Forwards: 70 From: "5382 on 141" <sip:5382@192.168.72.141>;tag=66661130 To: "5398" <sip:5398@192.168.72.141:5062> Call-ID: a9891a15-9da9-122d-b3ad-003048d7e9f0 CSeq: 127444135 MESSAGE Contact: <sip:mod_sofia@192.168.72.141:5060> User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-32M Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, precondition, path, replaces Content-Type: text/html Content-Length: 63
<font size="2" face="Arial">hello this is Jerry from Teo</font>
---------------------------------------------------------------------- -- recv 459 bytes from udp/[192.168.72.141]:5062 at 18:43:24.728390: ------------------------------------------------------------------------ SIP/2.0 415 Unsupported media type Via: SIP/2.0/UDP 192.168.72.141;rport=5060;branch=z9hG4bKXg6SNUcQa5Kre;received=192.168 .72.14 1 From: "5382 on 141" <sip:5382@192.168.72.141>;tag=66661130 To: "5398" <sip:5398@192.168.72.141:5062> Call-ID: a9891a15-9da9-122d-b3ad-003048d7e9f0 CSeq: 127444135 MESSAGE Date: Fri, 26 Feb 2010 18:43:24 GMT User-Agent: MobilityGateway-2.0.34078 Server: MobilityGateway-2.0.34078 Accept: text/plain Content-Length: 0
Best Regards, Jerry
_______________________________________________ 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-use rs http://www.freeswitch.org
It says SHOULD, not MUST right? The message passing in FS is abstracted and protocol agnostic and we are a b2bua not a proxy in terms of SIP. You are sending a message to 1 UA on FS who is accepting the message and delivering it to the core who is happy to receive messages in any format. Then it's routed back out another sip dialog where it's rejected. It's too late to go tell the sender that is unacceptable because we already happily accepted it (messages are not always passed out to other phones they can easily be directed at other internal resources). We don't know what the content-type means as we are a neutral party in the whole thing so there is not much else we can do but violate this scope issue and break out of our role as a neutral party and translate it to plain text and try again which is not very elegant. If FS was a proxy software, like openser and friends, we would be passing the data between UA in the way you expect but we are not a proxy. Based on the frequency and specific nature of your constant inquiries, and the likelihood that you are offering commercial VoIP services to customers. I suggest you contact us at consulting@freeswitch.org to investigate commercial support options for FreeSWITCH. Even then, I am not sure I could help you besides maybe a param to convert all text/html messages to plain text or some other sad hack. On Fri, Feb 26, 2010 at 1:43 PM, Jerry Richards <jerry.richards@teotech.com>wrote:
I'm not sure I follow your comment. The first device prefers text/html so that's what it normally sets in the initial MESSAGE. Devices that support text/html will not generate this 415 error reply. It's only devices that don't support it that would send the 415 reply, so the issue is that the 415 is not getting passed back to the originator.
Best Regards, Jerry
-----Original Message----- From: Brian West [mailto:brian@freeswitch.org] Sent: Friday, February 26, 2010 11:01 AM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] 415 Unsupported Media Handling
Its really clear here you'll need to say text/plain in the content type their accept header says they only take text/plain.
/b
On Feb 26, 2010, at 12:57 PM, Jerry Richards wrote:
I have two types of devices, one supports text/html MESSAGE content and one that only supports text/plain MESSAGE content. When I send an IM from the first to the second, the second replies with 415 Unsupported Media Type (as shown below). Section 8.1.3.5 of RFC 3261 says the sender should retry using the media type acceptable to the
receiver (in this case: plain/text).
The problem I have is that Freeswitch doesn't pass the error back to the sender (nor does it retry itself using plain/text). So the IM is
lost.
Does anyone see the reason why the error is not being handled correctly?
---------------------------------------------------------------------- -- send 668 bytes to udp/[192.168.72.141]:5062 at 18:43:24.720446:
------------------------------------------------------------------------
MESSAGE sip:5398@192.168.72.141:5062 SIP/2.0 Via: SIP/2.0/UDP 192.168.72.141;rport;branch=z9hG4bKXg6SNUcQa5Kre Max-Forwards: 70 From: "5382 on 141" <sip:5382@192.168.72.141<sip%3A5382@192.168.72.141> ;tag=66661130 To: "5398" <sip:5398@192.168.72.141:5062> Call-ID: a9891a15-9da9-122d-b3ad-003048d7e9f0 CSeq: 127444135 MESSAGE Contact: <sip:mod_sofia@192.168.72.141:5060> User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-32M Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, precondition, path, replaces Content-Type: text/html Content-Length: 63
<font size="2" face="Arial">hello this is Jerry from Teo</font>
---------------------------------------------------------------------- -- recv 459 bytes from udp/[192.168.72.141]:5062 at 18:43:24.728390:
------------------------------------------------------------------------
SIP/2.0 415 Unsupported media type Via: SIP/2.0/UDP 192.168.72.141;rport=5060;branch=z9hG4bKXg6SNUcQa5Kre;received=192.168 .72.14 1 From: "5382 on 141" <sip:5382@192.168.72.141<sip%3A5382@192.168.72.141> ;tag=66661130 To: "5398" <sip:5398@192.168.72.141:5062> Call-ID: a9891a15-9da9-122d-b3ad-003048d7e9f0 CSeq: 127444135 MESSAGE Date: Fri, 26 Feb 2010 18:43:24 GMT User-Agent: MobilityGateway-2.0.34078 Server: MobilityGateway-2.0.34078 Accept: text/plain Content-Length: 0
Best Regards, Jerry
_______________________________________________ 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-use rs 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
-- 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 <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
Sorry again for the late reply on this issue. I think I understand what you're saying. Since IMs are not sent in the context of a dialog (it's simply a send/receive handshake), the b2bua has nothing to tell the originator. I will investigate the possibility of getting the Bria phones to send plain text. Regarding commercial support options for FS, I raised the issue to management here, but I'm not sure what the outcome of that will be (it's not my decision to make). Thanks And Best Regards, Jerry _____ From: Anthony Minessale [mailto:anthony.minessale@gmail.com] Sent: Friday, February 26, 2010 12:56 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] 415 Unsupported Media Handling It says SHOULD, not MUST right? The message passing in FS is abstracted and protocol agnostic and we are a b2bua not a proxy in terms of SIP. You are sending a message to 1 UA on FS who is accepting the message and delivering it to the core who is happy to receive messages in any format. Then it's routed back out another sip dialog where it's rejected. It's too late to go tell the sender that is unacceptable because we already happily accepted it (messages are not always passed out to other phones they can easily be directed at other internal resources). We don't know what the content-type means as we are a neutral party in the whole thing so there is not much else we can do but violate this scope issue and break out of our role as a neutral party and translate it to plain text and try again which is not very elegant. If FS was a proxy software, like openser and friends, we would be passing the data between UA in the way you expect but we are not a proxy. Based on the frequency and specific nature of your constant inquiries, and the likelihood that you are offering commercial VoIP services to customers. I suggest you contact us at consulting@freeswitch.org to investigate commercial support options for FreeSWITCH. Even then, I am not sure I could help you besides maybe a param to convert all text/html messages to plain text or some other sad hack. On Fri, Feb 26, 2010 at 1:43 PM, Jerry Richards <jerry.richards@teotech.com> wrote: I'm not sure I follow your comment. The first device prefers text/html so that's what it normally sets in the initial MESSAGE. Devices that support text/html will not generate this 415 error reply. It's only devices that don't support it that would send the 415 reply, so the issue is that the 415 is not getting passed back to the originator. Best Regards, Jerry -----Original Message----- From: Brian West [mailto:brian@freeswitch.org] Sent: Friday, February 26, 2010 11:01 AM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] 415 Unsupported Media Handling Its really clear here you'll need to say text/plain in the content type their accept header says they only take text/plain. /b On Feb 26, 2010, at 12:57 PM, Jerry Richards wrote:
I have two types of devices, one supports text/html MESSAGE content and one that only supports text/plain MESSAGE content. When I send an IM from the first to the second, the second replies with 415 Unsupported Media Type (as shown below). Section 8.1.3.5 of RFC 3261 says the sender should retry using the media type acceptable to the
receiver (in this case: plain/text).
The problem I have is that Freeswitch doesn't pass the error back to the sender (nor does it retry itself using plain/text). So the IM is
lost.
Does anyone see the reason why the error is not being handled correctly?
---------------------------------------------------------------------- -- send 668 bytes to udp/[192.168.72.141]:5062 at 18:43:24.720446: ------------------------------------------------------------------------ MESSAGE sip:5398@192.168.72.141:5062 SIP/2.0 Via: SIP/2.0/UDP 192.168.72.141;rport;branch=z9hG4bKXg6SNUcQa5Kre Max-Forwards: 70 From: "5382 on 141" <sip:5382@192.168.72.141 <mailto:sip%3A5382@192.168.72.141> >;tag=66661130 To: "5398" <sip:5398@192.168.72.141:5062> Call-ID: a9891a15-9da9-122d-b3ad-003048d7e9f0 CSeq: 127444135 MESSAGE Contact: <sip:mod_sofia@192.168.72.141:5060> User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-32M Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, precondition, path, replaces Content-Type: text/html Content-Length: 63
<font size="2" face="Arial">hello this is Jerry from Teo</font>
---------------------------------------------------------------------- -- recv 459 bytes from udp/[192.168.72.141]:5062 at 18:43:24.728390: ------------------------------------------------------------------------ SIP/2.0 415 Unsupported media type Via: SIP/2.0/UDP 192.168.72.141;rport=5060;branch=z9hG4bKXg6SNUcQa5Kre;received=192.168 .72.14 1 From: "5382 on 141" <sip:5382@192.168.72.141 <mailto:sip%3A5382@192.168.72.141> >;tag=66661130 To: "5398" <sip:5398@192.168.72.141:5062> Call-ID: a9891a15-9da9-122d-b3ad-003048d7e9f0 CSeq: 127444135 MESSAGE Date: Fri, 26 Feb 2010 18:43:24 GMT User-Agent: MobilityGateway-2.0.34078 Server: MobilityGateway-2.0.34078 Accept: text/plain Content-Length: 0
Best Regards, Jerry
_______________________________________________ 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-use rs 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 -- 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 <mailto:MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com <mailto:PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <mailto:sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org <mailto:googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
participants (3)
-
Anthony Minessale
-
Brian West
-
Jerry Richards