PPTP VPN and Failure to Register on SIP

[crhoads71]

I get the following error when attempting to connect via SIP over our PPTP VPN. This seemed to work well when I was running PFSense 1.23, but I upgraded to PFSense 2.0 a few weeks ago and the Avaya Softphone won't work over the PPTP VPN. I have a rule that allows all traffic on all protocols across the VPN. The Softphone works on the local lan. Any ideas would be appreciated.

3183891mS SIP Rx: UDP 192.168.5.16:9155 -> 192.168.1.50:5060
REGISTER sip:192.168.1.50 SIP/2.0
Via: SIP/2.0/UDP 192.168.5.16:9155;branch=z9hG4bK-d8754z-514b95c2f4bb7957-1---d8754z-;rport
Max-Forwards: 70
Contact: <sip:5505@192.168.5.16:9155;rinstance=96058599eb179a2c;transport=udp>
To: "username"<sip:5505@192.168.1.50>
From: "username"<sip:5505@192.168.1.50>;tag=2465af37
Call-ID: MGY2NGE4YjdkYjkzNzFmZmUwMTc1NDkwZWVlZGI2MmM
CSeq: 7 REGISTER
Expires: 3600
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO
User-Agent: IP Office Softphone 6.1 3.2.3.15 build 64595
Content-Length: 0

3183896mS SIP Tx: UDP 192.168.1.50:5060 -> 192.168.5.16:9155
SIP/2.0 500 Server Internal Error
Via: SIP/2.0/UDP 192.168.5.16:9155;branch=z9hG4bK-d8754z-514b95c2f4bb7957-1---d8754z-;rport
From: "username" <sip:5505@192.168.1.50>;tag=2465af37
To: "username" <sip:5505@192.168.1.50>;tag=ffa7ed42ec3ee2de
Call-ID: MGY2NGE4YjdkYjkzNzFmZmUwMTc1NDkwZWVlZGI2MmM
CSeq: 7 REGISTER
User-Agent: IP Office 8.0 (16)
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, SUBSCRIBE, REGISTER, PUBLISH
Supported: timer
Content-Length: 0

3183896mS Interface Queue: v=(null) WAN
IP Header info - Dst=192.168.5.16 Src=192.168.1.50 vl=0x45 tos=0x88 len=510 id=0x1c1e
ttl=99 flg=0 off=0 pcol=17(UDP) sum=0xb1b6
UDP Header info - DstPort=9155 SrcPort=5060(SIP) Len=490 Sum=0x0000
0000 53 49 50 2f 32 2e 30 20 35 30 30 20 53 65 72 76 SIP/2.0 500 Serv
0010 65 72 20 49 6e 74 65 72 6e 61 6c 20 45 72 72 6f er Internal Erro

 

[amriddle01]

If it was upgrading the VPN client stopped it working then the system and software is just fine, not sure what we can do to help

 

[crhoads71]

It was the VPN Server that was upgraded, and maybe someone else has experienced this?

Are there any settings in the IP Office that restrict what subnets it will register?