can the sip trunk port be set to 5060 for OXE invite?

murraya · Post by **murraya** » 15 Feb 2010 05:31

Hi all, just playing with a ALG but it seems to route calls back to the source port. in the example attached the setup message from the OXE (h1.301.34) is sent from port 10002 to destination port 5060. No problem if the SIP provider is connected directly as they reply on port 5060.
When I put the ALG between then the following happens.. (addresses are just for example and nor real)
setup from oxe 192.168.1.1 on port 10002 to 10.1.1.1 port 5060

ALG sends setup from 10.1.2.1 port 5060 to 10.1.1.1 port 5060

Provider replies trying 10.1.1.1 port 5060 to 10.1.2.1 port 5060

Now the issue.. the ALG knows the session so it sends the trying to the oxe from 10.1.1.1 port 5060 to 192,168.1.1 port 10002

The oxe is expecting the reply on port 5060 but because it is being sent on port 10002 the call fails.

note that the screen shot is just to show the original port data.
what I want to do is to make the oxe always send invites from port 5060. is this possible?

murraya · Post by **murraya** » 23 Feb 2010 20:24

someting strange happened

all of asudden I could see that calls being made from the OXE were now using port 5060, oh happy days I thought:rolleyes:
But what I found was in reality when the sip motor starts and calls are made they go out on ports 10002 upwards. however if the sip motor is restarted and a call is sent into the OXE on port 5060 then all out going calls after that are on 5060.

Still not sure whats going on but in the lab I can make it work as long as the first call is generated from outside to the OXE.

I will update if I find any other weird stuff.
P.S. I have changed the software to 9.1 i1.605.12 and the behaviour is still the same.