Hello,
Is it possible to use openSER as TCP <--> UDP convertor?
I have this working to a certain extent.
1) UA -> TCP INV -> openSER -> UDP INV -> Carrier
2) UA <- TCP 200 <- openSER <- UDP 200 <- Carrier
3) UA -> TCP ACK -> openSER -> UDP ACK -> Carrier
Setup transaction works like it should.
My question is about subsequent transactions.
In the 200 from Carrier (2) a parameter of transport=udp is set on the contact header.
Now if the UA is running in an automatic protocol mode ( this would be UA specific ), It honors the transport=udp param and sends a BYE or re-Invite as UDP
4) UA -> UDP BYE -> openSER -> UDP BYE -> Carrier
5) UA <- UDP 200 <- openSER <- UDP 200 <- Carrier
Is there a way to re-write the transport= param in the contact header of the 200 ( msg 2 ) so it says transport=tcp Which would then allow the subsequent request messages from UA to be sent tcp?
Would doing this break the rfc?
Is anyone using openSER to accomplish similar protocol conversion?
Thanks,
T.R.
________________________________
T.R. Missner Director Enterprise VoIP Products trmissner@bandwidth.com 919-439-3575 - Ph 925-888-2997 - Fax
4001 Weston Parkway Cary, NC 27513
________________________________
CONFIDENTIALITY NOTICE This e-mail message, including any attachments from Bandwidth.com - contain information which is CONFIDENTIAL AND/OR LEGALLY PRIVILEGED. The information is intended only for the use of the individual named above and may not be disseminated to any other party without written permission. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, disclosure, distribution, copying or taking of any action in reliance on the contents of this e-mailed information is strictly prohibited. If you have received this transmission in error, please immediately notify info@bandwidth.com, and permanently delete this e-mail and the attachments hereto, if any, and destroy any printout thereof.
Hello,
On 05/19/06 05:49, T.R. Missner wrote:
Hello,
Is it possible to use openSER as TCP <--> UDP convertor?
yes, it is possible. OpenSER can perform transport layer conversion.
I have this working to a certain extent.
UA -> TCP INV -> openSER -> UDP INV -> Carrier
UA <- TCP 200 <- openSER <- UDP 200 <- Carrier
UA -> TCP ACK -> openSER -> UDP ACK -> Carrier
Setup transaction works like it should.
My question is about subsequent transactions.
In the 200 from Carrier (2) a parameter of transport=udp is set on the contact header.
Now if the UA is running in an automatic protocol mode ( this would be UA specific ), It honors the transport=udp param and sends a BYE or re-Invite as UDP
The ua has to honor the Record-Route from 200OK, which would specify the TCP transport. The proxy is the one which has to honor the Contact header, being the one which delivers the message to that hop.
Cheers, Daniel
UA -> UDP BYE -> openSER -> UDP BYE -> Carrier
UA <- UDP 200 <- openSER <- UDP 200 <- Carrier
Is there a way to re-write the transport= param in the contact header of the 200 ( msg 2 ) so it says transport=tcp Which would then allow the subsequent request messages from UA to be sent tcp?
Would doing this break the rfc?
Is anyone using openSER to accomplish similar protocol conversion?
Thanks,
T.R.
*T.R. Missner* /Director Enterprise VoIP Products/ trmissner@bandwidth.com mailto:trmissner@bandwidth.com 919-439-3575 - Ph 925-888-2997 - Fax
4001 Weston Parkway Cary, NC 27513
CONFIDENTIALITY NOTICE This e-mail message, including any attachments from Bandwidth.com - contain information which is CONFIDENTIAL AND/OR LEGALLY PRIVILEGED. The information is intended only for the use of the individual named above and may not be disseminated to any other party without written permission. If you are not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, disclosure, distribution, copying or taking of any action in reliance on the contents of this e-mailed information is strictly prohibited. If you have received this transmission in error, please immediately notify info@bandwidth.com, and permanently delete this e-mail and the attachments hereto, if any, and destroy any printout thereof.
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
-
Daniel-Constantin Mierla -
T.R. Missner