[SIPForum-discussion] Doubt regarding sipp with SER --- logs attached

mohan mannappan mohanjan1984 at gmail.com
Sat Nov 7 18:05:19 UTC 2009


Hi Sriram,

                   It worked when i fed the via for both the proxy and the
60.0.0.12.
                   I had last_via in my xml but it was shown at the right
corner of SIP 200 ok msg.            I also found that the branch id for the
bye sent was different than that was in the 200 ok, i changed it i.e, i fed
it correctly then it all worked fine, i still dont fine any chance of y it
did not reflect in last_via bcoz the bye sent from SER to UAS has it.

thanks,
Mohan

On Fri, Nov 6, 2009 at 10:28 AM, Sriram Subramanian <sriram.ngn at gmail.com>wrote:

> Hi Mohan,
>                    I think i found out the reason for your problem .Check
> your UAS script you have not mentioned the Via header for the 200 OK your
> had written for the BYE.
>
> Include the [last_Via:] in that 200 OK message in the UAS script and things
> should mostly work fine.
>
> You can also see in your traces that the 200 OK which is sent from the UAS
> has no Via header when it sends to the SER.The SER might have dropped it as
> it does not account for a VALID TRANSACTION as ther is no branch to indicate
> it .
>
> Regards,
> Sriram
>
>
> On Fri, Nov 6, 2009 at 9:24 AM, mohan mannappan <mohanjan1984 at gmail.com>wrote:
>
>> Hi,
>>
>>             The following logs are attached:
>>
>>             1. .XML and .CSV with register for UAC
>>             2. .XML and .csv for UAS
>>             3. .XML for registration ( I have attached the ethereal trace
>> for this, even though i dont
>>                 give any retransmition, i find  that UAS keeps on sending
>> register message and SER is sending continous 200 ok.
>>             4. Ethereal trace for registration for UAC to SER is mentioned
>> as 60.0.0.1.
>>             5. Ethereal trace for registration for UAS to SER is mentioned
>> as 50.0.0.1.
>>             6. Ethereal trace for call scenario.
>>                 the flow is 60.0.0.10 - 50.0.0.1- 50.0.0.1 - 50.0.0.15 (
>> after the bye sent from UAC, 200 ok is sent from UAS to SER but SER is not
>> forwarding the bye.
>>             hence, continous BYE msg is being sent by UAC.
>>
>>
>> thanks,
>> Mohan M
>>
>>>
>>>>
>>>>   Hi all,
>>>>>>
>>>>>>
>>>>>>              I need to automate some of the SIP testing features with
>>>>>> SIPP.
>>>>>>              The Topology that we use using Polycom phones is :
>>>>>>
>>>>>>
>>>>>>                    50.0.0.10            50.0.0.254           9.9.9.2
>>>>>>                            9.9.9.1          60.0.0.254
>>>>>> 60.0.0.10
>>>>>>
>>>>>>  UAS--------------HUB--------------------Router----------------------------------------------------Router------------------HUB-------------------UAC
>>>>>>                                   |
>>>>>>                                   |
>>>>>>                                   |
>>>>>>                Linux box SER proxy and registrar
>>>>>>
>>>>>>
>>>>>> The Scenario is that :
>>>>>>
>>>>>> UAC side is considered as WAN.
>>>>>> UAS side is considered as LAN.
>>>>>> Both UAC and UAS need to register with the SER server.
>>>>>> The call should be made from WAN to LAN.
>>>>>>
>>>>>>
>>>>>> ###############################################
>>>>>>
>>>>>> For both i am using
>>>>>>
>>>>>> REGISTER message in xml to register to the servers.
>>>>>>
>>>>>>
>>>>>> ################################################
>>>>>>
>>>>>> In From and to, i use the SER's ip address bcoz both UAC and UAS is
>>>>>> registered with the SER
>>>>>>
>>>>>> i.e from :  101 at 50.0.0.1  where 101 is the number of UAC
>>>>>>     To    :  201 at 50.0.0.1  where 201 is the number of UAS
>>>>>>
>>>>>> I am making a call with the normal polycom phone with the same
>>>>>> topology, captured the ethereal and then did all this.
>>>>>>
>>>>>> Everything is fine but atlast when UAC is sending the BYE, SER
>>>>>> forwards it to UAS and UAS gives 200 ok but SER does not send it to UAC
>>>>>> hence the call fails.
>>>>>>
>>>>>> Please, help me with how to troubleshoot, such a Scenario.
>>>>>>
>>>>>> Note : I have attached the diagram of the Scenario.
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> Mohan M
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> This is the SIP Forum discussion mailing list
>>>>>> TO UNSUBSCRIBE, or edit your delivery options, please visit
>>>>>> http://sipforum.org/mailman/listinfo/discussion
>>>>>> Post to the list at discussion at sipforum.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> They can because they think they can.
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> They can because they think they can.
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20091107/c6c4d3f7/attachment-0002.html>


More information about the discussion mailing list