SIP: BYE/ 481 (No Dialog Found)!!!!!!!!!!
Hi all,
I am developing an IMChat application using Nokia SIP Stack.
Kindly c my problem and help me in this.. there are 2 issues..
1)I want to know whether the CALLID will be same in REGISTER, INVITE, MESSAGE,BYE for a particular session.
2) And when i am sending a BYE Request i am getting 481 (NO DIALOG FOUND) response!!!!!!!!
If anyone has encountered the same problem,..plzz let me know.
I can see the BYE packet going in the network as:
/********************************************************/
Session Initiation Protocol
Request-Line: BYE sip:minu@172.19.25.22 SIP/2.0
Message Header
Via: SIP/2.0/UDP 172.19.25.21:5060;branch=z9hG4bKCew6vUOO2MXge
To: sip:minu@172.19.25.22;tag=_zxwyt30no
From: sip:smilie@172.19.25.21;tag=FjU6vPYYrk
Supported: sec-agree
Call-ID: FKM6vRvhxQ60RH2TswVdthy6hAenZx
CSeq: 170 BYE
Max-Forwards: 70
Content-Length: 0
/********************************************************/
This is the response i'm getting for BYE
/********************************************************/
Session Initiation Protocol
Status-Line: SIP/2.0 481 No dialog found
Message Header
Via: SIP/2.0/UDP 172.19.25.21:5060;branch=z9hG4bKCew6vUOO2MXge
To: sip:minu@172.19.25.22;tag=_zxwyt30no
From: sip:smilie@172.19.25.21;tag=FjU6vPYYrk
Call-ID: FKM6vRvhxQ60RH2TswVdthy6hAenZx
CSeq: 170 BYE
Content-Length: 0
/******************************************************/
Thanks in advance,
Mini
Re: SIP: BYE/ 481 (No Dialog Found)!!!!!!!!!!
Hi,
Call-ID should be unique for each SIP dialog.
1) it must be unique for REGISTER( and same for corresponding repsonses...)
2) and new must be generated for each INVITE request( this is used for all provisinal 1xx responses, final responses, ACK, BYE and CANCEL request and all requests send within dialog (as MESSAGE for example )
3) other dialog examples are PUBLISH or SUBSCRIBE requests
Note that dialog is not referenced only by Call-ID header, but also both tag parameters from To and From header must be same.
If you need me to help you with your problem you must put here complete trace with INVITE, not only BYE!!!! or send me etheral file to my mail
Bye
STeN
Re: SIP: BYE/ 481 (No Dialog Found)!!!!!!!!!!
Look on RFC
"...Call-ID contains a globally unique identifier for this call, generated by the combination of a random string
and the softphone’s host name or IP address. The combination of the To tag, From tag, and Call-ID completely
defines a peer-to-peer SIP relationship between Alice and Bob and is referred to as a dialog..."
or
"...Dialog: A dialog is a peer-to-peer SIP relationship between two UAs that persists for some time. A dialog
is established by SIP messages, such as a 2xx response to an INVITE request. A dialog is identified by
a call identifier, local tag, and a remote tag. A..."
AND
"... A key concept for a user agent is that of a dialog. A dialog represents a peer-to-peer SIP relationship between
two user agents that persists for some time. ..."
"...A dialog is identified at each UA with a dialog ID, which consists of a Call-ID value, a local tag and a remote
tag. The dialog ID at each UA involved in the dialog is not the same. Specifically, the local tag at one UA is
identical to the remote tag at the peer UA. The tags are opaque tokens that facilitate the generation of unique
dialog IDs.
A dialog ID is also associated with all responses and with any request that contains a tag in the To field..."
Bye
STeN
Re: SIP: BYE/ 481 (No Dialog Found)!!!!!!!!!!
Hi,
Thanks for the Reply...
i'm sending all the packet info..plzz help me in this..
i'm still gettg 48i response for BYE :(
/************************REGISTER************************/
Frame 1325 (427 bytes on wire, 427 bytes captured)
Ethernet II, Src: 00:40:43:25:22:4a, Dst: 00:d0:b7:72:99:83
Internet Protocol, Src Addr: 172.19.25.22 (172.19.25.22), Dst Addr: 172.19.24.113 (172.19.24.113)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Request-Line: REGISTER sip:172.19.24.113 SIP/2.0
Method: REGISTER
Resent Packet: False
Message Header
Route: <sip:172.19.24.113>
Via: SIP/2.0/UDP 172.19.25.22:5060;branch=z9hG4bKq972Q5SJsxd2r
From: sip:minu@172.19.25.22;tag=c4f2QeDr1N
SIP from address: sip:minu@172.19.25.22
SIP tag: c4f2QeDr1N
To: sip:minu:fd@172.19.24.113
Contact: <sip:minu@172.19.25.22;comp=sigcomp>;expires=3600
Supported: sec-agree
Call-ID: hVH2Q7OfaP7YUwySQJfZ7mXLC8ICQT
CSeq: 372 REGISTER
Max-Forwards: 70
Content-Length: 0
/***********************200_OK_Register********************/
Frame 1327 (610 bytes on wire, 610 bytes captured)
Ethernet II, Src: 00:0f:fe:19:d0:ef, Dst: 00:40:43:25:22:4a
Internet Protocol, Src Addr: 172.19.24.113 (172.19.24.113), Dst Addr: 172.19.25.22 (172.19.25.22)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Status-Code: 200
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 172.19.25.22:5060;branch=z9hG4bKq972Q5SJsxd2r
From: sip:minu@172.19.25.22;tag=c4f2QeDr1N
SIP from address: sip:minu@172.19.25.22
SIP tag: c4f2QeDr1N
To: sip:minu:fd@172.19.24.113;tag=e13f869e5c297be432dff76e3726d0a5.78a9
SIP to address: sip:minu:fd@172.19.24.113
SIP tag: e13f869e5c297be432dff76e3726d0a5.78a9
Call-ID: hVH2Q7OfaP7YUwySQJfZ7mXLC8ICQT
CSeq: 372 REGISTER
Contact: <sip:minu@172.19.25.22;comp=sigcomp>;q=0.00;expires=3600
Server: Sip EXpress router (0.8.14 (i386/linux))
Content-Length: 0
Warning: 392 172.19.24.113:5060 "Noisy feedback tells: pid=21132 req_src_ip=172.19.25.22 req_src_port=5060 in_uri=sip:172.19.24.113 out_uri=sip:172.19.24.113 via_cnt==1"
/***********************INVITE ***************************/
Frame 1537 (371 bytes on wire, 371 bytes captured)
Ethernet II, Src: 00:40:43:24:fa:49, Dst: 00:40:43:25:22:4a
Internet Protocol, Src Addr: 172.19.25.21 (172.19.25.21), Dst Addr: 172.19.25.22 (172.19.25.22)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Request-Line: INVITE sip:minu@172.19.25.22 SIP/2.0
Method: INVITE
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 172.19.25.21:5060;branch=z9hG4bKoHAq28p2Ob3PK
From: sip:smilie@172.19.25.21;tag=-Fgq2aIjwX
SIP from address: sip:smilie@172.19.25.21
SIP tag: -Fgq2aIjwX
To: sip:minu@172.19.25.22
Contact: sip:smilie@172.19.25.21
Supported: sec-agree
CSeq: 295 INVITE
Call-ID: b-8q238QLrfGzj9SImJc69W0OQoGQW
Max-Forwards: 70
Content-Length: 0
/**************** TRYING ****************************/
Frame 1604 (290 bytes on wire, 290 bytes captured)
Ethernet II, Src: 00:40:43:25:22:4a, Dst: 00:40:43:24:fa:49
Internet Protocol, Src Addr: 172.19.25.22 (172.19.25.22), Dst Addr: 172.19.25.21 (172.19.25.21)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Status-Code: 200
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 172.19.25.21:5060;branch=z9hG4bKoHAq28p2Ob3PK
To: sip:minu@172.19.25.22;tag=1VX2Q1whQN
SIP to address: sip:minu@172.19.25.22
SIP tag: 1VX2Q1whQN
From: sip:smilie@172.19.25.21;tag=-Fgq2aIjwX
SIP from address: sip:smilie@172.19.25.21
SIP tag: -Fgq2aIjwX
Call-ID: b-8q238QLrfGzj9SImJc69W0OQoGQW
CSeq: 295 INVITE
Content-Length: 0
/******************** ACK ******************************/
Frame 1615 (346 bytes on wire, 346 bytes captured)
Ethernet II, Src: 00:40:43:24:fa:49, Dst: 00:40:43:25:22:4a
Internet Protocol, Src Addr: 172.19.25.21 (172.19.25.21), Dst Addr: 172.19.25.22 (172.19.25.22)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Request-Line: ACK sip:minu@172.19.25.22 SIP/2.0
Method: ACK
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 172.19.25.21:5060;branch=z9hG4bK21GBmxB5kR5kY
To: sip:minu@172.19.25.22;tag=1VX2Q1whQN
SIP to address: sip:minu@172.19.25.22
SIP tag: 1VX2Q1whQN
From: sip:smilie@172.19.25.21;tag=-Fgq2aIjwX
SIP from address: sip:smilie@172.19.25.21
SIP tag: -Fgq2aIjwX
Supported: sec-agree
Call-ID: b-8q238QLrfGzj9SImJc69W0OQoGQW
CSeq: 295 ACK
Max-Forwards: 70
Content-Length: 0
/******************MESSAGE******************************/
Frame 1832 (376 bytes on wire, 376 bytes captured)
Ethernet II, Src: 00:40:43:25:22:4a, Dst: 00:40:43:24:fa:49
Internet Protocol, Src Addr: 172.19.25.22 (172.19.25.22), Dst Addr: 172.19.25.21 (172.19.25.21)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Request-Line: MESSAGE sip:smilie@172.19.25.21 SIP/2.0
Method: MESSAGE
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 172.19.25.22:5060;branch=z9hG4bKrGz2Q4aPhgRZE
From: sip:minu@172.19.25.22;tag=Q7P2Q9UESw
SIP from address: sip:minu@172.19.25.22
SIP tag: Q7P2Q9UESw
To: sip:smilie@172.19.25.21
Supported: sec-agree
CSeq: 374 MESSAGE
Call-ID: R-f2Qfr5c0V2Xa6aohMK0a9i8Ngk4T
Max-Forwards: 70
Content-Type: text/plain
Content-Length: 9
Message body
/*******************200OK_Message*************************/
Frame 1837 (291 bytes on wire, 291 bytes captured)
Ethernet II, Src: 00:40:43:24:fa:49, Dst: 00:40:43:25:22:4a
Internet Protocol, Src Addr: 172.19.25.21 (172.19.25.21), Dst Addr: 172.19.25.22 (172.19.25.22)
User Datagram Protocol, Src Port: 5060 (5060), Dst Port: 5060 (5060)
Session Initiation Protocol
Status-Line: SIP/2.0 200 OK
Status-Code: 200
Resent Packet: False
Message Header
Via: SIP/2.0/UDP 172.19.25.22:5060;branch=z9hG4bKrGz2Q4aPhgRZE
To: sip:smilie@172.19.25.21;tag=FkQq2cf-qr
SIP to address: sip:smilie@172.19.25.21
SIP tag: FkQq2cf-qr
From: sip:minu@172.19.25.22;tag=Q7P2Q9UESw
SIP from address: sip:minu@172.19.25.22
SIP tag: Q7P2Q9UESw
Call-ID: R-f2Qfr5c0V2Xa6aohMK0a9i8Ngk4T
CSeq: 374 MESSAGE
Content-Length: 0
/********************** BYE ****************************/
Session Initiation Protocol
Request-Line: BYE sip:minu@172.19.25.22 SIP/2.0
Message Header
Via: SIP/2.0/UDP 172.19.25.21:5060;branch=z9hG4bKCew6vUOO2MXge
To: sip:minu@172.19.25.22;tag=_zxwyt30no
From: sip:smilie@172.19.25.21;tag=FjU6vPYYrk
Supported: sec-agree
Call-ID: FKM6vRvhxQ60RH2TswVdthy6hAenZx
CSeq: 170 BYE
Max-Forwards: 70
Content-Length: 0
/********************************************************/
/***********************481 (No Dialog Found)*****************/
Session Initiation Protocol
Status-Line: SIP/2.0 481 No dialog found
Message Header
Via: SIP/2.0/UDP 172.19.25.21:5060;branch=z9hG4bKCew6vUOO2MXge
To: sip:minu@172.19.25.22;tag=_zxwyt30no
From: sip:smilie@172.19.25.21;tag=FjU6vPYYrk
Call-ID: FKM6vRvhxQ60RH2TswVdthy6hAenZx
CSeq: 170 BYE
Content-Length: 0
/******************************************************/
Thanks a lot
-Mini
Re: SIP: BYE/ 481 (No Dialog Found)!!!!!!!!!!
Hi,
you're use different <tag> parameters for each sip transacion.
Your BYE <To> anf <From> headers:
To: sip:minu@172.19.25.22;tag=_zxwyt30no
From: sip:smilie@172.19.25.21;tag=FjU6vPYYrk
It shoud be:
To: sip:minu@172.19.25.22;tag=1VX2Q1whQN
From: sip:smilie@172.19.25.21;tag=-Fgq2aIjwX
this is used in INVITE/200 OK/ACKand together with Call-ID it identifies the dialog.
Bye
STeN
Re: SIP: BYE/ 481 (No Dialog Found)!!!!!!!!!!
Hi Stenlik,
But the nokia SIP Stack is creating the tag and i'm not able to manipulate any of the headers like Call-Id, CSeq, From, MAx-Fwds, Min-Expires, record Route, To, Via...
I can set only the content header and in BYE the content header is not coming..
Is it necessary that the contect header should be ther in BYE ??
I tried setting the content too..but then the programme is crashing at SendByeL().
Thanx a lot again ..:)
-Mini
Re: SIP: BYE/ 481 (No Dialog Found)!!!!!!!!!!
Hi,
I don't know Nokia SIP stack API, because I use other vendor commercial SIP stack, but I saw Nokia applications, which use Nokia sip stack and they were able to use the same Dialog ID(Call-ID+both tags) for whole SIP session. It should be done in some way!!!, otherwise each SIP proxy will reject the BYE request.
Anybody here on the forum tried it and ans send traces here ???
Any SIP expert here???
Thanks a lot for help
Bye
STeN
Chat with Nokia SIP Stack
Hi,
I also want to create a IMChat with presence using the Nokia SIP Stack, but I find not clearly in the Nokia API if it supports methods like "MESSAGE" or "PUBLISH". How can I use them with this SIP Stack? Anyone has tested it?
Thanks in advance
Re: Chat with Nokia SIP Stack
[QUOTE=diegodm]Hi,
I also want to create a IMChat with presence using the Nokia SIP Stack, but I find not clearly in the Nokia API if it supports methods like "MESSAGE" or "PUBLISH". How can I use them with this SIP Stack? Anyone has tested it?
Thanks in advance[/QUOTE]
Hi,
you can have a look at the sip example (SIPEX) which comes along with 90 Series SDK(Nokia 7710 sdk).That example has used MESSAGE API's.Have a look on that.
Hp thiz Helps
Best Regardz
Priju
Re: SIP: BYE/ 481 (No Dialog Found)!!!!!!!!!!
Hello,
Thanks for answering. I am not sure if you talked about the Nokia 7710 Message API for SMS,MMS,.. or the Message API I am interesting in, to send a SIP 'MESSAGE' request. In 'Nokia 7710: Messaging APIs' talks about the first one, maybe I have not understood you... :-((
Re: SIP: BYE/ 481 (No Dialog Found)!!!!!!!!!!
[QUOTE=diegodm]
I am not sure if you talked about the Nokia 7710 Message API for SMS,MMS,.. or the Message API I am interesting in, to send a SIP 'MESSAGE' request. [/QUOTE]
No, the relevant SIPEX example comes along with Nokia 7710 sdk installation.Do install that sdk which is available in forum.nokia and you find the example.
this SIPEX example deals with the method MESSAGE of SIP Protocol.
I think you need to configure the settings in that example.As i dont have the sdk now im not sure what all i had configured.Anyways that SIPEX example is a good start for u!
More over in this document s90_cpp_sdk_1_1_exapp ( which come in your installation folder of 7710 sdk) you can find the explanation of that example..
Best Regardz
Priju
Re: SIP: BYE/ 481 (No Dialog Found)!!!!!!!!!!
Hi,
Thanks , it seems a complete example with the MESSAGE method!!!. Do you know something about the PUBLISH? I was thinking about something like that:
reqElem->SetMethodL( "PUBLISH" );
Do you know if the Nokia SIP Stack would support it?
Thanks a lot
Diego
Re: SIP: BYE/ 481 (No Dialog Found)!!!!!!!!!!
[QUOTE=diegodm]
Do you know if the Nokia SIP Stack would support it?
Diego[/QUOTE]
Yea,Nokia SIP Stack does support Publish.
i suggest you to have look at the chipflip example,its really worth example to get started.
you also need to download The SIP Plug-in for Series 60 SDK which is an extension to the Series 60 SDK 2.0 for development of SIP applications.
It provides tools and documentation for developing and testing SIP enabled Applications for Series 60 Developer Platform 2.0 devices.
Bst Regardz
Priju
Re: SIP: BYE/ 481 (No Dialog Found)!!!!!!!!!!
Hi,
Iam also trying to establish a SIP session and Even Iam facing the same problem you had faced of sending a BYE request, I get a 481 response. If you could solve the problem i will be very thankful to you if you could let me know how you did it (i.e if you cold share with me the code for sending BYE, Im successful in sending INVITE, Processing incoming INVITE, Register etc..). Even Iam using Nokia S60 3rd Edition phones for my programs. I please request you to share your thoughts with me.
Thanks a million
