Alexey, Thank you for the suggestion. Currently, I am working on doing exactly that, using the AudioCodes Mediant 1000 with a IP2IP MPM. I expect to have some tests running on this setup early next week. With any luck, this setup will solve many of the issues that I am seeing with the 9640s.
------------------------------------------------------------------------ Heather L. Sanders Linux Systems Administrator Saginaw Valley State University 7400 Bay Road 374 Wickes Hall University Center, MI 48710 Office: (989) 964-2156 Mobile: (989) 326-3300 Email: [email protected] On 09/09/2010 10:22 AM, Alexey Kanukhin wrote: > I am not sure that it is possible to generate a custom "Contact" > header for calls to certain type phones in sipXecs. However I believe > that you may solve this task by external tool – by hardware or > software Session Border Controller (SBC). Unfortunately, it is not > easy way as this approach will complicate VoIP system. > Several years ago I solved a similar problem. I need to manipulate > contents of "From" and "To" headers in SIP messages for my voice lab > environment. I used OpenSER > (http://www.voip-info.org/wiki/view/OpenSER) for this purpose. I think > this software also can be used for adding Display Name in "Contact" > header. > > -- > Sincerely yours, > Alexey Kanukhin > > > On Sat, Sep 4, 2010 at 12:31 AM, Heather L. Sanders <[email protected]> wrote: > >> I found the answer to this problem by accident today. The new Avaya phones >> get their caller id information from the 'Contact' header. Interestingly, >> the ACD function of sipX uses full contact header information, and thus, >> caller id displays on Avaya phones. >> >> Any chance there is an easy way to change a setting to send contact header >> information in the same manner as the from header? >> >> ________________________________ >> Heather L. Sanders >> Linux Systems Administrator >> Saginaw Valley State University >> 7400 Bay Road >> 374 Wickes Hall >> University Center, MI 48710 >> Office: (989) 964-2156 >> Mobile: (989) 326-3300 >> Email: [email protected] >> >> On 08/26/2010 10:47 AM, Heather L. Sanders wrote: >> >> Wouldn't it be nice if it were just that easy? >> ________________________________ >> Heather L. Sanders >> Linux Systems Administrator >> Saginaw Valley State University >> 7400 Bay Road >> 374 Wickes Hall >> University Center, MI 48710 >> Office: (989) 964-2156 >> Mobile: (989) 326-3300 >> Email: [email protected] >> >> On 08/26/2010 10:38 AM, Nathaniel Watkins wrote: >> >> Polycom has a trade-in program going - $75 back for each phone you >> purchase. Helps ease the pain… >> >> >> >> http://www.polycom.com/global/documents/products/promotions/latest_promotions/soundpoint-ip-tradein-program.pdf >> >> >> >> >> >> Nathaniel Watkins >> IT Director >> Garrett County Government >> 203 South 4th Street, Room 210 >> Oakland, MD 21550 >> Telephone: 301-334-5001 >> Fax: 301-334-5021 >> E-mail: [email protected] >> >> >> >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Heather L. >> Sanders >> Sent: Thursday, August 26, 2010 10:30 AM >> To: Martin Steinmann >> Cc: [email protected] >> Subject: Re: [sipx-users] From Header Info Incomplete on Unmanaged Phones >> >> >> >> On 08/26/2010 12:13 AM, Martin Steinmann wrote: >> >> I would put them into the category of ‘closed’ phones, meaning that they are >> really not made with the intent to work on other systems than Avaya’s. >> >> Ain't that the truth.... >> >> Therefore, taking all this and including support cost into account, new >> phones might not be that bad an option. >> >> We started this 'pilot' with the Polycom 670 handset, which imho, is a >> superior product for this implementation. However, it would seem that those >> who make purchasing decisions are not the same folks as those who must >> configure the system... >> >> On a positive note, my boss and I did figure out how to make the Avaya 9640s >> send a proper From header this morning. But, the Avaya 9640s choose not to >> read the proper From header, thus, no name info is displayed, still. >> >> ________________________________ >> This message and any files transmitted with it are intended only for the >> individual(s) or entity named. If you are not the intended individual(s) or >> entity named you are hereby notified that any disclosure, copying, >> distribution or reliance upon its contents is strictly prohibited. If you >> have received this in error, please notify the sender, delete the original, >> and destroy all copies. Email transmissions cannot be guaranteed to be >> secure or error-free as information could be intercepted, corrupted, lost, >> destroyed, arrive late or incomplete, or contain viruses. Garrett County >> Government therefore does not accept any liability for any errors or >> omissions in the contents of this message, which arise as a result of email >> transmission. >> >> >> Garrett County Government, >> 203 South Fourth Street, Courthouse, Oakland, Maryland 21550 >> www.garrettcounty.org >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> >> _______________________________________________ >> sipx-users mailing list >> [email protected] >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ >> >> > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
