svwar -e does not accept more than 10 digits number

[GoogleCodeExporter]

What steps will reproduce the problem?
1. C:\Python27\sipvicious-0.2.7>svwar.py -eXXXXXXXX1000-XXXXXXXX1010 10.10.10.10
2. XXXXXXXX is the 8 digits prefix of a 12 digits number ending with 1000, 1001 
... and number are registered on PBX
3. 10.10.10.10 is the IP of the PBX
The scenario is possible when the subscribers are registered with full DN 

What is the expected output? What do you see instead?
The expected output:
| Extension    | Authentication |
---------------------------------
| XXXXXXXX1003 | noauth         |
| XXXXXXXX1002 | noauth         |
| XXXXXXXX1001 | noauth         |
| XXXXXXXX1000 | noauth         |
| XXXXXXXX1007 | noauth         |
...

I see instead:

Traceback (most recent call last):
  File "C:\Python27\sipvicious-0.2.7\svwar.py", line 517, in <module>
    extensionstotry = getRange(options.range)
  File "C:\Python27\sipvicious-0.2.7\svhelper.py", line 116, in getRange
    numericrange.append(xrange(startport,endport))
OverflowError: Python int too large to convert to C long

What version of the product are you using? On what operating system?
Windows XP, Python2.7, sipvicious 0.2.7

Please provide any additional information below.

I solved this problem by modifying line 116 in file svhelper.py. I replaced 
xrange(startport,endport)
with
itertools.islice(itertools.count(startport, 1), (endport-startport))
(also "import itertools" in the beginning)

I see the same issue in line 126 same file.

Original issue reported on code.google.com by achro...@gmail.com on 12 Apr 2012 at 12:09

[GoogleCodeExporter]

I am having issues with this myself. I am a VOIP engineer at my company and we 
are getting reports of callers with the name sipvicious calling them. I am 
trying to format a SIP message using sipvicious and am finding that since we 
register with full DN we are only able to receive calls when the SIP TO header 
contains a full 10 digit DN. How do I make this work for testing our security?

Original comment by jaimechieng@gmail.com on 16 Apr 2013 at 6:16

[GoogleCodeExporter]

Original comment by san...@enablesecurity.com on 17 Apr 2013 at 9:20

• Changed state: Accepted

[GoogleCodeExporter]

Could you please update from svn and test the latest fix for this?

thanks,

Original comment by san...@enablesecurity.com on 17 Apr 2013 at 9:21

• Changed state: Fixed

[GoogleCodeExporter]

Could you please update from svn and test the latest fix for this?

thanks,

Original comment by san...@enablesecurity.com on 17 Apr 2013 at 9:21