< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

RE: [reSIProcate] Trouble listening on non-standard port


That's odd - it's fairly common thing to do.  There are no known bugs
that I know of.  Does anything appear in the logging?

Scott

> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-
> devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Dale R. Worley
> Sent: Thursday, November 17, 2005 6:39 PM
> To: Resiprocate-devel
> Subject: [reSIProcate] Trouble listening on non-standard port
> 
> I'm running into trouble with dum/resiprocate when I have it listen on
a
> non-5060 port.  It seems simple enough:
> 
>    dum.addTransport(resip::UDP, mUdpPort);
> 
> and when I run the code, netstat shows that my program is listening on
> the port I specify.  But when an INVITE is sent to that port (and I
can
> see the packet via Ethereal), the onNewSession
> (resip::ServerInviteSessionHandle, ...) method is not called.  But
when
> I set mUdpPort to 5060, everything works as expected.  Is this a known
> bug and/or is there something else I need to do to get Dum to listen
on
> a non-standard port?
> 
> Dale
> 
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel