[Blink] How to register Blink without using full domain name

Kerry Larmer kerry at letsengage.com.au
Sun May 8 12:14:02 CEST 2011


Ok, thanks for the feedback.  We’ll check it out.



On 8/05/11 8:08 PM, "Adrian Georgescu" <ag at ag-projects.com> wrote:

A media server will do as well, but is overkill for what you want.

There is very little to change in sip-audio-session to playback a file after answering the call. Look inside the sample scripts for when DTMF tones are played.

Regards,
Adrian

On May 8, 2011, at 10:42 AM, Kerry Larmer wrote:

Ok, so no answer machine on Linux either then?

Was hoping there was a SIP end point that supported playing of a configurable answer machine message on the local PC out of the box, as that would avoid any programming effort and hence any additional delay in scheduling the work.

If not,  I’ll have to go back to our development team for SIP SIMPLE.

Some-one else has suggested SEMS (http://www.iptel.org/sems) so we’ll check that out too.

Thanks


On 8/05/11 6:29 PM, "Adrian Georgescu" <ag at ag-projects.com <x-msg://11/ag@ag-projects.com> > wrote:

What you want can be easily scripted using SIP SIMPLE client SDK command line tools. You need to do a bit a programming though.

The command line clients can auto-answer a call and play files.

http://sipsimpleclient.com/wiki/SipTesting

Regards,
Adrian


On May 8, 2011, at 9:49 AM, Kerry Larmer wrote:

Ah, right....that’s a pity, as its probably going to kill the use of Blink in the scenario we need it.

Although, I guess we could consider changing the OS to Linux? Is it feature available on Linux and will we be able to replace the recording with a specific file, in the way described?

We are looking for a solution where a SIP end point simply answers test calls and plays a specific message, so it can act as a virtual Agent across an international data link.  We are then sending calls via a third party testing application that uses speech recognition to determine whether the calls experience any quality issues.  A call is made every 15 minutes and if any words are not heard correctly and completely, due to jitter or delay for example, an alert is raised.  All of these test calls are also recorded, so you can play it back later to help determine where any underlying issues might lie.

Are you aware of any other easy to set-up and install SIP end pint that might be able to do what we want here?  It doesn’t have to support answer machine necessarily, its just an easy way to get the PC to play a file across the international data link that the testing service can then track and validate.  Perhaps there is a SIP end points that will run a script when a call arrives to answer it and to play a recorded file down the line...?

Thanks for your help
Kerry


On 8/05/11 5:36 PM, "Adrian Georgescu" <ag at ag-projects.com <x-msg://11/ag@ag-projects.com>  <x-msg://40/ag@ag-projects.com <x-msg://40/ag@ag-projects.com> > > wrote:

The answering machine functionality has not been implemented in Windows yet.

Adrian

On May 8, 2011, at 9:21 AM, Kerry Larmer wrote:

Hi

Just wondering if anyone has an answer to this?

Thanks
Kerry


On 6/05/11 11:29 AM, "Kerry Larmer" <kerry at letsengage.com.au <x-msg://11/kerry@letsengage.com.au>  <x-msg://40/kerry@letsengage.com.au <x-msg://40/kerry@letsengage.com.au> >  <x-msg://33/kerry@letsengage.com.au <x-msg://33/kerry@letsengage.com.au>  <x-msg://33/kerry@letsengage.com.au <x-msg://33/kerry@letsengage.com.au> > > > wrote:

HI,

Now we have Blink connected and working, we need to set-up a custom answer machine message, using a specific file recording we have on hand.

I can only find a way to record a custom message directly via the application, not to load an alternative pre-recorded file.

I assume there is a file located somewhere on the PC that we can simply overwrite, to change the default message or custom message?  Do you know where that file is located and what its called so I can overwrite?  We’re using Windows 7.

Thanks for your help
Kerry




On 5/05/11 5:22 PM, "Adrian Georgescu" <ag at ag-projects.com <x-msg://11/ag@ag-projects.com>  <x-msg://40/ag@ag-projects.com <x-msg://40/ag@ag-projects.com> >  <x-msg://33/ag@ag-projects.com <x-msg://33/ag@ag-projects.com>  <x-msg://33/ag@ag-projects.com <x-msg://33/ag@ag-projects.com> > > > wrote:

Blink tries to register to your server but your server does not reply. You have to check your server logs to see why.

Adrian


On May 5, 2011, at 6:59 AM, Kerry Larmer wrote:

Hi Adrian,

We are still having issues trying to register using 82999 at 172.22.22.16 <x-msg://11/82999@172.22.22.16>  <x-msg://40/82999@172.22.22.16 <x-msg://40/82999@172.22.22.16> >  <x-msg://33/82999@172.22.22.16 <x-msg://33/82999@172.22.22.16>  <x-msg://33/82999@172.22.22.16 <x-msg://33/82999@172.22.22.16> > >  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16>  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16> >  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16>  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16> > > > .

We have confirmed we can telnet to 172.22.22.16 on port 5060, so there is no issue from the connectivity point.

We can’t see any connection attempt in the logs for Sip Server 172.22.22.16.

The log is showing the following sequence over and over again, but no specific error:

-
2011-05-05 11:01:31.087000 [blink.exe 4808]: SENDING: Packet 1, +0:00:01.154000
172.22.7.7:49983 -(SIP over UDP)-> 172.22.22.16:5060
REGISTER sip:172.22.22.16 SIP/2.0

Via: SIP/2.0/UDP 172.22.7.7:49983;rport;branch=z9hG4bKPjf89d54dff0544ce9a1aa0afdb58eb895

Max-Forwards: 70

From: "82999" <sip:82999 at 172.22.22.16 <x-msg://11/82999@172.22.22.16>  <x-msg://40/82999@172.22.22.16 <x-msg://40/82999@172.22.22.16> >  <x-msg://33/82999@172.22.22.16 <x-msg://33/82999@172.22.22.16>  <x-msg://33/82999@172.22.22.16 <x-msg://33/82999@172.22.22.16> > >  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16>  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16> >  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16>  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16> > > > >;tag=e96422924e644c9f871d56d785ecf3e2

To: "82999" <sip:82999 at 172.22.22.16 <x-msg://11/82999@172.22.22.16>  <x-msg://40/82999@172.22.22.16 <x-msg://40/82999@172.22.22.16> >  <x-msg://33/82999@172.22.22.16 <x-msg://33/82999@172.22.22.16>  <x-msg://33/82999@172.22.22.16 <x-msg://33/82999@172.22.22.16> > >  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16>  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16> >  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16>  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16> > > > >

Contact: <sip:tknsfcba at 172.22.7.7:49983 <x-msg://11/tknsfcba@172.22.7.7:49983>  <x-msg://40/tknsfcba@172.22.7.7:49983 <x-msg://40/tknsfcba@172.22.7.7:49983> >  <x-msg://33/tknsfcba@172.22.7.7:49983 <x-msg://33/tknsfcba@172.22.7.7:49983>  <x-msg://33/tknsfcba@172.22.7.7:49983 <x-msg://33/tknsfcba@172.22.7.7:49983> > >  <x-msg://77/tknsfcba@172.22.7.7:49983 <x-msg://77/tknsfcba@172.22.7.7:49983>  <x-msg://77/tknsfcba@172.22.7.7:49983 <x-msg://77/tknsfcba@172.22.7.7:49983> >  <x-msg://77/tknsfcba@172.22.7.7:49983 <x-msg://77/tknsfcba@172.22.7.7:49983>  <x-msg://77/tknsfcba@172.22.7.7:49983 <x-msg://77/tknsfcba@172.22.7.7:49983> > > > >

Call-ID: 3dcde9ac2e05453b9dcd4388de8386e0

CSeq: 1 REGISTER

Expires: 600

User-Agent: Blink 0.2.6 (Windows)

Content-Length:  0

--
2011-05-05 11:01:31.087000 [blink.exe 4808]: SENDING: Packet 2, +0:00:01.154000
172.22.7.7:49983 -(SIP over UDP)-> 172.22.22.16:5060
SUBSCRIBE sip:82999 at 172.22.22.16 <x-msg://11/82999@172.22.22.16>  <x-msg://40/82999@172.22.22.16 <x-msg://40/82999@172.22.22.16> >  <x-msg://33/82999@172.22.22.16 <x-msg://33/82999@172.22.22.16>  <x-msg://33/82999@172.22.22.16 <x-msg://33/82999@172.22.22.16> > >  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16>  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16> >  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16>  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16> > > >  SIP/2.0

Via: SIP/2.0/UDP 172.22.7.7:49983;rport;branch=z9hG4bKPje2b6e7beeebe4020b381f3eeafa1e897

Max-Forwards: 70

From: "82999" <sip:82999 at 172.22.22.16 <x-msg://11/82999@172.22.22.16>  <x-msg://40/82999@172.22.22.16 <x-msg://40/82999@172.22.22.16> >  <x-msg://33/82999@172.22.22.16 <x-msg://33/82999@172.22.22.16>  <x-msg://33/82999@172.22.22.16 <x-msg://33/82999@172.22.22.16> > >  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16>  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16> >  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16>  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16> > > > >;tag=7a6e5a8fb4194d4bb997528467a55890

To: <sip:82999 at 172.22.22.16 <x-msg://11/82999@172.22.22.16>  <x-msg://40/82999@172.22.22.16 <x-msg://40/82999@172.22.22.16> >  <x-msg://33/82999@172.22.22.16 <x-msg://33/82999@172.22.22.16>  <x-msg://33/82999@172.22.22.16 <x-msg://33/82999@172.22.22.16> > >  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16>  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16> >  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16>  <x-msg://77/82999@172.22.22.16 <x-msg://77/82999@172.22.22.16> > > > >

Contact: <sip:tknsfcba at 172.22.7.7:49983 <x-msg://11/tknsfcba@172.22.7.7:49983>  <x-msg://40/tknsfcba@172.22.7.7:49983 <x-msg://40/tknsfcba@172.22.7.7:49983> >  <x-msg://33/tknsfcba@172.22.7.7:49983 <x-msg://33/tknsfcba@172.22.7.7:49983>  <x-msg://33/tknsfcba@172.22.7.7:49983 <x-msg://33/tknsfcba@172.22.7.7:49983> > >  <x-msg://77/tknsfcba@172.22.7.7:49983 <x-msg://77/tknsfcba@172.22.7.7:49983>  <x-msg://77/tknsfcba@172.22.7.7:49983 <x-msg://77/tknsfcba@172.22.7.7:49983> >  <x-msg://77/tknsfcba@172.22.7.7:49983 <x-msg://77/tknsfcba@172.22.7.7:49983>  <x-msg://77/tknsfcba@172.22.7.7:49983 <x-msg://77/tknsfcba@172.22.7.7:49983> > > > >

Call-ID: 442222fe593e4a0499b8ac545820e699

CSeq: 7643 SUBSCRIBE

Event: message-summary

Expires: 3600

Accept: application/simple-message-summary

Allow-Events: conference, message-summary, presence, presence.winfo, xcap-diff, refer

User-Agent: Blink 0.2.6 (Windows)

Content-Length:  0



Any assistance you could provide would be greatly appreciated, there must be something simple we are missing still.


Cheers
Kerry


On 4/05/11 9:48 PM, "Adrian Georgescu" <ag at ag-projects.com <x-msg://11/ag@ag-projects.com>  <x-msg://40/ag@ag-projects.com <x-msg://40/ag@ag-projects.com> >  <x-msg://33/ag@ag-projects.com <x-msg://33/ag@ag-projects.com>  <x-msg://33/ag@ag-projects.com <x-msg://33/ag@ag-projects.com> > >  <x-msg://77/ag@ag-projects.com <x-msg://77/ag@ag-projects.com>  <x-msg://77/ag@ag-projects.com <x-msg://77/ag@ag-projects.com> >  <x-msg://77/ag@ag-projects.com <x-msg://77/ag@ag-projects.com>  <x-msg://77/ag@ag-projects.com <x-msg://77/ag@ag-projects.com> > > > > wrote:

You must use only the IP address in the domain part, without the port. Example:

user at 172.22.22.16 <x-msg://11/user@172.22.22.16>  <x-msg://40/user@172.22.22.16 <x-msg://40/user@172.22.22.16> >  <x-msg://33/user@172.22.22.16 <x-msg://33/user@172.22.22.16>  <x-msg://33/user@172.22.22.16 <x-msg://33/user@172.22.22.16> > >  <x-msg://77/user@172.22.22.16 <x-msg://77/user@172.22.22.16>  <x-msg://77/user@172.22.22.16 <x-msg://77/user@172.22.22.16> >  <x-msg://77/user@172.22.22.16 <x-msg://77/user@172.22.22.16>  <x-msg://77/user@172.22.22.16 <x-msg://77/user@172.22.22.16> > > >

To connect to a non-standard port or another protocol than udp to your server, you can set the outbound proxy of your account. Example:

172.22.22.16:5060;transport=udp

Replace the port and protocol accordingly.

Adrian

On May 4, 2011, at 12:45 PM, Kerry Larmer wrote:

HI,

We have a SIP Server within our network that is accessed by IP address and port only.

What is the correct way to register Blink to this?

We’ve been using the following format: “exension at ipaddress:port”

But we’re seeing DNS error in the logs:

-
2011-05-04 16:03:07.636000 [blink.exe 292]: DNS lookup NAPTR 172.22.22.16:5060 failed: DNS record does not exist
2011-05-04 16:03:07.640000 [blink.exe 292]: DNS lookup SRV _sips._tcp.172.22.22.16:5060 failed: DNS record does not exist
2011-05-04 16:03:07.644000 [blink.exe 292]: DNS lookup SRV _sip._tcp.172.22.22.16:5060 failed: DNS record does not exist
2011-05-04 16:03:07.649000 [blink.exe 292]: DNS lookup SRV _sip._udp.172.22.22.16:5060 failed: DNS record does not exist
2011-05-04 16:03:07.657000 [blink.exe 292]: DNS lookup A 172.22.22.16:5060 failed: DNS record does not exist

How can we get around this?  We don’t have a fully qualified DNS name to enter to connect to this SIP Server.


Thanks
Kerry
_______________________________________________
Blink mailing list
Blink at lists.ag-projects.com <x-msg://11/Blink@lists.ag-projects.com>  <x-msg://40/Blink@lists.ag-projects.com <x-msg://40/Blink@lists.ag-projects.com> >  <x-msg://33/Blink@lists.ag-projects.com <x-msg://33/Blink@lists.ag-projects.com>  <x-msg://33/Blink@lists.ag-projects.com <x-msg://33/Blink@lists.ag-projects.com> > >  <x-msg://77/Blink@lists.ag-projects.com <x-msg://77/Blink@lists.ag-projects.com>  <x-msg://77/Blink@lists.ag-projects.com <x-msg://77/Blink@lists.ag-projects.com> >  <x-msg://77/Blink@lists.ag-projects.com <x-msg://77/Blink@lists.ag-projects.com>  <x-msg://77/Blink@lists.ag-projects.com <x-msg://77/Blink@lists.ag-projects.com> > > >
http://lists.ag-projects.com/mailman/listinfo/blink


________________________________
_______________________________________________
Blink mailing list
Blink at lists.ag-projects.com <x-msg://11/Blink@lists.ag-projects.com>  <x-msg://40/Blink@lists.ag-projects.com <x-msg://40/Blink@lists.ag-projects.com> >  <x-msg://33/Blink@lists.ag-projects.com <x-msg://33/Blink@lists.ag-projects.com>  <x-msg://33/Blink@lists.ag-projects.com <x-msg://33/Blink@lists.ag-projects.com> > >  <x-msg://77/Blink@lists.ag-projects.com <x-msg://77/Blink@lists.ag-projects.com>  <x-msg://77/Blink@lists.ag-projects.com <x-msg://77/Blink@lists.ag-projects.com> >  <x-msg://77/Blink@lists.ag-projects.com <x-msg://77/Blink@lists.ag-projects.com>  <x-msg://77/Blink@lists.ag-projects.com <x-msg://77/Blink@lists.ag-projects.com> > > >
http://lists.ag-projects.com/mailman/listinfo/blink
_______________________________________________
Blink mailing list
Blink at lists.ag-projects.com <x-msg://11/Blink@lists.ag-projects.com>  <x-msg://40/Blink@lists.ag-projects.com <x-msg://40/Blink@lists.ag-projects.com> >  <x-msg://33/Blink@lists.ag-projects.com <x-msg://33/Blink@lists.ag-projects.com>  <x-msg://33/Blink@lists.ag-projects.com <x-msg://33/Blink@lists.ag-projects.com> > >
http://lists.ag-projects.com/mailman/listinfo/blink


________________________________
_______________________________________________
Blink mailing list
Blink at lists.ag-projects.com <x-msg://11/Blink@lists.ag-projects.com>  <x-msg://40/Blink@lists.ag-projects.com <x-msg://40/Blink@lists.ag-projects.com> >  <x-msg://33/Blink@lists.ag-projects.com <x-msg://33/Blink@lists.ag-projects.com>  <x-msg://33/Blink@lists.ag-projects.com <x-msg://33/Blink@lists.ag-projects.com> > >
http://lists.ag-projects.com/mailman/listinfo/blink

_______________________________________________
Blink mailing list
Blink at lists.ag-projects.com <x-msg://11/Blink@lists.ag-projects.com>  <x-msg://40/Blink@lists.ag-projects.com <x-msg://40/Blink@lists.ag-projects.com> >
http://lists.ag-projects.com/mailman/listinfo/blink


________________________________
_______________________________________________
Blink mailing list
Blink at lists.ag-projects.com <x-msg://11/Blink@lists.ag-projects.com>  <x-msg://40/Blink@lists.ag-projects.com <x-msg://40/Blink@lists.ag-projects.com> >
http://lists.ag-projects.com/mailman/listinfo/blink
_______________________________________________
Blink mailing list
Blink at lists.ag-projects.com <x-msg://11/Blink@lists.ag-projects.com>
http://lists.ag-projects.com/mailman/listinfo/blink


________________________________
_______________________________________________
Blink mailing list
Blink at lists.ag-projects.com <x-msg://11/Blink@lists.ag-projects.com>
http://lists.ag-projects.com/mailman/listinfo/blink
_______________________________________________
Blink mailing list
Blink at lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink


________________________________
_______________________________________________
Blink mailing list
Blink at lists.ag-projects.com
http://lists.ag-projects.com/mailman/listinfo/blink
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20110508/022b870e/attachment.html>


More information about the Blink mailing list