SIP 3c3108 with 6.5.22

[mswann60]

The Wire shark .pcap file we have is for the remote location. Everything step shows that the traffic is on port 5060.  I can upload the file to be reviewed.

The firewall vendor verified that the packets were bi-directional though the appliance. They did a pcap scan remotely and have stated that the firewall is performing correctly in this application.

We do not have a service contract on the NBX V3000, but this this point, we would be willing to spend some money to resolve this. I am running to the end of my skill set and this problem scared off the network support that I had.

I am open to suggestions.

[bosoxfan]

another suggestion:

did you create a user on the NBX with that extension number and password?

that would cause a 404 Not FOund also since the extension number does not exist on the NBX.

[mswann60]

I set up the user configuration like you stated in post #4  with our assigned extension number and it registered fine in network. I created a new SIP profile based off of the working "in network" profile. All ihave done is experiment with our Static Sip IP and the handset's sip domain and outbound address settings. I then tied it to a new network profile (remote) and have been try empirically to get it to work ever since.

[mswann60]

So how do we open a case? We do not have an active service contract.

On another issue, is there a way to directly look at the packets in the NBX? Unfortunately, our firewall defeats the wireshark.
Please respond. We have been struggling 2.5 months now trying to get WAN SIP connectivity.

[bosoxfan]

Call 800-876-3266 and they can tell you how to log a call.

No way to look at NBX packets directly.. most customers will mirror a port on the switch that the NBX is attached to and attach a PC to that port and run wireshark... .or put a hub with a PC in between the

NBX and the switch.

One other thing that we never mentioned.. the NBX must be in SIP mode, is it?

[mswann60]

HP said the unit is out of warranty, therefore unsupported.

A hub? Like a base 10 T hub? Can you even get those anymore?  I have never been inside my switch, but I think I can handle this.

Yes the NBX is in sip mode. The 3018 works fine in LAN. I got Astaro to monitor it remotely. Wireshark apparently does not work with Linux.

The NBX is issuing a 404:

14:41:11.134340 IP (tos 0x0, ttl 64, id 5010, offset 0, flags [none], proto UDP (17), length 546) 192.168.1.15.5060 > 71.108.16.62.5060: SIP, length: 518

SIP/2.0 404 Not Found

From: 112 <sip:112@192.168.1.15:5060>;tag=822837bdb457c2f

To: 112 <sip:112@192.168.1.15:5060>

Call-Id: 752feda1062783bfb5d9eb77a5d54703@192.168.1.18

Cseq: 546185160 REGISTER

Via: SIP/2.0/UDP

192.168.1.18:5060;branch=z9hG4bK0ae859bec;received=71.108.16.62

Date: Thu, 30 Sep 2010 22:40:53 GMT

Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, REGISTER, SUBSCRIBE, NOTIFY

User-Agent: 3Com-SIP-Phone/v2.6.0 (sipXphone) (VxWorks)

Accept-Language: en

Supported: replaces

Content-Length: 0

[bosoxfan]

hi. Since the phone does register when it is in the LAN, the x112 is ok.

We have seen issues where the firewall changes the packet if the firewall is "sip enabled"... is the firewall

SIP enabled?

also, I am presuming that the 192.168.1.15 is the nbx in the above..

[mswann60]

Bosox,

Yes its sip enabled. Its an Astaro ASG120 running 7.507. Yes the NBX is 192.168.1.15.

Do you know a competent tech out in southern Californa we could contact?

Thanks,

Mike

[bosoxfan]

Can you disable SIP on the firewall and see if it registers?

It should.

We have seen issues where "SIP enabled" firewalls are acting as the proxy and changing the SIP packets.

When SIP has been disabled, everything was fine.

Sorry, I am not allowed to give out tech names.

[mswann60]

We did that yesterday, it did not register.