Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SCN (IPO_VoiceNetworking) 50795 errors

Status
Not open for further replies.

daz306td

Technical User
Mar 6, 2007
8
GB
Does anyone have experience of implementing Avaya IP Office (500) systems hosted either side of R65?

I'm recieving errors with the UDP packet IPO_VoiceNetworking (port 50795) used for small community networking. The R65 box reports "message_info: Server to client packet of an old UDP session", checking the protocols associated to the IPO_VoiceNetworking service is was bound to 'none'.

If I change this to a SIP protocol I see the following on the firewall "Attack: Malformed SIP datagram Attack Information: Invalid or no 'CSEQ' field"

I just dont seem to be able to route this community networking traffic and I'm wondering if theres a misconfigration somewhere so that my firewall will except the IPO_VoiceNetworking 50795 traffic ?

Something missing in my IP office configuration (the Invalid or no 'CSEQ' field message leads me to believe this) or mis-configured protocols on the firewall I'm not sure ?

thanks in advance
 
Is there a VPN tunnnel between the IPO's?

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
Nope. They are on different sites separated by a private circuit. So to expand on that my config is:


FW1----------------------FW2
10.8.250.1 10.7.250.1
| |
| |
| |
| |
AvayaSystem1 AvayaSystem2
10.8.250.5 10.8.250.1

FW1 on site one and FW2 on site two. thanks.
 
Then it will not work, they must be in the same LAN or thru VPN.

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________
 
Can I ask why? Everything else routes fine I dont understand why a VPN is necessary
 
you network config is wrong, private circuit is fine as long as you allow all traffic.



You have system1 on 10.8.250.5 which will have a default route of 10.8.250.1, this is fine,

But system2 on 10.8.250.1 with default route of 10.7.250.1.
1st off this is the same ip as FW1??? second, how can it get to 10.7.250.X if it is on 10.8.250.x subnet??? put the 2nd IPO on .7 subnet and use default route FW2 and it should be fine.
 
Sorry! Typo !

FW1----------------------FW2
10.8.250.1 10.7.250.1
| |
| |
| |
| |
AvayaSystem1 AvayaSystem2
10.8.250.5 10.7.250.1
 
FW1----------------------FW2
10.8.250.1 10.7.250.1
| |
| |
| |
| |
AvayaSystem1 AvayaSystem2
10.8.250.5 10.7.250.5

increased UDP timeout on firewall for the serivce IPO_VoiceNetworking 50795 - seems to have improved things
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top