SIP VIA Discrepancy

[ThePhoneMn]

Hi all,

A vendor is trying to setup their Windows Server 2008 to register as a SIP user on my IP Office IP 500V2. All licensing is there, there are also some other 3rd party SIP endpoints registering successfully, as you will see below.

When the Windows server send me a Register, the IP Office does not respond.

This Windows server has 2 NIC cards; 10.37.56.250 and 192.168.10.96. When the server sends a Register request from 10.37.56.250, the Via IP address is 192.168.10.96. I think my issue is right there, but I cannot be %100 sure.

Here are the snips from the trace showing a failure from 10.37.56.250, and a succuss from 10.37.56.13.

Any thoughts on whether this is causing IPOffice to ignore?

603141003mS SIP Rx: UDP 10.37.56.250:5060 -> 10.37.56.2:5060
REGISTER sip:10.37.56.2;ttl=3 SIP/2.0
From: <sip:8500@10.37.56.250>;tag=3e27938-0-13c4-50022-656b2-13e130c2-656b2
To: <sip:8500@10.37.56.250>
Call-ID: 36f9ff0-0-13c4-50022-656b2-7baeb8e4-656b2
CSeq: 1 REGISTER
Via: SIP/2.0/UDP 192.168.10.96:5060;branch=z9hG4bK-656b2-18c2aacf-2cac1dec
Max-Forwards: 70
Supported: replaces
Expires: 3600
Contact: <sip:8500@10.37.56.250>
Content-Length: 0


603171264mS SIP Rx: UDP 10.37.56.13:5060 -> 10.37.56.2:5060
REGISTER sip:10.37.56.2;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.37.56.13:5060;rport;branch=z9hG4bKPj6Z
Max-Forwards: 70
From: <sip:8199@10.37.56.2>;tag=l1r6c9vED-27T7q4wrMA9u3-DtxSfZjz
To: <sip:8199@10.37.56.2>
Call-ID: AotDFWez14wtLdQAc5f33vRi6LYljvcl
CSeq: 56675 REGISTER
User-Agent: Avaya B179 2.3.0
Contact: <sip:8199@10.37.56.13:5060;ob>
Expires: 1800
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Content-Length: 0


Been there, done that

 

[janni78]

SIP Registrar not enabled in the LANx -> Voip tab?

"Trying is the first step to failure..." - Homer

 

[ThePhoneMn]

The first thing I went for was the VoIP tab, thinking SIP Registrar or Remote SIP... They were both ticked. We have other SIP devices registered and working also.

Been there, done that

 

[janni78]

What application on the windows server is trying to register?


"Trying is the first step to failure..." - Homer

 

[amriddle01]

If you have SIP devices registered you know the IPO side is correct, the server is giving out incorrect information, that's what you need to fix first, if once corrected it doesn't work then look deeper

 

[ThePhoneMn]

The application is called Distributed Dial-a-Script/RxCall.

From Googling the interwebs, it seems the Windows Server with 2 NIC cards could be causing the issue. Without access to it, all I can do is send links for them to read. amriddle is correct, I told them it is not the IPOffice, and their first response was, "Fine, we'll just call Avaya". Now that's funny!

Been there, done that

 

[derfloh]

Let us know what AVAYA told them. I don't AVAYA will talk to them...