Example: I can configure a lot of parameters in my polycom phone from its
web interface, some I have to include ina config file.
in a file for a polycom
0004f1123456-sip-phone.cfg
there are lines...
-->
<phone1>
<reg
reg.1.displayName="Heather Sanders"
(this is the display name for the first line in the phone, not the label the
phone shows on its display to the user of the phone, this is what is sent to
other sip users when that line calls them).
I don't pretend to know if that is settable in your avaya phone via a web
interface, deployment/config tool, etc. or not. If it needs to be added into
the config file and generated, ultimately, by sipxconfig to make your
deployment and management easier, then obviously the "adding support for
your phone" into sipx makes sense.
On Wed, Aug 25, 2010 at 12:42 PM, Michael Picher <[email protected]> wrote:
> Correct. That message in frame 9 is directly from the phone itself... it
> should have that name in the request.
>
>
> On Wed, Aug 25, 2010 at 12:40 PM, Heather L. Sanders <[email protected]>wrote:
>
>> Mike,
>>
>> So, what you are saying is that the phones themselves are not sending the
>> information along?
>>
>>
>>
>> ------------------------------
>> 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/25/2010 12:36 PM, Michael Picher wrote:
>>
>> Heather,
>>
>> A managed phone is simply a phone that sipXecs can generate a
>> configuration file for. There is no difference in the way a call is sent to
>> or taken from a managed or un-managed phone.
>>
>> Mike
>>
>>
>> On Wed, Aug 25, 2010 at 12:14 PM, Tony Graziano <
>> [email protected]> wrote:
>>
>>> Please try using the new wiki... if those links are broken, sound an
>>> alarm!
>>>
>>>
>>> http://wiki.sipfoundry.org/display/xecsdev/Adding+support+for+managed+phones
>>>
>>> On Wed, Aug 25, 2010 at 12:09 PM, Heather L. Sanders <[email protected]
>>> > wrote:
>>>
>>>>
>>>> My organization requires that we use the Avaya 9640 handsets for our
>>>> SIP phone implementation. So far, I have not had many issues with this
>>>> deployment. However, I am stuck on an issue with these phones because they
>>>> are 'unmanaged'. If you examine the attached pcaps, you will see where the
>>>> problem lies.
>>>>
>>>> In the 'topolycom' pcap, the phonecall is from the avaya 9640 handset.
>>>> In frame 9, you can see that the caller's name information is missing.
>>>>
>>>> In the 'toavaya' pcap, the phonecall is from a polycom 670 handset. In
>>>> frame 9, you can see that the caller's name information is present.
>>>>
>>>> I know that this is not an Avaya 9640 issue, because I can also
>>>> reproduce the issue with the Adore sip phone client on my iPhone, and the
>>>> X-Lite soft phone client on my windows pc.
>>>>
>>>> It is an unmanaged phone issue.
>>>>
>>>> I tried to explore adding support for the phones in sipX. I found this
>>>> page:
>>>> http://sipx-wiki.calivia.com/index.php/Adding_support_for_managed_phones...
>>>> However, the links to download the code are all broken, thus making it
>>>> difficult for me to add the support....
>>>>
>>>> -Or-
>>>>
>>>> Is there a much simpler way for me to get complete from header
>>>> information to be passed on unmanaged phones?
>>>>
>>>> --
>>>> ------------------------------
>>>> 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]
>>>>
>>>> _______________________________________________
>>>> sipx-users mailing list
>>>> [email protected]
>>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>>
>>>
>>>
>>>
>>> --
>>> ======================
>>> Tony Graziano, Manager
>>> Telephone: 434.984.8430
>>> sip: [email protected]
>>> Fax: 434.984.8431
>>>
>>> Email: [email protected]
>>>
>>> LAN/Telephony/Security and Control Systems Helpdesk:
>>> Telephone: 434.984.8426
>>> sip: [email protected]
>>> Fax: 434.984.8427
>>>
>>> Helpdesk Contract Customers:
>>> http://www.myitdepartment.net/gethelp/
>>>
>>> Why do mathematicians always confuse Halloween and Christmas?
>>> Because 31 Oct = 25 Dec.
>>>
>>>
>>> _______________________________________________
>>> sipx-users mailing list
>>> [email protected]
>>> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>>>
>>
>>
>>
>> --
>> There are 10 kinds of people in this world, those who understand binary
>> and those who don't.
>>
>> [email protected]
>> blog: http://www.sipxecs.info
>> call: sip:[email protected] <sip%[email protected]>
>>
>>
>> _______________________________________________
>> sipx-users mailing [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/
>>
>
>
>
> --
> There are 10 kinds of people in this world, those who understand binary and
> those who don't.
>
> [email protected]
> blog: http://www.sipxecs.info
> call: sip:[email protected] <sip%[email protected]>
>
> _______________________________________________
> sipx-users mailing list
> [email protected]
> List Archive: http://list.sipfoundry.org/archive/sipx-users/
>
--
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.984.8431
Email: [email protected]
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]
Fax: 434.984.8427
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
