Displaying 5 results from an estimated 5 matches for "2944030".
2006 Jun 26
7
'500 Internal Server' Error on SIP NOTIFY
...'re using 1.2.9, but it's been ocurring for quite some time. We have about 35 phones and it's happening on most (also on the few running SIP software 1.6.6).
SIP Software version: 1.6.3.0067
BootROM version: 2.6.2.0032
Reliably Transmitting (no NAT) to xxx.187.128.95:5060:
NOTIFY sip:2944030@ua1.ipt.oneeighty.com SIP/2.0
Via: SIP/2.0/UDP xxx.187.142.203:5060;branch=z9hG4bK4d777013;rport
From: <sip:2944026@ua1.ipt.oneeighty.com>;tag=as6fd80d1b
To: "Front Desk" <sip:2944030@ua1.ipt.oneeighty.com>;tag=3B576862-120A3007
Contact: <sip:2944026@xxx.187.142.203>
Cal...
2006 Jun 26
1
Email notification
...9;s been ocurring for quite some time. We have about 35 phones and it's happening on most (also on the few running SIP software 1.6.6).
>
> SIP Software version: 1.6.3.0067
> BootROM version: 2.6.2.0032
>
> Reliably Transmitting (no NAT) to xxx.187.128.95:5060:
> NOTIFY sip:2944030@ua1.ipt.oneeighty.com SIP/2.0
> Via: SIP/2.0/UDP xxx.187.142.203:5060;branch=z9hG4bK4d777013;rport
> From: <sip:2944026@ua1.ipt.oneeighty.com>;tag=as6fd80d1b
> To: "Front Desk" <sip:2944030@ua1.ipt.oneeighty.com>;tag=3B576862-120A3007
> Contact: <sip:2944026@xxx...
2006 Mar 30
1
'sip show users' shows NAT RFC3581
Ok, this is highly confusing.
hestia*CLI> sip show users
Username Secret Accountcode Def.Context ACL NAT
2944030 2944030 oneeighty_start No RFC3581
2944035 2944035 oneeighty_start No RFC3581
sip users (type=friend) are in sip.conf. I have nat=no against all of them. Why does a 'sip show users' have R...
2006 May 11
4
'extensions reload' clears Regextens
...2944022) [SIP]
'2944023' => 1. Noop(2944023) [SIP]
'2944026' => 1. Noop(2944026) [SIP]
'2944029' => 1. Noop(2944029) [SIP]
'2944030' => 1. Noop(2944030) [SIP]
'2944033' => 1. Noop(2944033) [SIP]
'2944034' => 1. Noop(2944034) [SIP]
'2944035' => 1. Noop(2944035)...
2006 Jun 09
1
Polycom subscriptions
...P Request: REGISTER sip:ua1.ipt.twoeighty.com
5 0.211432 219.187.142.203 -> 219.187.128.95 SIP Status: 100 Trying (1 bindings)
6 0.237595 219.187.142.203 -> 219.187.128.95 SIP Status: 200 OK (1 bindings)
7 3.987556 219.187.142.203 -> 219.187.128.95 SIP Request: NOTIFY sip:2944030@219.187.128.95 (text/plain)
8 4.087355 219.187.128.95 -> 219.187.142.203 SIP Status: 200 OK
The phone is not sending a SIP subscription message for the watched buddy in the directory.
This worked previously in SIP software version 1.6.3.
We completely upgraded the sip and phone1 xml files...