Originally created by: lauri.za...@gmail.com
What steps will reproduce the problem?
1. Make Calls fail.
2. SIP INVITE Metod
3.
What is the expected output? What do you see instead?
The Invite are worng acording RFC 3261:
CsipSimple send:
INVITE sip:1002@sip.omninetwork.com.br SIP/2.0.
Via: SIP/2.0/UDP 187.25.9.223:5060;rport;branch=z9hG4bKPjiJ.YggVzv3cny3t6A.0VOF0YRdGCHSSB.
Max-Forwards: 70.
From: <sip:1001@sip.omninetwork.com.br>;tag=CSUbKC9z6l2tf9m38GRtz1FW5Dz4LuIp.
To: sip:1002@sip.omninetwork.com.br.
Contact: <sip:1001@187.25.9.223:5060>.
And should be:
INVITE sip:1002@sip.omninetwork.com.br SIP/2.0.
Via: SIP/2.0/UDP 187.25.9.223:5060;rport;branch=z9hG4bKPjiJ.YggVzv3cny3t6A.0VOF0YRdGCHSSB.
Max-Forwards: 70.
From: <sip:1001@sip.omninetwork.com.br>;tag=CSUbKC9z6l2tf9m38GRtz1FW5Dz4LuIp.
To: sip:<1002@sip.omninetwork.com.br>.
Contact: <sip:1001@187.25.9.223:5060>.
What version of the product are you using? On what operating system?
CsipSimple 0.00-15
Android 2.1 on Samsung Galaxy I5700
Please provide any additional information below.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: r3gis...@gmail.com
I introduced something in latest builds cause some sip servers doesn't support non escaped uris.
I detected that it was the cause of the fact using some sip server you were not able to hangup the call. Sip server was just not able to treat my BYE request.
I quickly searched over the web to have an explanation to my observation, but didn't found.
I'm not a SIP expert, I just use the reliable sip stack pjsip and provide an android interface for that.
However what you get is not what I should send indeed. What I introduced should send you something like that :
<sip:1002@sip.omninetwork.com.br> and not sip:<1002@sip.omninetwork.com.br>
I think (but I'm not sure, correct me if I'm wrong) that <sip:1002@sip.omninetwork.com.br> is valid.
What dialer did you used? The native android dialer, the csipsimple digit dialer or the csipsimple text dialer?
Labels: -Priority-Medium Priority-Critical
Status: Accepted
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: r3gis...@gmail.com
I've just retested all listed cases
All send
To: <sip:xxx@xxx.loc>
In addition just read the rfc on that point:
Page 36 about To header in invite, have a look to the example :
The following is an example of a valid To header field:
To: Carol <sip:carol@chicago.com>
So I guess that <> are valid and besides it solves the problem with some sip provider that probably doesn't parse properly do sip uris comparison :S...
Let me know from where you are able to reproduce the sip:<xxx@xxx> and if possible send me logs (You can use the tool available in help).
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: lauri.za...@gmail.com
Thank!
Now CsipSimple are correct according RFC 3261!
And will be approved for use in us service provider!
If you need more sip trance from us softswitch side, mail me!
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: lauri.za...@gmail.com
Wen a new APK file with this bug fix will be done?
On Sat, Nov 20, 2010 at 7:35 PM, Lauri José Zancanaro Junior <
lauri.zancanaro.junior@gmail.com> wrote:
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: r3gis...@gmail.com
Should be already available on download section of this website : 0.00-15-13 is the last build that already include this fix. (https://code.google.com/p/csipsimple/downloads/detail?name=CSipSimple_0.00-15-13-tls.apk)
If you find any other points that seems strange to you, do not hesitate !! Feedback is really welcome.
I mark this as fixed in next release (since for now on the market version that's not the case, but should be fine in current development version).
I think that I'll release something on the android market in next coming weeks (I'm currently finalizing MESSAGES support).
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: r3gis...@gmail.com
(No comment was entered for this change.)
Status: NextRelease
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: r3gis...@gmail.com
Ok fine !
Just, you should maybe not add sip trace as it (be aware of the fact on issue list it's directly published onto the web and can be indexed by search engines).
That's the reason why I usually advise to directly send me sip logs (as PM on my email address) instead of posting it on the website - and the tricky thing is that now replying on emails on googlecode publish it on the website.
If you have not the delete button on your comment on the website let me know I'll delete it for you ;). Would be safer ;)...
Anyway, thanks a lot for testing and reporting that ! And again if you find anything else do not hesitate.