boghe
boghe copied to clipboard
DoubangoTelecom
Boghe parse errors and invalid content errors
Boghe is setup for SIMPLE Presence (no XCAP and no RLS)
It is failing to parse the SIP response and notify messages from the client.
This is a client that I am writing so it's possible that I am not including
something or formatting something in the message correctly.
For now the client uses the same TCP connection to send back the Responses as
well as the Notifies.
From the boghe log:
2012-11-21 09:40:28,135 ERROR [9] BogheCore.Services.Impl.SipService:0 -
***ERROR: function: "tsip_message_parser_execute()"
file: ".\src\parsers\tsip_parser_message.c"
line: "465"
MSG: Failed to parse header - SIP/2.0 200 OK
Via: SIP/2.0/TCP
10.51.2.181:51483;branch=z9hG4bK1644629;rport=51483;received=10.51.2.181
From: <sip:[email protected]>;tag=1651818
To: <sip:[email protected]>;tag=4553420699375288837
Contact:
<sip:[email protected]:51483;transport=tcp>;+g.oma.sip-im;language="en,fr"
Call-ID: 30074204-9ced-cc88-e8af-6131104fdbe8
CSeq: 32393 SUBSCRIBE
l: 0
Expires: 3600
2012-11-21 09:40:28,139 ERROR [6] BogheCore.Services.Impl.SipService:0 -
Invalid content
2012-11-21 09:40:28,335 ERROR [9] BogheCore.Services.Impl.SipService:0 -
***ERROR: function: "tsip_message_parser_execute()"
file: ".\src\parsers\tsip_parser_message.c"
line: "465"
MSG: Failed to parse header - SIP/2.0 200 OK
Via: SIP/2.0/TCP
10.51.2.181:51483;branch=z9hG4bK1652501;rport=51483;received=10.51.2.181
From: <sip:[email protected]>;tag=1656856
To: <sip:[email protected]>;tag=4553420699375288838
Contact:
<sip:[email protected]:51483;transport=tcp>;+g.oma.sip-im;language="en,fr"
Call-ID: d1dab636-ff9b-2672-7521-4bea5e73fa7f
CSeq: 24466 SUBSCRIBE
l: 0
Expires: 3600
NOTIFY sip:[email protected]:51483;transport=tcp SIP/2.0
To: sip:[email protected];tag=212220272428209375
From: sip:[email protected];tag=212220272428209377
Via: SIP/2.0/TCP defaultsmsc.com;branch=z9hG4bK212220272428209378
CSeq: 1 NOTIFY
Call-ID: d1dab636-ff9b-2672-7521-4bea5e73fa7f
Max-Forwards: 70
User-Agent: IM-serv/OMA1.0
Event: reg
Contact: <sip:defaultsmsc.com>;transport=tcp
Subscription-State: active;expires=3600
Content-Length: 0
2012-11-21 09:40:28,336 ERROR [6] BogheCore.Services.Impl.SipService:0 -
Invalid content
2012-11-21 09:40:28,405 DEBUG [5]
BogheCore.Services.Impl.XmlConfigurationService:0 - Saving configuration...
2012-11-21 09:40:28,978 INFO [6] BogheCore.Services.Impl.SipService:0 -
OnDialogEvent (Dialog connecting)
2012-11-21 09:40:28,980 ERROR [9] BogheCore.Services.Impl.SipService:0 -
***ERROR: function: "tsip_message_parser_execute()"
file: ".\src\parsers\tsip_parser_message.c"
line: "465"
MSG: Failed to parse header - SIP/2.0 200 OK
Via: SIP/2.0/TCP
10.51.2.181:51483;branch=z9hG4bK1645988;rport=51483;received=10.51.2.181
From: <sip:[email protected]>;tag=1651093
To: <sip:[email protected]>;tag=4553420699375288839
Call-ID: 98400711-2fbb-e010-9d98-73675625caf2
CSeq: 32393 PUBLISH
l: 0
Expires: 3600
SIP-ETag: 212220272429051604
ioŸr£–fˆx
2012-11-21 09:40:28,980 ERROR [6] BogheCore.Services.Impl.SipService:0 -
Invalid content
Also once the boghe client is running. Any change in status - Busy->Online or
Online->Busy etc doesn't trigger a PUBLISH request to the server. There is only
the first PUBLISH when the client connects to the server for the first time.
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Version of the product is : v2.0.97.687 on a Windows 7 machine
Network trace between the client and server are attached
Original issue reported on code.google.com by [email protected] on 21 Nov 2012 at 7:00
Attachments:
Fixed the parse errors. The notify messages were missing the \r\n at the end.
Now I am noticing something different. When I update my status say from Busy to
Online etc the client is not sending a PUBLISH to the server. Not sure what the
issue is.
I see this in the boghe log file:
2012-11-26 13:46:00,125 ERROR [7] BogheCore.Services.Impl.SipService:0 -
***ERROR: function: "tnet_get_ip_n_port()"
file: ".\src\tnet_utils.c"
line: "920"
MSG: TNET_GET_SOCKADDR has failed with status code: -1
2012-11-26 13:46:00,126 ERROR [7] BogheCore.Services.Impl.SipService:0 -
***ERROR: function: "tnet_transport_send()"
file: ".\src\tnet_transport_win32.c"
line: "258"
MSG: WSASend have failed.
2012-11-26 13:46:00,126 ERROR [7] BogheCore.Services.Impl.SipService:0 -
***ERROR: function: "tnet_transport_send()"
file: ".\src\tnet_transport_win32.c"
line: "258"
MSG: (SYSTEM)NETWORK ERROR ==>An operation was attempted on something that is
not a socket.
2012-11-26 13:46:00,129 ERROR [7] BogheCore.Services.Impl.SipService:0 -
***ERROR: function: "tnet_get_ip_n_port()"
file: ".\src\tnet_utils.c"
line: "920"
MSG: TNET_GET_SOCKADDR has failed with status code: -1
2012-11-26 13:46:00,129 ERROR [7] BogheCore.Services.Impl.SipService:0 -
***ERROR: function: "tnet_transport_send()"
file: ".\src\tnet_transport_win32.c"
line: "258"
MSG: WSASend have failed.
2012-11-26 13:46:00,129 ERROR [7] BogheCore.Services.Impl.SipService:0 -
***ERROR: function: "tnet_transport_send()"
file: ".\src\tnet_transport_win32.c"
line: "258"
MSG: (SYSTEM)NETWORK ERROR ==>An operation was attempted on something that is
not a socket.
2012-11-26 13:46:00,130 ERROR [7] BogheCore.Services.Impl.SipService:0 -
***ERROR: function: "tnet_get_ip_n_port()"
file: ".\src\tnet_utils.c"
line: "920"
MSG: TNET_GET_SOCKADDR has failed with status code: -1
2012-11-26 13:46:00,130 ERROR [7] BogheCore.Services.Impl.SipService:0 -
***ERROR: function: "tnet_transport_send()"
file: ".\src\tnet_transport_win32.c"
line: "258"
MSG: WSASend have failed.
2012-11-26 13:46:00,130 ERROR [7] BogheCore.Services.Impl.SipService:0 -
***ERROR: function: "tnet_transport_send()"
file: ".\src\tnet_transport_win32.c"
line: "258"
MSG: (SYSTEM)NETWORK ERROR ==>An operation was attempted on something that is
not a socket.
2012-11-26 13:46:32,130 INFO [5] BogheCore.Services.Impl.SipService:0 -
OnDialogEvent (Transport error.)
2012-11-26 13:46:32,130 INFO [5] BogheCore.Services.Impl.SipService:0 -
OnDialogEvent (Dialog terminated)
2012-11-26 13:46:32,133 INFO [5] BogheCore.Services.Impl.SipService:0 -
OnDialogEvent (Transport error.)
2012-11-26 13:46:32,133 INFO [5] BogheCore.Services.Impl.SipService:0 -
OnDialogEvent (Dialog terminated)
2012-11-26 13:46:32,134 INFO [5] BogheCore.Services.Impl.SipService:0 -
OnDialogEvent (Transport error.)
2012-11-26 13:46:32,134 INFO [5] BogheCore.Services.Impl.SipService:0 -
OnDialogEvent (Dialog terminated)
2012-11-26 14:05:54,276 DEBUG [10]
BogheCore.Services.Impl.XmlConfigurationService:0 - Saving configuration...
2012-11-26 14:06:28,928 DEBUG [10]
BogheCore.Services.Impl.XmlConfigurationService:0 - Saving configuration...
2012-11-26 14:06:49,877 DEBUG [10]
BogheCore.Services.Impl.XmlConfigurationService:0 - Saving configuration...
Any clue if that would make the PUBLISH not get sent to the server?
Original comment by [email protected] on 26 Nov 2012 at 8:25