Jump to content

FaxSIP.dll


cbehh

Recommended Posts

Hello @all,

 

a couple of days we're using a SIP trunk wich works like a charm but the FaxServer isn't working anymore.

In the Trace I've found the following (extract):

 

Compression configuration object created; algorithm = 0
04 11:08:09.871 002dc0 Inf2 SIP        0479EB18 00000000 TransportSelector.cxx:93                () No compression library available
04 11:08:09.872 002dc0 Info SIP        0479EB18 00000000 UdpTransport.cxx:45                     () Creating UDP transport host= port=61000 ipv4=1
04 11:08:09.872 002dc0 Inf2 SIP        0479EB18 00000000 InternalTransport.cxx:89                () Creating fd=1620 V4/UDP
04 11:08:09.872 002dc0 Inf2 SIP        0479EB18 00000000 InternalTransport.cxx:97                () Binding to 0.0.0.0
04 11:08:09.872 002dc0 Info SIP        0479EB18 00000000 Transport.cxx:188                       () Some other error (10048): Unknown error
04 11:08:09.872 002dc0 *Err SIP        0479EB18 00000000 InternalTransport.cxx:105               () [ V4 0.0.0.0:61000 UDP target domain=unspecified mFlowKey=0 ] already in use
04 11:08:09.872 002dc0 Inf2 SIP        0479EB18 00000000 BaseException.cxx:17                    () BaseException at InternalTransport.cxx:106 port already in use
04 11:08:09.872 002dc0 *Err SIP        0479EB18 00000000 SipStack.cxx:185                        () Failed to create transport: V4 UDP 61000 on ANY
04 11:08:09.872 002dc0 Inf2 SIP        0479EB18 00000000 SipStack.cxx:97                         () SipStack::~SipStack()
04 11:08:09.872 002dc0 Inf2 SIP        0479EB18 00000000 Security.cxx:915                        () BaseSecurity::~BaseSecurity
04 11:08:09.872 002dc0 Info SIP        0479EB18 00000000 Socket.cxx:113                          () INVALID_SOCKET handle
04 11:08:09.872 002dc0 Info SIP        0479EB18 00000000 Socket.cxx:113                          () INVALID_SOCKET handle
04 11:08:09.873 002dc0 *Err SwSIP      0479EA38 00000000 CSIPSessionHandler::Init                () All configured SIP ports are in use
04 11:08:09.873 002dc0 Info SwSIP      0479EA38 00000000 CSIPSessionHandler::Stop                () SIP Session Handler thread prepared to stop...
04 11:08:09.873 002dc0 *Err FaxSIP     047779F8 00000000 FaxSIPInterf::Initialize                () Could not initialize SIP session handler!
04 11:08:09.974 002dc0 *Err FaxSrv     00000000 00000000 CFaxSIPWrp::InitializeFaxSIP            () Could not initialize FaxSIPInterface object!
04 11:08:09.974 002dc0 *Err FaxSrv     00000000 00000000 CFaxSIPWrp::InitializeFaxSIP            () Fax SIP initialization failed

 

I've read that there's a configuration tweak with LowerBoundSipPort and UpperBoundSipPort in Registry to Change that port.

After hours of searching I'll give up. Still have'nt found where to put those Keys in Registry.

 

Any hint?

 

I'm just wondering about the FaxServer (and some other Parts):

1.)  If there are other Trunks existing so why is FaxSRV failing only by SIP? He could start and use the other Trunks as before

2.)  Is'nt it better to spend a Little GUI fresh up to make such parts configurable

 

Thanks in advance for any hint about that issue.

 

(and even if we're running straight and fast to next Christmas time - a happy new year to all of you :-))

 

Chris

Link to comment
Share on other sites


  • Most Valued User

Did see that on machines running DNS on the same machine as swyxware. Did u already try KB3778?

 

In case u don't have partnernet access:

 

Server 2003: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Reg key Name: ReservedPorts
Registry Key Typ: Multi-String Wert (REG_MULTI_SZ)
Swyx values: 50000-56000, 65000-65002, 61000, 65010
Keep existing values!
each portrange has to be in a separate line
See also: Microsoft kb812873
 
Server 2008 and newer:
Portrange is the same as above
Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and have taken note of our Privacy Policy.
We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.