osip-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[osip-dev] What can cause the call of cb_transp_error?


From: Roger Schreiter
Subject: [osip-dev] What can cause the call of cb_transp_error?
Date: Sun, 01 Feb 2015 15:15:23 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130329 Thunderbird/17.0.5

Hello,

I wonder, why the callback function for transport error is called
in my programm.

My programm is accepting an INVITE from remote, is sending back
100 Trying immedeately, and then sending a new INVITE to another
IP address.

osip is calling my call back function cb_send_message(), which
sends the INVITE and returns with 0.
And then immedeately my cb_transp_error() is called with that
INVITE message as argument (less than 1 ms later).

How can osip guess, there is a transport error that quickly?

Any ideas, what can cause it?

The invite and the log follow here.

Regards,
Roger.


INVITE SIP:address@hidden SIP/2.0
Via: SIP/2.0/UDP 192.168.1.1;branch=454a55ef_1254647244
From: <SIP:address@hidden>;tag=296aae9d
To: <SIP:address@hidden>
Call-ID: address@hidden
CSeq: 1 INVITE
Contact: <SIP:address@hidden>
Content-Type: application/sdp
Allow: ACK, INVITE, CANCEL, BYE
Max-Forwards: 70
User-Agent: PLANica 0.1
Content-Length:   355
...


|5| <osip_transaction.c: 136> | allocating transaction resource 2
10ad96517d0d0c3

|5| <ict.c: 32> | allocating ICT context

|7| <osip_transaction.c: 349> | sipevent tr->transactionid: 2

|7| <osip_transaction.c: 350> | sipevent tr->state: 0

|7| <osip_transaction.c: 351> | sipevent evt->type: 16

|7| <osip_transaction.c: 352> | sipevent evt->sip: 4503810

|7| <osip_transaction.c: 373> | sipevent evt: method called!

|6| <osip_event.c: 51> | MESSAGE REC. CALLID:10ad96517d0d0c3

|7| <osip_transaction.c: 349> | sipevent tr->transactionid: 2

|7| <osip_transaction.c: 350> | sipevent tr->state: 1

|7| <osip_transaction.c: 351> | sipevent evt->type: 13

|7| <osip_transaction.c: 352> | sipevent evt->sip: 4503e10



reply via email to

[Prev in Thread] Current Thread [Next in Thread]