0.9.x has an issue where outgoing messages don't go out on the incoming interface, but rather the main. This also holds for source port used when listening on multiple ports. The trace will show this if this is the issue you see.
2.x automatically stores and uses correct interface and port. You can also force source interface and port. g-)
------- Original message ------- From: Arun Kumar arunvoip@gmail.com Cc: serusers@lists.iptel.org, users@openser.org Sent: 28.12.'07, 19:15
- Are you updating the port to 5070 for UA B in your configuration.
yes
- Are you sure that cisco is not blocking incoming traffic for 5070.
Maybe its allowing only outgoing traffic.
I've configured my cisco to block udp/tcp 5060 only rest traffic is
allowed , that is why I'm able to reg. on port 5070 and call users who are on 5060 but not rev.
thanks
arun
-Jai
On Dec 28, 2007 9:52 AM, Arun Kumar arunvoip@gmail.com wrote: Hi,
how do I run ser/openser on multiple ports. ?
I've configured my ser with two listen stat. listen = ip:5060 listen = ip:5070
UA:5070 -------> Cisco (Blocked 5060) --------> SER -------------> UB:5060
UA is able to call UB, but UB is not able to call UA, I know 5060 is
blocked but it should goto 5070 ? please guide on this ?
Thanks,
Arun
Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers