I tried sipsak first on win xp and no luck there, then installed,
compiled sipsak on the asterisk server itself, disable iptables before
running these tests, still no luck. 

Perhaps I am doing something wrong, but I see no pop-ups on the polycom
501 with 3.1 firmware for one thing, secondly, I am getting an error
header back from sipsak, possibly from the ip phone itself:

Following is what I have tried:

My phone's ip is static and its set to:192.168.10.100
My asterisk server is 192.168.10.5 and I also tried 127.0.0.1 and made
no difference
My test extension (of the polycom 501 phone) is 400

And also I believe I need to enable the proper setting in the phone's
config file so the phone can respond to these warning headers:

...
<voIpProt>
 <SIP
  voIpProt.SIP.header.warning.enable="1"
  voIpProt.SIP.header.warning.codes.accept="399">
  <alertInfo voIpProt.SIP.alertInfo.1.value="Auto Answer"
voIpProt.SIP.alertInfo.1.class="3"/>
 </SIP>
</voIpProt>
...

My sipsak command:

[EMAIL PROTECTED]:~/sipsak $ sipsak -vvvvv -f warn.dat -s sip:[EMAIL PROTECTED] 
-G
-a 654321
fqdnhostname: 127.0.0.1
warning: could not find this '$dsthost$' replacement string in message
warning: could not find this '$srchost$' replacement string in message
warning: could not find this '$port$' replacement string in message
warning: could not find this '$user$' replacement string in message
our Via-Line: Via: SIP/2.0/UDP
127.0.0.1:32843;branch=z9hG4bK.0c0c9c79;rport;alias

New message with Via-Line:
NOTIFY sip:[EMAIL PROTECTED]:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:32843;branch=z9hG4bK.0c0c9c79;rport;alias
Via: SIP/2.0/UDP 127.0.0.1
From: <sip:[EMAIL PROTECTED]>
To: <sip:[EMAIL PROTECTED]>
Warning: 399 192.168.10.100 "The sky is falling"
Date: Sat, 01 Nov 2008 22:35:06 GMT
Call-ID: [EMAIL PROTECTED]
CSeq: 1300 NOTIFY
Contact: <sip:[EMAIL PROTECTED]>
Content-Length: 0



request:
NOTIFY sip:[EMAIL PROTECTED]:5060 SIP/2.0
Via: SIP/2.0/UDP 127.0.0.1:32843;branch=z9hG4bK.0c0c9c79;rport;alias
Via: SIP/2.0/UDP 127.0.0.1
From: <sip:[EMAIL PROTECTED]>
To: <sip:[EMAIL PROTECTED]>
Warning: 399 192.168.10.100 "The sky is falling"
Date: Sat, 01 Nov 2008 22:35:06 GMT
Call-ID: [EMAIL PROTECTED]
CSeq: 1300 NOTIFY
Contact: <sip:[EMAIL PROTECTED]>
Content-Length: 0


send to: UDP:192.168.10.5:5060

message received:
SIP/2.0 489 Bad event
Via: SIP/2.0/UDP
127.0.0.1:32843;branch=z9hG4bK.0c0c9c79;alias;received=192.168.10.5;rpor
t=32843
Via: SIP/2.0/UDP 127.0.0.1
From: <sip:[EMAIL PROTECTED]>
To: <sip:[EMAIL PROTECTED]>;tag=as0bd1c574
Call-ID: [EMAIL PROTECTED]
CSeq: 1300 NOTIFY
User-Agent: Asterisk PBX
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
Supported: replaces
Content-Length: 0



** reply received after 0.214 ms **
   SIP/2.0 489 Bad event
   final received 

If anyone notices anything that is obviously wrong or out of place, let
me know what it is, maybe its staring me right in my face and I am not
seeing it...

Thanks.
Elliott


> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On 
> Behalf Of Simon P. Ditner
> Sent: Thursday, October 30, 2008 10:40 PM
> To: Elliott Jeyaseelan
> Cc: Toronto Asterisk UG
> Subject: Re: [on-asterisk] Polycom 3.1 firmware pop-up 
> notification on phones display
> 
> I would likely use "sipsak", which is a command line tool for 
> crafting sip messages. It says in that PDF that only warning 
> codes 300 to 399 are supported.
> 399 is the generic warning parameter (see the SIP RFC3261, 
> section 20.43 on 'Warning'), so it would likely go something 
> like this (I have not tried it yet):
> 
> sip endpoint: [EMAIL PROTECTED]:5060
> sip endpoint password: abc123
> sip server: 192.168.0.20:5060
> 
> 192.168.0.100
> 
> ----
> echo 'NOTIFY sip:[EMAIL PROTECTED]:5060 SIP/2.0
> 
> Via: SIP/2.0/UDP 192.168.0.20
> From: <sip:[EMAIL PROTECTED]>
> To: <sip:[EMAIL PROTECTED]>
> Warning: 399 192.168.0.20 "The sky is falling"
> Date: blah
> Call-ID: [EMAIL PROTECTED]
> CSeq: 1300 NOTIFY
> Contact: <sip:[EMAIL PROTECTED]>
> Content-Length: 0
> ' | sipsak -v -f - -s sip:[EMAIL PROTECTED]:5060 -G -a abc123
> ----
> 
> On Thu, Oct 30, 2008 at 12:04 PM, Elliott Jeyaseelan 
> <[EMAIL PROTECTED]> wrote:
> > Anyone?
> >
> >> -----Original Message-----
> >> From: Elliott Jeyaseelan [mailto:[EMAIL PROTECTED]
> >> Sent: Sunday, October 26, 2008 2:07 PM
> >> To: Toronto Asterisk UG
> >> Subject: [on-asterisk] Polycom 3.1 firmware pop-up notification on 
> >> phones display
> >>
> >> Hi,
> >>
> >> I was going thru the new 3.1 series of polycom firmware for the 
> >> soundpoint series IP phones, (301/501/550 etc) and on page 4-72 of 
> >> the Sip 3.1 administrators guide, there is a very short 
> blurp about 
> >> how to display a 3 second notification on the polycom 
> phone's display 
> >> via sip header.
> >>
> >> Has any tried this or have a clue on how to do this from 
> asterisk 1.4?
> >>
> >> The pdf can be viewed from the following link if anyone is 
> interested 
> >> in checking this out, I would be very interested to know 
> how to put 
> >> up a server generated message on the phones display sent from 
> >> asterisk either triggered by an event, time or other:
> >>
> >> http://www.polycom.com/common/documents/support/setup_maintena
> >> nce/produc
> >> ts/voice/spip_ssip_Admin_Guide_SIP_3_1.pdf
> >>
> >> Thanks for any suggestions or ideas.
> >>
> >> Elliott
> >>
> >> 
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional 
> >> commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED] For additional 
> > commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> 
> 
> -- 
> | It ain't what you don't know that gets you into trouble. It's what
> | you know for sure that just ain't so.   -- Mark Twain
> |
> | The Toronto Asterisk Users Group
> | Join the discussion group by visiting http://taug.ca
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to