[Asterisk-Users] OT: Snom 320, displaying text on the screenfrom *

[Franklin Webb]

Sean,
    I can concur as far as the comments here regarding the sipsak
syntax.  We use sipsak to update the display on our phones so our agents
know if they are logged in or logged out.
 
The sipsak syntax we use with good results is:
 
sipsak -M -O deasktop -B "(your message)" -r 5060 -s sip:(phone
exten)@(phone IP)
 
5060 is the port we use.  In the Snom setup I set the port for each
phone to 5060 under the "Advanced" section by putting 5060 in "	Network
identity (port):"
 
It definitely took me a while to get sipsak working properly, but the
good news is once you get it working it is reliable.
 
-Frank Webb
Inter Media Marketing Solutions

----- Original Message ----- 
From: Sean Kennedy <mailto:skennedy at qualitydentists.com>  
To: Asterisk Users Mailing List -
<mailto:asterisk-users at lists.digium.com> Non-Commercial Discussion 
Sent: Thursday, March 09, 2006 7:00 PM
Subject: Re: [Asterisk-Users] OT: Snom 320, displaying text on the
screenfrom *

I have that set, but for some reason I get errors when I try sipsak, and
nothing comes through to the phone:



sipsak -M -B "test" -s sip:44 at 192.168.1.67 <mailto:44 at 192.168.1.67> 
timeout after 500ms
timeout after 500ms...


Some debugging info:


[root at firewall root]# sipsak -vvv -M -B "test" -s sip:44 at 192.168.1.67
<mailto:44 at 192.168.1.67> 
warning: ignoring -i option when in usrloc mode
fqdnhostname: 192.168.1.1
our Via-Line: Via: SIP/2.0/UDP
192.168.1.1:34213;branch=z9hG4bK.105fb86e;rport;alias

New message with Via-Line:
MESSAGE sip:44 at 192.168.1.67 <sip:44 at 192.168.1.67>  SIP/2.0
Via: SIP/2.0/UDP 192.168.1.1:34213;branch=z9hG4bK.105fb86e;rport;alias
To: sip:44 at 192.168.1.67 <sip:44 at 192.168.1.67> 
Call-ID: 2089538687 at 192.168.1.1 <mailto:2089538687 at 192.168.1.1> 
CSeq: 1 MESSAGE
Content-Type: text/plain
Max-Forwards: 70
User-Agent: sipsak 0.9.5
From: sip:sipsak at 192.168.1.1:34213;tag=7c8bd47f
<sip:sipsak at 192.168.1.1:34213;tag=7c8bd47f> 
Content-Length: 4

test
sending message ...

request:
MESSAGE sip:44 at 192.168.1.67 <sip:44 at 192.168.1.67>  SIP/2.0
Via: SIP/2.0/UDP 192.168.1.1:34213;branch=z9hG4bK.105fb86e;rport;alias
To: sip:44 at 192.168.1.67 <sip:44 at 192.168.1.67> 
Call-ID: 2089538687 at 192.168.1.1 <mailto:2089538687 at 192.168.1.1> 
CSeq: 1 MESSAGE
Content-Type: text/plain
Max-Forwards: 70
User-Agent: sipsak 0.9.5
From: sip:sipsak at 192.168.1.1:34213;tag=7c8bd47f
<sip:sipsak at 192.168.1.1:34213;tag=7c8bd47f> 
Content-Length: 4

test
send to: UDP:192.168.1.67:5060
:
ignoring MESSAGE retransmission
timeout after 500 ms


So I am at a bit of a loss. 

Thanks for your help though, I apprecaite it.  :)

Colin Anderson wrote:


Trick with Sipsak is you have to change the network port to 5060 or
sipsak
messages never hit the right port. In the web interface, Advaced >
Avanced
Network > Network identity (port): change that to 5060 and you should be
good assuming you can figure out sipsak's nasty syntax. hth. 






  _____  




_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --

Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20060310/9ad17a06/attachment.htm