SIPfoundry

Mailing Lists

Issue Tracker

Source Code

< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

[SFtrack] Commented: (XECS-1607) Call pickup problem (presumably dialog event package on LG-Nortel phones work inaccurately)

    [ 
http://track.sipfoundry.org/browse/XECS-1607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_30269
 ] 

Nikolay Kondratyev commented on XECS-1607:
------------------------------------------

Ok.
I'm watching xtrn-218.
When i'll get fixed firmware for LG phone, i'll verify, that the problem is 
gone.
Nikolay.

> Call pickup problem (presumably dialog event package on LG-Nortel phones work 
> inaccurately)
> -------------------------------------------------------------------------------------------
>
>                 Key: XECS-1607
>                 URL: http://track.sipfoundry.org/browse/XECS-1607
>             Project: sipXecs
>          Issue Type: Bug
>          Components: LG 6800 Phones
>    Affects Versions: 3.10.2
>         Environment: SIPxchange ECS (3.10.2-013153 2008-07-22T03:38:43 
> oem-centos5)
> LG-Nortel phones with firmware  1.2.38sp
> Snom 360 phone with firmware 7.3.7 14671
>            Reporter: Nikolay Kondratyev
>            Assignee: Nikolay Kondratyev
>            Priority: Critical
>         Attachments: dump1, merged.xml, sipx-configuration.tar.gz
>
>
> The problem is that when the call is going from snom360 phone to LG-Nortel 
> phone and another LG-Nortel phone tries to pickup the call, pickup fails.
> Network trace in tcpdump format is attached. 
> Sipxsnapshot with debug logging level is also attached.
> The time of the call is Wed Aug 13 08:25:44 UTC 2008.
> The call is as follows:
> The snom 360 phone (ext. 3805, ip 172.23.12.229) calls ext. 3800 (lg-nortel 
> 6830 phone, 172.23.12.246).  Call-Id is 3c27b2070551-cn02ehf5ylue.
> Sipx address is 172.23.12.104.
> Then lg-nortel 6812 phone (ext. 3803, 172.23.12.242) tries to pickup the 
> call.  Call pick-up call has Call-Id 
> 94bc6260-ac170cf2-13c4-14122-73f9b7c-14122@xxxxxxxxxxxxx  Call pick-up 
> SUBSCRIBE has Call-Id s-965aba646ee4829d-1.
> But when sipx sends "Invite with replaces" to snom phone (packet 56 in the 
> attached trace), snom phone answers with 404 not found and pickup fails.
> My analysis is as following:
> I noticed that snom phone is registered at sipx with the following contact 
> (shown in diagnostics->registration page in the sipx UI) uri:  
> <sip:3805@xxxxxxxxxxxxx:2051;line=za5gatgk>
> And initial invite in the attached trace (packet 23) contains the same 
> contact uri.
> I compared attached trace with successful call pickup, when the call is 
> originating from mp118, and with basic call to snom phone.
> I noticed, that when making basic call to snom phone, request line of the 
> invite message is 
> INVITE sip:3805@xxxxxxxxxxxxx:2051;line=za5gatgk SIP/2.0
> And when sipx sends "invite with replaces" to snom phone during call pickup, 
> the request line is
> INVITE sip:3805@xxxxxxxxxxxxx:2051 SIP/2.0
> My idea is that snom phone does not like, that request line does not contain 
> "line=za5gatgk ", and answers with "404 not found".
> As far as i understand full URI (string included between < > must be used.
> When creating "invite with replaces" sipx, as far as i know, copies uri and 
> tags from the body of Notify message (packets 47 and 51 in attached trace) 
> recieved from ext.6800 lg-nortel phone.
> Here is the body of packet 47:
> <?xml version="1.0"?>
> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" 
> state="full" entity="sip:3800@xxxxxxxxxxxx">
> <dialog id="16b7eb0" call-id="3c267c70b576-fxtoi35agsbl" 
> local-tag="94bf47b8-ac170cf6-13c4-c5b-219cd5ca-c5b" remote-tag="8q6qek5d4d" 
> direction="recipient">
> <state code="180">early</state>
> <duration>4</duration>
> <local>
> <identity>sip:3800@xxxxxxxxxxxx</identity>
> <target uri="sip:3800@xxxxxxxxxxxxx:5060"/>
> </local>
> <remote>
> <identity>sip:3805@xxxxxxxxxxxx</identity>
> <target uri="sip:3805@xxxxxxxxxxxxx:2051"/>
> </remote>
> </dialog>
> </dialog-info>
> Uri is specified without line=za5gatgk part, though contact uri of initial 
> invite (packet 23) contains it.
> The above problem means, that in mixed phone environment (snom and lg-nortel) 
> call pickup feature can not be used.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://track.sipfoundry.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira