Hi Guys,
I'm hoping someone will be able to help with an issue that we are having with a 1608 over a site to site IPSEC VPN.
It is an IP500v2, with all 16/96 series handsets. They have just opened a new site half a mile down the road, leased line in each, and an IPSEC VPN between the two. We unfortunately don't provide the connectivity or manage the VPN or any of the network kit.
There are no issues with the tunnel itself, it doesn't drop, it passes all of their data traffic fine, good bandwidth and latency etc. The phone registers fine, can make a call, and gets perfect audio quality. However after exactly 1 minute and 42 seconds, without fail, the handset re-registers itself. If no call is in progress it takes a few seconds, if a call is in progress then the call cuts off and handset reboots.
The IT company cannot find any issues, and is asking for logs from the phone to say what traffic it is receiving unexpectedly, or what traffic it is not receiving that it should be, etc. in order for this to happen. As far as I can see there is no way to export logs from the phone, so I have done a Monitor trace with default filters plus all H323 options. I will post the trace after this. I am no expert on Monitor and the various messages it spews out, I can usually work out what is going wrong one way or another, but with H323 signalling I am at a loss. I have looked through the knowledge base, but cannot find anything that gives me enough detail, either on Monitor, or H323, to decode what I am seeing. A few things that jump out at me are:
17:21:17 1700437mS H323Evt: RRQ --- CallSigProtocol is H323AnnexL_P. Go for Avaya 4600IP phone
17:21:17 1700437mS H323Evt: RRQ --- Treat this as a forced login, the phone was probably rebooted (same_cs_addr 1)
17:21:17 1700438mS H323Evt: GK: Unregister endpoint CustomerName_5df276a27b337860 for extension 612 reason 4
17:21:17 1700438mS CMExtnEvt: Test Phone:612 ExtnFault now 1
17:21:17 1700439mS CMExtnTx: v=612, p1=8071
And
17:21:17 1700365mS H323Evt: Recv: RegistrationRequest 192.168.52.80; Endpoints registered: 52; Endpoints in registration: 0
17:21:17 1700366mS H323Evt: RRQ --- keep-alive rejected (endpoint is currently not registered)
Does this mean anything to anyone? I'm thinking either some keepalive traffic is being blocked, or the extension is not fully registering and the IP is trying to register?
Full trace to follow; it was taken a few seconds before the phone started re-registering, and stopped a few seconds after it finished.
Any help on this would be very much appreciated.
Thanks in advance for your help.
Joe
Joe Newton
I'm hoping someone will be able to help with an issue that we are having with a 1608 over a site to site IPSEC VPN.
It is an IP500v2, with all 16/96 series handsets. They have just opened a new site half a mile down the road, leased line in each, and an IPSEC VPN between the two. We unfortunately don't provide the connectivity or manage the VPN or any of the network kit.
There are no issues with the tunnel itself, it doesn't drop, it passes all of their data traffic fine, good bandwidth and latency etc. The phone registers fine, can make a call, and gets perfect audio quality. However after exactly 1 minute and 42 seconds, without fail, the handset re-registers itself. If no call is in progress it takes a few seconds, if a call is in progress then the call cuts off and handset reboots.
The IT company cannot find any issues, and is asking for logs from the phone to say what traffic it is receiving unexpectedly, or what traffic it is not receiving that it should be, etc. in order for this to happen. As far as I can see there is no way to export logs from the phone, so I have done a Monitor trace with default filters plus all H323 options. I will post the trace after this. I am no expert on Monitor and the various messages it spews out, I can usually work out what is going wrong one way or another, but with H323 signalling I am at a loss. I have looked through the knowledge base, but cannot find anything that gives me enough detail, either on Monitor, or H323, to decode what I am seeing. A few things that jump out at me are:
17:21:17 1700437mS H323Evt: RRQ --- CallSigProtocol is H323AnnexL_P. Go for Avaya 4600IP phone
17:21:17 1700437mS H323Evt: RRQ --- Treat this as a forced login, the phone was probably rebooted (same_cs_addr 1)
17:21:17 1700438mS H323Evt: GK: Unregister endpoint CustomerName_5df276a27b337860 for extension 612 reason 4
17:21:17 1700438mS CMExtnEvt: Test Phone:612 ExtnFault now 1
17:21:17 1700439mS CMExtnTx: v=612, p1=8071
And
17:21:17 1700365mS H323Evt: Recv: RegistrationRequest 192.168.52.80; Endpoints registered: 52; Endpoints in registration: 0
17:21:17 1700366mS H323Evt: RRQ --- keep-alive rejected (endpoint is currently not registered)
Does this mean anything to anyone? I'm thinking either some keepalive traffic is being blocked, or the extension is not fully registering and the IP is trying to register?
Full trace to follow; it was taken a few seconds before the phone started re-registering, and stopped a few seconds after it finished.
Any help on this would be very much appreciated.
Thanks in advance for your help.
Joe
Joe Newton