[Blink] "Not acceptable here" error after yesterday's 3.0.0

Jeff Pyle jpyle at fidelityvoice.com
Fri Aug 16 21:17:53 CEST 2013


I have Blink Pro - hopefully they're close.  Under Preferences, Accounts
(then choose the account if necessary), Advanced (right pane), SIP
Signaling you have the options for primary and alternate proxies.  In here
you should be able to specify the format you're used to.

The SIP address you used when you created the account will be
username at domain, period.  The Primary Proxy, however, could contain
server:port;transport=tcp if you wanted to.  The ;transport parameter is
optional of course.

If you don't have direct access to the Asterisk side, you can experiment by
disabling some of the new codecs under Advanced, RTP Media and check
Customize.  If you're using this client for PSTN calls only you may get
away with G.711u all by itself.  If you're connecting to other IP endpoints
with higher fidelity codecs like G.722 then it may make sense to leave
those enabled also.

On my network I use RFC2833-style DTMF, so I uncheck "Send Inband DTMF"
(thus forcing it to 2833).

Report back how it goes.

- Jeff

On Fri, Aug 16, 2013 at 12:25 PM, Adrian Georgescu <ag at ag-projects.com>wrote:

> Blink supports any protocol/port combinations. Can you detail what do you
> mean by this:
> normal username at server:port entry is refused by Blink.
> Refused where, in which context?
> Adrian
> On Aug 16, 2013, at 6:23 PM, James Mueller <
> james.mueller at kingleyhealth.com> wrote:
>  It seems Asterisk doesn't like something in the codecs advertised in the
>> SDP.  What do you have configured for codecs in the Asterisk peer/user?  I
>> bet by adjusting them on one side or the other you can resolve this.
>> - Jeff
> Thank you Jeff - our administrator is looking closely at the 1400+ lines
> of log the test call generated on the server.
> To test this more directly I just purchased my own copy of Blink Lite for
> my Mac but I'm having trouble configuring it to use the non-standard port
> he uses for SIP. Obviously it can be done - he set it up for the boss in
> the previous version of Blink, but the normal username at server:port entry
> is refused by Blink.
> This message contains confidential information and is intended only for
> the individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail. It may be client
> communication that may contain information that is legally privileged or
> confidential or otherwise legally exempt from disclosure. Please notify
> the sender immediately by e-mail if you have received this e-mail by
> mistake and delete this e-mail from your system and do not disclose its
> contents to any person. E-mail transmission cannot be guaranteed to be
> secure or error-free as information could be intercepted, corrupted, lost,
> destroyed, arrive late or incomplete, or contain viruses. The sender
> therefore does not accept liability for any errors or omissions in the
> contents of this message, which arise as a result of e-mail transmission.
> If verification is required please request a hard-copy version. It's About
> Wellness, LLC c/o Kingley Health 220 Centennial Ave., Piscataway, NJ 08854.
> P: 732.283.1900 F: 732.791.**9566.
> _______________________________________________
> 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/20130816/71ddda78/attachment.html>

More information about the Blink mailing list