7 Mar
2007
7 Mar
'07
3:41 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I try to use WeSIP C2C with UACs registered to freeswitch. freeswitch
never answeres the INVITEs for caller (that INVITE with no SDP and
from=to=caller's sip address). So my question is, is it because
freeswitch maybe doesn't support rfc 3725? If so, is there any C2C
proven SIP-PBX I can use instead?
Helmut
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF7s8L4tZeNddg3dwRArGjAKCRJ+Kqi4FqdE2J9S/Q6t8L3VEVzwCgncCc
G2rxVs9s3fqs+XgUXnsefRs=
=RqW7
-----END PGP SIGNATURE-----
7 Mar
7 Mar
5:13 p.m.
Hi,
asterisk supports it. I've just tested
Regards
Gines
El 07/03/2007, a las 15:41, Helmut Kuper escribió:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I try to use WeSIP C2C with UACs registered to freeswitch. freeswitch
never answeres the INVITEs for caller (that INVITE with no SDP and
from=to=caller's sip address). So my question is, is it because
freeswitch maybe doesn't support rfc 3725? If so, is there any C2C
proven SIP-PBX I can use instead?
Helmut
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF7s8L4tZeNddg3dwRArGjAKCRJ+Kqi4FqdE2J9S/Q6t8L3VEVzwCgncCc
G2rxVs9s3fqs+XgUXnsefRs=
=RqW7
-----END PGP SIGNATURE-----
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
21 Mar
21 Mar
10:42 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I tested c2c now with openser. My phone is registered to openser. When I
start a call via c2c app, my phone rings but as soon as openser sends
back the ringing message, wesip throws this to console:
hk@vm-en-test0:~/wesip/wesip$ java.text.ParseException: ERROR: bad index
for start of uri:0<7
at com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.From.<init>(From.java:51)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:254)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Unknown Source)
java.text.ParseException: ERROR: bad index for start of uri:0<13
at com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.To.<init>(To.java:54)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:251)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Unknown Source)
java.lang.StringIndexOutOfBoundsException: String index out of range: -58
at java.lang.String.checkBounds(Unknown Source)
at java.lang.String.<init>(Unknown Source)
at com.voztele.javax.sip.header.CallID.<init>(CallID.java:34)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:260)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Unknown Source)
Exception in thread "ExpressMChannel[4]" java.lang.NullPointerException
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:143)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Unknown Source)
any ideas? Is is an error in c2c app or is ringing message not allowed
to send to c2c app?
regards
helmut
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGAP4D4tZeNddg3dwRAp65AKCKa9QnUMLh5By8ZdgIKtaYCoCfPACeMJ1N
RlPhqiZYxecY0HH5uObyTE4=
=nTar
-----END PGP SIGNATURE-----
12:08 p.m.
Hello Helmut,
Can you send the message/From header/URI that caused the exception ?
It'll help debug the error
Thanks for you interest :)
Elias Baixas
Helmut Kuper wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I tested c2c now with openser. My phone is registered to openser. When I
start a call via c2c app, my phone rings but as soon as openser sends
back the ringing message, wesip throws this to console:
hk@vm-en-test0:~/wesip/wesip$ java.text.ParseException: ERROR: bad index
for start of uri:0<7
at com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.From.<init>(From.java:51)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:254)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Unknown Source)
java.text.ParseException: ERROR: bad index for start of uri:0<13
at com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.To.<init>(To.java:54)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:251)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Unknown Source)
java.lang.StringIndexOutOfBoundsException: String index out of range: -58
at java.lang.String.checkBounds(Unknown Source)
at java.lang.String.<init>(Unknown Source)
at com.voztele.javax.sip.header.CallID.<init>(CallID.java:34)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:260)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Unknown Source)
Exception in thread "ExpressMChannel[4]" java.lang.NullPointerException
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:143)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Unknown Source)
any ideas? Is is an error in c2c app or is ringing message not allowed
to send to c2c app?
regards
helmut
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGAP4D4tZeNddg3dwRAp65AKCKa9QnUMLh5By8ZdgIKtaYCoCfPACeMJ1N
RlPhqiZYxecY0HH5uObyTE4=
=nTar
-----END PGP SIGNATURE-----
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
12:13 p.m.
Hi again,
Actually I've just seen there are couple of exceptions, all related to
the decodification of the binary encoding of the messages.
I guess this might be related to the new binary protocol format.
If you're using a recent openser version, then you need to download the
new version of WeSIP from www.WeSIP.eu,
the binary protocol has changed and that's what is making all these errors.
best regards,
Elias Baixas
Elias Baixas wrote:
Hello Helmut,
Can you send the message/From header/URI that caused the exception ?
It'll help debug the error
Thanks for you interest :)
Elias Baixas
Helmut Kuper wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I tested c2c now with openser. My phone is registered to openser. When I
start a call via c2c app, my phone rings but as soon as openser sends
back the ringing message, wesip throws this to console:
hk@vm-en-test0:~/wesip/wesip$ java.text.ParseException: ERROR: bad index
for start of uri:0<7
at com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.From.<init>(From.java:51)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:254)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Unknown Source)
java.text.ParseException: ERROR: bad index for start of uri:0<13
at com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.To.<init>(To.java:54)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:251)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Unknown Source)
java.lang.StringIndexOutOfBoundsException: String index out of range:
-58
at java.lang.String.checkBounds(Unknown Source)
at java.lang.String.<init>(Unknown Source)
at com.voztele.javax.sip.header.CallID.<init>(CallID.java:34)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:260)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Unknown Source)
Exception in thread "ExpressMChannel[4]" java.lang.NullPointerException
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:143)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Unknown Source)
any ideas? Is is an error in c2c app or is ringing message not allowed
to send to c2c app?
regards
helmut
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGAP4D4tZeNddg3dwRAp65AKCKa9QnUMLh5By8ZdgIKtaYCoCfPACeMJ1N
RlPhqiZYxecY0HH5uObyTE4=
=nTar
-----END PGP SIGNATURE-----
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
2 Apr
2 Apr
10:04 a.m.
I too am having "bad index" errors. This is a different setup, but is
there a way to turn on full debug, to determine what specifically is
getting rejected?
I have: openser1 (1.2.0 release ) ( seas proxy) 192.168.0.110 port 5061
I have: openser2 (1.2.0 release ) ( registrar, proxy ) 192.168.0.110 port 5060
I have 5000 X-lite : 192.168.0.112 port 5060
I have 5001 sipura : 192.168.0.104 port 5061
wesip version = beta 0.2.
setup is :
caller( 5000) openser2 openser1 callee (5001)
<------INVITE(nosdp)
<------------INVITE(no sdp)
------------>180 Ringing
-------->180 Ringing
------------>200 ok(5000's sdp)
--------> 200 OK(5000's sdp)
------------>200 ok(5000's sdp) ( this message is retransmitted )
As far as I can tell there is something in the 200 ok from openser2
that wesip doesn't like.
Here's the 200 OK packet:
U 192.168.0.112:5060 -> 192.168.0.110:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.0.110;branch=z9hG4bKc487.36c6a7f1.0.
Via: SIP/2.0/UDP 192.168.0.110:5061;branch=z9hG4bKc487.f8ab40c.0.
Record-Route:
<sip:192.168.0.110;lr;ftag=B712F1B2E6240BA0E679ED5FD82D4DCC;did=4c8.8e50c39>.
Contact: <sip:5000@192.168.0.112:5060>.
To: <sip:5000@192.168.0.110>;tag=f3783b63.
From: <sip:5000@192.168.0.110>;tag=B712F1B2E6240BA0E679ED5FD82D4DCC.
Call-ID: F309951C9E79AA2051EAF1E9B58D6EFC(a)192.168.0.110.
CSeq: 1 INVITE.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO.
Content-Type: application/sdp.
User-Agent: X-Lite release 1006e stamp 34025.
Content-Length: 184.
.
v=0.
o=- 4 2 IN IP4 192.168.0.112.
s=CounterPath X-Lite 3.0.
c=IN IP4 192.168.0.112.
t=0 0.
m=audio 5062 RTP/AVP 0 101.
a=fmtp:101 0-15.
a=rtpmap:101 telephone-event/8000.
a=sendrecv.
Using sample c2c, I'm getting :
[HttpProcessor[5080][4]] - Transport: udp
ExpressMessageChannel [HttpProcessor[5080][4]] - Creating Express
message channel 192.168.0.110/5060
ExpressMessageChannel [HttpProcessor[5080][4]] - setting spiral=false
SIPClientTransaction [HttpProcessor[5080][4]] - actionID = 1533381624
SipRequest [HttpProcessor[5080][4]] - >>>>>>>>> Sending
Request >>>>>>>>>
INVITE sip:5000@192.168.0.110 SIP/2.0
Call-ID: AF0B0A41163B94EBA3E3BEA9E4656761(a)192.168.0.110
CSeq: 1 INVITE
From: <sip:5000@192.168.0.110>;tag=5C52C7DB87B8234E5F2C9BF63AC7DA6D
To: <sip:5000@192.168.0.110>
Max-Forwards: 70
Contact: <sip:192.168.0.110:5061;transport=udp>
Via: SIP/2.0/UDP 192.168.0.110:5061;branch=z9hG4bK1533381624
Content-Length: 0
ExpressMessageChannel [HttpProcessor[5080][4]] - sending with spiral=false
ActionRouter$ActionSender [ActionSender] - Writing 375 bytes
into Action Socket
SeasMessageEvent [SeasRouter] - New message received, from
192.168.0.110:5060 to 192.168.0.110:5061 over UDP
SeasTransactionEvent [SeasRouter] - hash_index = 659,label=698262579 flags=0
SeasReplyEvent [SeasRouter] - Response Event: uac_id:1533381624 code:180
ExpressMessageChannel [ExpressMChannel[0]] - peerAddress = 192.168.0.110/5060
java.text.ParseException: ERROR: bad index for start of uri:0<8
at com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.To.<init>(To.java:54)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:251)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Thread.java:595)
java.text.ParseException: ERROR: bad index for start of uri:0<7
at com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.From.<init>(From.java:51)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:254)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Thread.java:595)
SeasMessageEvent [ExpressMChannel[0]] - ERROR parsing
a SEAS message event!!!
java.lang.StringIndexOutOfBoundsException: String index out of
range: -58
1:42 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
as far as I know, this seems to be a problem in wesip beta 0.1.3 (0.2
beta isn't out yet, isn't it?) and openser 1.2. Developers say, that the
binary format betwen openser 1.2 and wesip 0.1.3 has changed a bit, but
that's not realy sure.
If u ask me, it's not a freeswitch bug.
regards
Helmut
Andy Pyles schrieb:
I too am having "bad index" errors. This is
a different setup, but is
there a way to turn on full debug, to determine what specifically is
getting rejected?
I have: openser1 (1.2.0 release ) ( seas proxy) 192.168.0.110 port 5061
I have: openser2 (1.2.0 release ) ( registrar, proxy ) 192.168.0.110
port 5060
I have 5000 X-lite : 192.168.0.112 port 5060
I have 5001 sipura : 192.168.0.104 port 5061
wesip version = beta 0.2.
setup is :
caller( 5000) openser2 openser1 callee (5001)
<------INVITE(nosdp)
<------------INVITE(no sdp)
------------>180 Ringing
-------->180 Ringing
------------>200 ok(5000's sdp)
--------> 200 OK(5000's sdp)
------------>200 ok(5000's sdp) ( this message is retransmitted )
As far as I can tell there is something in the 200 ok from openser2
that wesip doesn't like.
Here's the 200 OK packet:
U 192.168.0.112:5060 -> 192.168.0.110:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.0.110;branch=z9hG4bKc487.36c6a7f1.0.
Via: SIP/2.0/UDP 192.168.0.110:5061;branch=z9hG4bKc487.f8ab40c.0.
Record-Route:
<sip:192.168.0.110;lr;ftag=B712F1B2E6240BA0E679ED5FD82D4DCC;did=4c8.8e50c39>.
Contact: <sip:5000@192.168.0.112:5060>.
To: <sip:5000@192.168.0.110>;tag=f3783b63.
From: <sip:5000@192.168.0.110>;tag=B712F1B2E6240BA0E679ED5FD82D4DCC.
Call-ID: F309951C9E79AA2051EAF1E9B58D6EFC(a)192.168.0.110.
CSeq: 1 INVITE.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO.
Content-Type: application/sdp.
User-Agent: X-Lite release 1006e stamp 34025.
Content-Length: 184.
.
v=0.
o=- 4 2 IN IP4 192.168.0.112.
s=CounterPath X-Lite 3.0.
c=IN IP4 192.168.0.112.
t=0 0.
m=audio 5062 RTP/AVP 0 101.
a=fmtp:101 0-15.
a=rtpmap:101 telephone-event/8000.
a=sendrecv.
Using sample c2c, I'm getting :
[HttpProcessor[5080][4]] - Transport: udp
ExpressMessageChannel [HttpProcessor[5080][4]] - Creating Express
message channel 192.168.0.110/5060
ExpressMessageChannel [HttpProcessor[5080][4]] - setting spiral=false
SIPClientTransaction [HttpProcessor[5080][4]] - actionID = 1533381624
SipRequest [HttpProcessor[5080][4]] - >>>>>>>>> Sending
Request
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGEOwq4tZeNddg3dwRAi5sAJ4iN54Rk93fNnXWTohl7uRW13Z1xACdFLWY
bKjIvdPp52buAXlvg0WIhlM=
=XMXU
-----END PGP SIGNATURE-----
>>>>>>>>
INVITE
sip:5000@192.168.0.110 SIP/2.0
Call-ID: AF0B0A41163B94EBA3E3BEA9E4656761(a)192.168.0.110
CSeq: 1 INVITE
From: <sip:5000@192.168.0.110>;tag=5C52C7DB87B8234E5F2C9BF63AC7DA6D
To: <sip:5000@192.168.0.110>
Max-Forwards: 70
Contact: <sip:192.168.0.110:5061;transport=udp>
Via: SIP/2.0/UDP 192.168.0.110:5061;branch=z9hG4bK1533381624
Content-Length: 0
ExpressMessageChannel [HttpProcessor[5080][4]] - sending with
spiral=false
ActionRouter$ActionSender [ActionSender] - Writing 375 bytes
into Action Socket
SeasMessageEvent [SeasRouter] - New message received, from
192.168.0.110:5060 to 192.168.0.110:5061 over UDP
SeasTransactionEvent [SeasRouter] - hash_index = 659,label=698262579
flags=0
SeasReplyEvent [SeasRouter] - Response Event: uac_id:1533381624 code:180
ExpressMessageChannel [ExpressMChannel[0]] - peerAddress =
192.168.0.110/5060
java.text.ParseException: ERROR: bad index for start of uri:0<8
at com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.To.<init>(To.java:54)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:251)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Thread.java:595)
java.text.ParseException: ERROR: bad index for start of uri:0<7
at
com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.From.<init>(From.java:51)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:254)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Thread.java:595)
SeasMessageEvent [ExpressMChannel[0]] - ERROR parsing
a SEAS message event!!!
java.lang.StringIndexOutOfBoundsException: String index out of
range: -58
4:42 p.m.
HI Helmut,
In this case I'm not using freeswitch. This is just openser 1.2 and
wesip beta 0.2.
Andy
On 4/2/07, Helmut Kuper <helmut.kuper(a)ewetel.de> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
as far as I know, this seems to be a problem in wesip beta 0.1.3 (0.2
beta isn't out yet, isn't it?) and openser 1.2. Developers say, that the
binary format betwen openser 1.2 and wesip 0.1.3 has changed a bit, but
that's not realy sure.
If u ask me, it's not a freeswitch bug.
regards
Helmut
Andy Pyles schrieb:
I too am having "bad index" errors.
This is a different setup, but is
there a way to turn on full debug, to determine what specifically is
getting rejected?
I have: openser1 (1.2.0 release ) ( seas proxy) 192.168.0.110 port 5061
I have: openser2 (1.2.0 release ) ( registrar, proxy ) 192.168.0.110
port 5060
I have 5000 X-lite : 192.168.0.112 port 5060
I have 5001 sipura : 192.168.0.104 port 5061
wesip version = beta 0.2.
setup is :
caller( 5000) openser2 openser1 callee (5001)
<------INVITE(nosdp)
<------------INVITE(no sdp)
------------>180 Ringing
-------->180 Ringing
------------>200 ok(5000's sdp)
--------> 200 OK(5000's sdp)
------------>200 ok(5000's sdp) ( this message is retransmitted )
As far as I can tell there is something in the 200 ok from openser2
that wesip doesn't like.
Here's the 200 OK packet:
U 192.168.0.112:5060 -> 192.168.0.110:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.0.110;branch=z9hG4bKc487.36c6a7f1.0.
Via: SIP/2.0/UDP 192.168.0.110:5061;branch=z9hG4bKc487.f8ab40c.0.
Record-Route:
<sip:192.168.0.110;lr;ftag=B712F1B2E6240BA0E679ED5FD82D4DCC;did=4c8.8e50c39>.
Contact: <sip:5000@192.168.0.112:5060>.
To: <sip:5000@192.168.0.110>;tag=f3783b63.
From: <sip:5000@192.168.0.110>;tag=B712F1B2E6240BA0E679ED5FD82D4DCC.
Call-ID: F309951C9E79AA2051EAF1E9B58D6EFC(a)192.168.0.110.
CSeq: 1 INVITE.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO.
Content-Type: application/sdp.
User-Agent: X-Lite release 1006e stamp 34025.
Content-Length: 184.
.
v=0.
o=- 4 2 IN IP4 192.168.0.112.
s=CounterPath X-Lite 3.0.
c=IN IP4 192.168.0.112.
t=0 0.
m=audio 5062 RTP/AVP 0 101.
a=fmtp:101 0-15.
a=rtpmap:101 telephone-event/8000.
a=sendrecv.
Using sample c2c, I'm getting :
[HttpProcessor[5080][4]] - Transport: udp
ExpressMessageChannel [HttpProcessor[5080][4]] - Creating Express
message channel 192.168.0.110/5060
ExpressMessageChannel [HttpProcessor[5080][4]] - setting spiral=false
SIPClientTransaction [HttpProcessor[5080][4]] - actionID = 1533381624
SipRequest [HttpProcessor[5080][4]] - >>>>>>>>> Sending
Request
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGEOwq4tZeNddg3dwRAi5sAJ4iN54Rk93fNnXWTohl7uRW13Z1xACdFLWY
bKjIvdPp52buAXlvg0WIhlM=
=XMXU
-----END PGP SIGNATURE-----
>>>>>>>>
INVITE
sip:5000@192.168.0.110 SIP/2.0
Call-ID: AF0B0A41163B94EBA3E3BEA9E4656761(a)192.168.0.110
CSeq: 1 INVITE
From: <sip:5000@192.168.0.110>;tag=5C52C7DB87B8234E5F2C9BF63AC7DA6D
To: <sip:5000@192.168.0.110>
Max-Forwards: 70
Contact: <sip:192.168.0.110:5061;transport=udp>
Via: SIP/2.0/UDP 192.168.0.110:5061;branch=z9hG4bK1533381624
Content-Length: 0
ExpressMessageChannel [HttpProcessor[5080][4]] - sending with
spiral=false
ActionRouter$ActionSender [ActionSender] - Writing 375 bytes
into Action Socket
SeasMessageEvent [SeasRouter] - New message received, from
192.168.0.110:5060 to 192.168.0.110:5061 over UDP
SeasTransactionEvent [SeasRouter] - hash_index = 659,label=698262579
flags=0
SeasReplyEvent [SeasRouter] - Response Event: uac_id:1533381624 code:180
ExpressMessageChannel [ExpressMChannel[0]] - peerAddress =
192.168.0.110/5060
java.text.ParseException: ERROR: bad index for start of uri:0<8
at com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.To.<init>(To.java:54)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:251)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Thread.java:595)
java.text.ParseException: ERROR: bad index for start of uri:0<7
at
com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.From.<init>(From.java:51)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:254)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Thread.java:595)
SeasMessageEvent [ExpressMChannel[0]] - ERROR parsing
a SEAS message event!!!
java.lang.StringIndexOutOfBoundsException: String index out of
range: -58
6:14 p.m.
FYI: The latest version released today seems to resolve the problem.
On 4/2/07, Andy Pyles <andy.pyles(a)gmail.com> wrote:
HI Helmut,
In this case I'm not using freeswitch. This is just openser 1.2 and
wesip beta 0.2.
Andy
On 4/2/07, Helmut Kuper <helmut.kuper(a)ewetel.de> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
as far as I know, this seems to be a problem in wesip beta 0.1.3 (0.2
beta isn't out yet, isn't it?) and openser 1.2. Developers say, that the
binary format betwen openser 1.2 and wesip 0.1.3 has changed a bit, but
that's not realy sure.
If u ask me, it's not a freeswitch bug.
regards
Helmut
Andy Pyles schrieb:
I too am having "bad index" errors.
This is a different setup, but is
there a way to turn on full debug, to determine what specifically is
getting rejected?
I have: openser1 (1.2.0 release ) ( seas proxy) 192.168.0.110 port 5061
I have: openser2 (1.2.0 release ) ( registrar, proxy ) 192.168.0.110
port 5060
I have 5000 X-lite : 192.168.0.112 port 5060
I have 5001 sipura : 192.168.0.104 port 5061
wesip version = beta 0.2.
setup is :
caller( 5000) openser2 openser1 callee (5001)
<------INVITE(nosdp)
<------------INVITE(no sdp)
------------>180 Ringing
-------->180 Ringing
------------>200 ok(5000's sdp)
--------> 200 OK(5000's sdp)
------------>200 ok(5000's sdp) ( this message is retransmitted )
As far as I can tell there is something in the 200 ok from openser2
that wesip doesn't like.
Here's the 200 OK packet:
U 192.168.0.112:5060 -> 192.168.0.110:5060
SIP/2.0 200 OK.
Via: SIP/2.0/UDP 192.168.0.110;branch=z9hG4bKc487.36c6a7f1.0.
Via: SIP/2.0/UDP 192.168.0.110:5061;branch=z9hG4bKc487.f8ab40c.0.
Record-Route:
<sip:192.168.0.110;lr;ftag=B712F1B2E6240BA0E679ED5FD82D4DCC;did=4c8.8e50c39>.
Contact: <sip:5000@192.168.0.112:5060>.
To: <sip:5000@192.168.0.110>;tag=f3783b63.
From: <sip:5000@192.168.0.110>;tag=B712F1B2E6240BA0E679ED5FD82D4DCC.
Call-ID: F309951C9E79AA2051EAF1E9B58D6EFC(a)192.168.0.110.
CSeq: 1 INVITE.
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
SUBSCRIBE, INFO.
Content-Type: application/sdp.
User-Agent: X-Lite release 1006e stamp 34025.
Content-Length: 184.
.
v=0.
o=- 4 2 IN IP4 192.168.0.112.
s=CounterPath X-Lite 3.0.
c=IN IP4 192.168.0.112.
t=0 0.
m=audio 5062 RTP/AVP 0 101.
a=fmtp:101 0-15.
a=rtpmap:101 telephone-event/8000.
a=sendrecv.
Using sample c2c, I'm getting :
[HttpProcessor[5080][4]] - Transport: udp
ExpressMessageChannel [HttpProcessor[5080][4]] - Creating Express
message channel 192.168.0.110/5060
ExpressMessageChannel [HttpProcessor[5080][4]] - setting spiral=false
SIPClientTransaction [HttpProcessor[5080][4]] - actionID = 1533381624
SipRequest [HttpProcessor[5080][4]] - >>>>>>>>> Sending
Request
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGEOwq4tZeNddg3dwRAi5sAJ4iN54Rk93fNnXWTohl7uRW13Z1xACdFLWY
bKjIvdPp52buAXlvg0WIhlM=
=XMXU
-----END PGP SIGNATURE-----
>>>>>>>>
INVITE
sip:5000@192.168.0.110 SIP/2.0
Call-ID: AF0B0A41163B94EBA3E3BEA9E4656761(a)192.168.0.110
CSeq: 1 INVITE
From: <sip:5000@192.168.0.110>;tag=5C52C7DB87B8234E5F2C9BF63AC7DA6D
To: <sip:5000@192.168.0.110>
Max-Forwards: 70
Contact: <sip:192.168.0.110:5061;transport=udp>
Via: SIP/2.0/UDP 192.168.0.110:5061;branch=z9hG4bK1533381624
Content-Length: 0
ExpressMessageChannel [HttpProcessor[5080][4]] - sending with
spiral=false
ActionRouter$ActionSender [ActionSender] - Writing 375 bytes
into Action Socket
SeasMessageEvent [SeasRouter] - New message received, from
192.168.0.110:5060 to 192.168.0.110:5061 over UDP
SeasTransactionEvent [SeasRouter] - hash_index = 659,label=698262579
flags=0
SeasReplyEvent [SeasRouter] - Response Event: uac_id:1533381624 code:180
ExpressMessageChannel [ExpressMChannel[0]] - peerAddress =
192.168.0.110/5060
java.text.ParseException: ERROR: bad index for start of uri:0<8
at com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.To.<init>(To.java:54)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:251)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Thread.java:595)
java.text.ParseException: ERROR: bad index for start of uri:0<7
at
com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
at com.voztele.javax.sip.header.From.<init>(From.java:51)
at
com.voztele.javax.sip.message.SIPMessage.createSIPHeader(SIPMessage.java:254)
at
com.voztele.javax.sip.message.SIPMessage.addSIPHeader(SIPMessage.java:230)
at
com.voztele.javax.sip.message.SIPMessage.<init>(SIPMessage.java:225)
at
com.voztele.javax.sip.message.SIPResponse.<init>(SIPResponse.java:338)
at
com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage(StringMsgParser.java:357)
at
com.voztele.seas.SeasMessageEvent.getSIPMessage(SeasMessageEvent.java:136)
at
com.voztele.seas.SeasTransactionEvent.getSIPMessage(SeasTransactionEvent.java:70)
at
com.voztele.seas.SeasReplyEvent.getSIPMessage(SeasReplyEvent.java:37)
at
com.voztele.seas.ExpressMessageChannel.run(ExpressMessageChannel.java:301)
at java.lang.Thread.run(Thread.java:595)
SeasMessageEvent [ExpressMChannel[0]] - ERROR parsing
a SEAS message event!!!
java.lang.StringIndexOutOfBoundsException: String index out of
range: -58
6:28 p.m.
Hello everybody,
We are sorry for this inconvenience, in fact we just realized the
WeSIP version on wesip.eu wasn't in sync with OpenSER-latest (1.2.0).
In march 1st, a new version of the WeSIP binary protocol was
released, which worked against OpenSER 1.2.0. Then versions released
later in march (5th, 28th, etc) were mistakenly using the old
protocol (for OpenSER 1.1).
A new version (0.1.4) has been uploaded to the server that works with
OpenSER 1.2.
again, sorry for inconvenience and thanks for your support.
eager to eat more bugs,
Elias Baixas
El 02/04/2007, a las 18:14, Andy Pyles escribió:
FYI: The latest version released today seems to
resolve the problem.
On 4/2/07, Andy Pyles <andy.pyles(a)gmail.com> wrote:
HI Helmut,
In this case I'm not using freeswitch. This is just openser 1.2 and
wesip beta 0.2.
Andy
On 4/2/07, Helmut Kuper <helmut.kuper(a)ewetel.de> wrote:
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
as far as I know, this seems to be a problem in wesip beta 0.1.3
(0.2
beta isn't out yet, isn't it?) and
openser 1.2. Developers say,
that the
binary format betwen openser 1.2 and wesip 0.1.3
has changed a
bit, but
that's not realy sure.
If u ask me, it's not a freeswitch bug.
regards
Helmut
Andy Pyles schrieb:
> I too am having "bad index" errors. This is a different setup,
but is
> there a way to turn on full debug, to
determine what
specifically is
> getting rejected?
>
>
> I have: openser1 (1.2.0 release ) ( seas proxy) 192.168.0.110
port 5061
> I have: openser2 (1.2.0 release ) (
registrar, proxy )
192.168.0.110
> port 5060
> I have 5000 X-lite : 192.168.0.112 port 5060
> I have 5001 sipura : 192.168.0.104 port 5061
> wesip version = beta 0.2.
>
> setup is :
>
> caller( 5000) openser2 openser1 callee
(5001)
>
<------INVITE(nosdp)
> <------------INVITE(no sdp)
> ------------>180 Ringing
> -------->180 Ringing
> ------------>200 ok(5000's sdp)
> --------> 200 OK(5000's sdp)
> ------------>200 ok(5000's sdp) ( this message is
retransmitted )
>
> As far as I can tell there is something in the 200 ok from
openser2
> that wesip doesn't like.
>
> Here's the 200 OK packet:
>
>
> U 192.168.0.112:5060 -> 192.168.0.110:5060
> SIP/2.0 200 OK.
> Via: SIP/2.0/UDP 192.168.0.110;branch=z9hG4bKc487.36c6a7f1.0.
> Via: SIP/2.0/UDP 192.168.0.110:5061;branch=z9hG4bKc487.f8ab40c.0.
> Record-Route:
> <sip:
192.168.0.110;lr;ftag=B712F1B2E6240BA0E679ED5FD82D4DCC;did=4c8.8e50c3
9>.
>
> Contact: <sip:5000@192.168.0.112:5060>.
> To: <sip:5000@192.168.0.110>;tag=f3783b63.
> From: <sip:
5000(a)192.168.0.110>;tag=B712F1B2E6240BA0E679ED5FD82D4DCCDCC.
> Call-ID:
F309951C9E79AA2051EAF1E9B58D6EFC(a)192.168.0.110.
> CSeq: 1 INVITE.
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE,
> SUBSCRIBE, INFO.
> Content-Type: application/sdp.
> User-Agent: X-Lite release 1006e stamp 34025.
> Content-Length: 184.
> .
> v=0.
> o=- 4 2 IN IP4 192.168.0.112.
> s=CounterPath X-Lite 3.0.
> c=IN IP4 192.168.0.112.
> t=0 0.
> m=audio 5062 RTP/AVP 0 101.
> a=fmtp:101 0-15.
> a=rtpmap:101 telephone-event/8000.
> a=sendrecv.
>
>
>
> Using sample c2c, I'm getting :
>
> [HttpProcessor[5080][4]] - Transport: udp
> ExpressMessageChannel [HttpProcessor[5080][4]] - Creating
Express
> message channel 192.168.0.110/5060
> ExpressMessageChannel [HttpProcessor[5080][4]] - setting
spiral=false
> SIPClientTransaction
[HttpProcessor[5080][4]] - actionID =
1533381624
> SipRequest [HttpProcessor[5080][4]] -
>>>>>>>>> Sending
Request
>>>>>>>>>>
> INVITE sip:5000@192.168.0.110 SIP/2.0
> Call-ID: AF0B0A41163B94EBA3E3BEA9E4656761(a)192.168.0.110
> CSeq: 1 INVITE
> From: <sip:
5000(a)192.168.0.110>;tag=5C52C7DB87B8234E5F2C9BF63AC7DA6D
> To: <sip:5000@192.168.0.110>
> Max-Forwards: 70
> Contact: <sip:192.168.0.110:5061;transport=udp>
> Via: SIP/2.0/UDP 192.168.0.110:5061;branch=z9hG4bK1533381624
> Content-Length: 0
>
>
>
> ExpressMessageChannel [HttpProcessor[5080][4]] - sending with
> spiral=false
> ActionRouter$ActionSender [ActionSender] - Writing 375
bytes
> into Action Socket
> SeasMessageEvent [SeasRouter] - New message received,
from
> 192.168.0.110:5060 to 192.168.0.110:5061
over UDP
> SeasTransactionEvent [SeasRouter] - hash_index =
659,label=698262579
> flags=0
> SeasReplyEvent [SeasRouter] - Response Event: uac_id:
1533381624 code:180
> ExpressMessageChannel
[ExpressMChannel[0]] - peerAddress =
> 192.168.0.110/5060
> java.text.ParseException: ERROR: bad index for start of uri:0<8
> at com.voztele.javax.sip.address.SipUri.<init>
(SipUri.java:85)
> at
com.voztele.javax.sip.header.To.<init>
(To.java:54)
> at
> com.voztele.javax.sip.message.SIPMessage.createSIPHeader
(SIPMessage.java:251)
>
> at
> com.voztele.javax.sip.message.SIPMessage.addSIPHeader
(SIPMessage.java:230)
> at
> com.voztele.javax.sip.message.SIPMessage.<init>
(SIPMessage.java:225)
> at
> com.voztele.javax.sip.message.SIPResponse.<init>
(SIPResponse.java:338)
> at
> com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage
(StringMsgParser.java:357)
>
> at
> com.voztele.seas.SeasMessageEvent.getSIPMessage
(SeasMessageEvent.java:136)
> at
> com.voztele.seas.SeasTransactionEvent.getSIPMessage
(SeasTransactionEvent.java:70)
>
> at
> com.voztele.seas.SeasReplyEvent.getSIPMessage
(SeasReplyEvent.java:37)
> at
> com.voztele.seas.ExpressMessageChannel.run
(ExpressMessageChannel.java:301)
> at
java.lang.Thread.run(Thread.java:595)
> java.text.ParseException: ERROR: bad index for start of
uri:0<7
> at
> com.voztele.javax.sip.address.SipUri.<init>(SipUri.java:85)
> at com.voztele.javax.sip.header.From.<init>
(From.java:51)
> at
> com.voztele.javax.sip.message.SIPMessage.createSIPHeader
(SIPMessage.java:254)
>
> at
> com.voztele.javax.sip.message.SIPMessage.addSIPHeader
(SIPMessage.java:230)
> at
> com.voztele.javax.sip.message.SIPMessage.<init>
(SIPMessage.java:225)
> at
> com.voztele.javax.sip.message.SIPResponse.<init>
(SIPResponse.java:338)
> at
> com.voztele.javax.sip.parser.StringMsgParser.parseSERMessage
(StringMsgParser.java:357)
>
> at
> com.voztele.seas.SeasMessageEvent.getSIPMessage
(SeasMessageEvent.java:136)
> at
> com.voztele.seas.SeasTransactionEvent.getSIPMessage
(SeasTransactionEvent.java:70)
>
> at
> com.voztele.seas.SeasReplyEvent.getSIPMessage
(SeasReplyEvent.java:37)
> at
> com.voztele.seas.ExpressMessageChannel.run
(ExpressMessageChannel.java:301)
> at
java.lang.Thread.run(Thread.java:595)
> SeasMessageEvent [ExpressMChannel[0]] - ERROR
parsing
> a SEAS message event!!!
> java.lang.StringIndexOutOfBoundsException: String index
out of
range:
-58
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGEOwq4tZeNddg3dwRAi5sAJ4iN54Rk93fNnXWTohl7uRW13Z1xACdFLWY
bKjIvdPp52buAXlvg0WIhlM=
=XMXU
-----END PGP SIGNATURE-----
6241
days inactive
6267
days old
9 comments
4 participants
participants (4)
-
Andy Pyles -
Elias Baixas -
Ginés Gómez -
Helmut Kuper