Re: [Opalvoip-user] SIP Ack problems with "To"-header
Brought to you by:
csoutheren,
rjongbloed
Menu
▾
▴
Re: [Opalvoip-user] SIP Ack problems with "To"-header
|
From: Alexey N. <ale...@ma...> - 2012-01-10 11:05:11
|
Thx, Robert, I checked on Luyten, it works OK now. On 8 January 2012 13:35, Robert Jongbloed <ro...@vo...> wrote: > > This should now be fixed in both Luyten (stable) and Eridani (trunk) > > -------- > Robert Jongbloed > OPAL/OpenH323/PTLib Architect and Co-founder. > > On 06/01/2012, at 12:40 PM, Robert Jongbloed wrote: > > OK, I see the problem. I will fix it this weekend. > > -------- > Robert Jongbloed > Vox Lucida Pty. Ltd. > > > > > On 26/12/2011, at 5:27 PM, Alexey Novikov wrote: > > Hello, > I'm rather new to OPAL so I hope I'm contacting right mailing-list. > I'm going to use OPAL in SIP-softphone application and now I'm testing > features of OPAL with OpenPhone. > This SIP-softphone is going to be used with Panasonic IP-PBXs (now only > but) mostly. > But I've found some "incompatibilitys" when connecting OPAL as > SIP-softphone to Panasonic PBXs. > With help of their tech-support and reading RFCs I managed to make some > changes to OPAL source and get all work (for now, but may be there will be > more problems), but I'm not very good programer, this changes are not > "clever" and can affect something else, and anyway I think I should inform > You about this iccompatibility, so if You are interested, You can make > right changes to code, or please tell if I'm wrong, and OPAL's behaviour is > correct. > So I'll try to describe problem. > There were two problems, both of them are related to how OPAL SIP-stack > acts when generating To-header of ACK-PDU. > In both of then we use OpenPhone as SIP client registered on SIP-server > (which is Paansonic PBX) and making outgoing call to another phone. > 1. When initiating a session OPAL sends Invite and gets "Status-Line: > SIP/2.0 407 Proxy Authentication Required" from SIP-server with header "To: > sip:115@192.168.0.111;tag=10743" it generates ACK message in rsponse with > following To-header: > To: <sip:115@192.168.0.111;tag=10743> > Which is not realy good. It should be > To: <sip:115@192.168.0.111>;tag=10743 or To: sip:115@192.168.0.111 > ;tag=10743 > I think that OPAL is not going to get "tag" field, but I don't know why. > In RFC-3665 there is similar example in section "3.3. Session with > Multiple Proxy Authentication" where "Tag" field is presented in To-header > field of 407-message and then it's copied in To-header field of ACK-message. > As result PBX generates "500-Internal server error" and call is not > performed. > 2. When we made OPAL respond to "407" message as our PBX expects, there > was found another error. > We are doing the same outgoing call from OPAL, remote party rings, we see > normal SIP-messages flow between OPAL and PBX, but when remote party > answers the call and OPAL gets "SIP/2.0 200 OK" message from SIP-server > with following to-header: "To: sip:115@192.168.0.111;tag=12897", > After that OPAL sends ACK-message but without "tag"-field in To-header: > "To: sip:115@192.168.0.111" > While in RFC-3261 there is example in 24.2 where sip-client responds to > "OK"-message from SIP-server with "tag"-field in "To"-header. > As result PBX resends "OK"-message several times and then disconnects call > after about 30-seconds. > > So I hope somebody can teach me if it's OPAL wrong interpretation if > SIP-standarts or Panasonic error, and how can it be corrected in right way. > I dont realy know much about OPAL's targets, but I think Panasonis PBXs > are widespread so getting it work with OPAL would be good for some users. > > > ------------------------------------------------------------------------------ > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > > http://p.sf.net/sfu/intel-appdev_______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > > > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! > http://p.sf.net/sfu/Citrix-VDIinabox_______________________________________________ > > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > > > > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > _______________________________________________ > Opalvoip-user mailing list > Opa...@li... > https://lists.sourceforge.net/lists/listinfo/opalvoip-user > > |
