[SR-Users] [Sipp-users] Use of SIPP along with kamailio - REGISTER followed by INVITE not working

Bernhard Suttner bernhard.suttner at winet.ch
Tue Jan 4 11:52:17 CET 2011


Hi,

I think, the NAT pin-hole is closed. Normally, kamailio does detect NAT and therefore does send small network pakets, that the firewall would not close the port. If you use sipp  and kill it to use a new configuration the NAT port was closed already.

Best regards,
Bernhard

-----Ursprüngliche Nachricht-----
Von: sr-users-bounces at lists.sip-router.org [mailto:sr-users-bounces at lists.sip-router.org] Im Auftrag von Stephen McVarnock
Gesendet: Dienstag, 4. Januar 2011 11:24
An: Michael Hirschbichler; sr-users at lists.sip-router.org; SIPP Users
Betreff: Re: [SR-Users] [Sipp-users] Use of SIPP along with kamailio - REGISTER followed by INVITE not working

Hi,
  I have got the second scenario here to work i.e. REGISTER xml ran, 
kill sipp, run sipp with INVITE xml.

There seems to be timing issue associated with this though - if I leave 
to long a delay between killing REGISTER xml
and running INVITE xml then the INVITE will not be received by the sipp 
script.

The Expires header for the REGISTER is set to 36000, so that is not the 
issue.

Maybe this is a kamalio problem - anyway, for my purposes (as long as I 
am quick enough!), this works.

Regards,
   Steve.

> On 2011-01-04 08:59, Stephen McVarnock wrote:
>   
>> http://sipp.sourceforge.net/wiki/index.php/Patches#Pre.2FPost_scenarios
>>
>> Does anyone know what the current state of play is for this proposed 
>> patch or if there is another way to get around this issue?
>>     
>
> Well, I developed this extension from june until december 2006 but we
> never managed to merge this branch into the main-tree.
>
>   
>> 2) I tried to REGISTER the SIPP endpoint in a single xml scenario file 
>> with kamailio. This works as per usual. I then killed
>> the SIPP instance and ran a new SIPP script listening on the same port 
>> before trying to send the INVITE to it. I expected this to work
>> as the SIPP scenarios (both sending REGISTER and expecting INVITE) 
>> listened on the same port. However, the INVITE was not
>> received by the SIPP endpoint. Can anyone think of a reason for this?
>>     
>
> Well, this is a standard task of sipp and usually works without any
> limitations. Can you send both scnearios (Register and UAS) as well as
> the used command line parameters?
>
> br
> Michael
>
>   


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Stephen McVarnock,
AePONA Ltd,
Interpoint Building, 
20-24 York Street, 
Belfast BT15 1AQ
Tel: +44 (0)28 9026 9114        
Fax: +44 (0)28 9026 9111

http://www.aepona.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users at lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users





More information about the sr-users mailing list