Re: [Sipp-users] UDP destination port in server mode

2008-09-15 Thread Charles P Wright
Marc,

If you can extract the port from the header, you can use the new, but as 
of yet undocumented setdest action:

Something like:
  nop
 action
assignstr assign_to=url value=[next_url] /
ereg 
regexp=sip:(.*)@([0-9A-Za-z\.]+):([0-9]+);transport=([A-Z]+) 
search_in=var check_it=true assign_to=dummy,name,host,port,transport 
variable=url /
warning message=HOST: [$host], PORT: [$port], TRANSPORT: 
[$transport] /
setdest host=[$host] port=[$port] protocol=[$transport] /
log 
message=[$host];[$port];[$transport];sip:[EMAIL PROTECTED]:[$port] /
 /action
  /nop

Charles

[EMAIL PROTECTED] wrote on 09/05/2008 10:31:22 AM:

 Hello all,
 
 I'm struggling to get sipp send out the response packets to the 
 right UDP port. 
 
 I'm using a pretty recent SIPp dated 20080723. SIPp is listening for
 register requests on port 5060 (-t u1 -p 5060) and answers them with
 a 200 OK.
 
 The register request messages arrive from a fixed source address (S-
 IP), with a variable UDP source port and have internally a Via:-
 header specifying S-IP:5060, so the responses are expected there, 
 and not an the variable source port number.
 
 Not specifying anything special on the command line, responses go 
 from SIPp:5060 to S-IP:source-port, instead of the address mentioned
 in the Via:.
 I've seen somewhere a mention that it can follow the via, but didn't
 find anything on that in documentation of source, so I think it is 
 not in. Anybody know more of this?
 
 As in my case the destination is the fixed S-IP:5060, I tried 
 specifying this with the '-rsa' remote sending address option. Using
 this option has a clear effect on the behaviour: SIPp now sends the 
 message from SIPp:variable-high-port to S-IP:source-port instead of 
 using 5060 as source port. This seems very strange to me, the SIPp 
 source port gets variable, but the specified sending address:port is
 not used, also not when giving another IP address as rsa-
 destination. So, using the rsa-option has an effect, but not really 
 the expected one.
 
 Anybody knowing how to solve this problem with SIPp?
 
   Best regards,
 
   MarcVD
 
 
 (-: from Marc VAN DIEST (BELGACOM) ;-)
 
 
-
 This SF.Net email is sponsored by the Moblin Your Move Developer's 
challenge
 Build the coolest Linux based applications with Moblin SDK  win great 
prizes
 Grand prize is a trip for two to an Open Source event anywhere in the 
world
 http://moblin-contest.org/redirect.php?banner_id=100url=/
 ___
 Sipp-users mailing list
 Sipp-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/sipp-users


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users


[Sipp-users] UDP destination port in server mode

2008-09-05 Thread marc.van.diest
Hello all,

I'm struggling to get sipp send out the response packets to the right UDP port.

I'm using a pretty recent SIPp dated 20080723. SIPp is listening for register 
requests on port 5060 (-t u1 -p 5060) and answers them with a 200 OK.

The register request messages arrive from a fixed source address (S-IP), with a 
variable UDP source port and have internally a Via:-header specifying 
S-IP:5060, so the responses are expected there, and not an the variable source 
port number.

Not specifying anything special on the command line, responses go from 
SIPp:5060 to S-IP:source-port, instead of the address mentioned in the Via:.
I've seen somewhere a mention that it can follow the via, but didn't find 
anything on that in documentation of source, so I think it is not in. Anybody 
know more of this?

As in my case the destination is the fixed S-IP:5060, I tried specifying this 
with the '-rsa' remote sending address option. Using this option has a clear 
effect on the behaviour: SIPp now sends the message from 
SIPp:variable-high-port to S-IP:source-port instead of using 5060 as source 
port. This seems very strange to me, the SIPp source port gets variable, but 
the specified sending address:port is not used, also not when giving another IP 
address as rsa-destination. So, using the rsa-option has an effect, but not 
really the expected one.

Anybody knowing how to solve this problem with SIPp?

  Best regards,

  MarcVD


(-: from Marc VAN DIEST (BELGACOM) ;-)


-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/___
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users