innovaphone wiki - User contributions [en]

Howto:How to configure an IP phone for direct IP address dialing

2017-05-23T08:02:35Z

Tomas: /* SIP configuration */

IP Phones can be configured to work without RAS, just by dialing IP addresses. Here is how.

==Applies To==
This information applies to

* All V6 IP Phones (except DECT)

Build sr1 and later.

==More Information==

===Problem Details===
Version 6 phones can work both with and without RAS (i.e. a Gatekeeper) simultaneously. This allows to work straight forward in environments, where normally there is a gatekeeper available but still to place and receive calls when the gatekeeper is gone for whatever reason.

Of course, the phone can also be entirely without a gatekeeper.

===System Requirements===
This function is implemented in the telephone, so it will work with V5, V6 and 3rd party gatekeepers. Please note though that you will need V6 phone firmware in any case (see above).

===Configuration===
To work with and without RAS simultaneously, 2 independent registrations have to be set up as follows
* Registration 1 will be the IP-only registration (which of course is self-contradictory). This is done by configuring 0.0.0.0 as Registration 1/Registration/Primary Gatekeeper Address
* To make sure there is a valid CLI when placing calls without gatekeeper, you should also configure the phones local IP address and extension as Registration 1/Registration/Name, just like 192.168.0.3#22 assuming 192.168.0.3 is your IP address and 22 is your extension
* Registration 2 will be your normal RAS registration. Please configure as usual. This registration has to be the active registration (that is the one that is normally used for outgoing and incoming calls). You need to set Phone/Registrations[Id=2]/Active for this
* You will probably want to have access to the local phone book from this 2nd registration. Use Registration 2/Directories/Local/Enable to switch this on.

Given that there might be no RAS available when placing a call, users will find it convenient to have all potential call destinations in their local phonebook. This can best be done using an import from excel (more precisely, from an CSV file).

Here is the columns definition for the CSV file:
{|border=1 |align=left
|align=left| '''Column''' || '''Meaning''' || '''Description'''
|-
|align=left| A || First Name || Columns A, B and C will be concatenated (space separated) to form the entries internal name
|-
|align=left| B || Surname ||
|-
|align=left| C || Organisation ||
|-
|align=left| D || Destination E.164 || Destination phone number
|-
|align=left| E || Destination Name || Destination name
|-
|align=left| F || Remarks ||
|-
|align=left| G || Flags || Must be FLAG_IP for IP direct destinations, empty otherwise. Put the destination IP address into column E!
If is set and this entry is dialled, then if the active registration is registered (RAS available), the number from column D is dialled. If RAS is not available, the IP address from column E is called directly.
|-
|align=left| H || Unused ||
|-
|align=left| I || Unused ||
|-
|align=left nowrap=true| J || Ringing Tone Melody ||
|-
|align=left nowrap=true| K || Ringing Tone Rhythm ||
|-
|align=left nowrap=true| L || Ringing Tone Volume ||
|-
|align=left| M || Source E.164 ||
|-
|align=left| N || Source Name ||
|}

To enter an IP destination manually into the local phone book, you will need to enter the IP address as H.323 name and leave the E.164 empty.

==== SIP configuration ====
To allow for inbound direct sip configure for User1 a SIP protocol, User ID: number#ip, eg 22#192.168.10.17, proxy: 0.0.0.0. Second registration as mentioned above

===Dialing IP Addresses===
'''H323 calls'''

You can dial an IP address directly from the phones keyboard. Simply dial e.g. 192*168*10*17 to call the endpoint at 192.168.10.17. If you need to dial an extension (e.g. because the destination really is a gateway), you can add this extension like #22 (assuming you want to dial extension 20), which makes 192*168*10*17#22.

Obviously, only block dialing is possible this way.

'''SIP calls'''

You can dial an IP address directly from the phones keyboard. The syntax is different to H.323, it is sip:number@ip-address. If the endpoint is e.g. 22 and the IP address e.g. 192.168.10.17, you must dial sip:22@192.168.10.17



[[Category:Howto|{{PAGENAME}}]]

Howto:How to configure an IP phone for direct IP address dialing

2017-05-23T08:02:07Z

Tomas:

IP Phones can be configured to work without RAS, just by dialing IP addresses. Here is how.

==Applies To==
This information applies to

* All V6 IP Phones (except DECT)

Build sr1 and later.

==More Information==

===Problem Details===
Version 6 phones can work both with and without RAS (i.e. a Gatekeeper) simultaneously. This allows to work straight forward in environments, where normally there is a gatekeeper available but still to place and receive calls when the gatekeeper is gone for whatever reason.

Of course, the phone can also be entirely without a gatekeeper.

===System Requirements===
This function is implemented in the telephone, so it will work with V5, V6 and 3rd party gatekeepers. Please note though that you will need V6 phone firmware in any case (see above).

===Configuration===
To work with and without RAS simultaneously, 2 independent registrations have to be set up as follows
* Registration 1 will be the IP-only registration (which of course is self-contradictory). This is done by configuring 0.0.0.0 as Registration 1/Registration/Primary Gatekeeper Address
* To make sure there is a valid CLI when placing calls without gatekeeper, you should also configure the phones local IP address and extension as Registration 1/Registration/Name, just like 192.168.0.3#22 assuming 192.168.0.3 is your IP address and 22 is your extension
* Registration 2 will be your normal RAS registration. Please configure as usual. This registration has to be the active registration (that is the one that is normally used for outgoing and incoming calls). You need to set Phone/Registrations[Id=2]/Active for this
* You will probably want to have access to the local phone book from this 2nd registration. Use Registration 2/Directories/Local/Enable to switch this on.

Given that there might be no RAS available when placing a call, users will find it convenient to have all potential call destinations in their local phonebook. This can best be done using an import from excel (more precisely, from an CSV file).

Here is the columns definition for the CSV file:
{|border=1 |align=left
|align=left| '''Column''' || '''Meaning''' || '''Description'''
|-
|align=left| A || First Name || Columns A, B and C will be concatenated (space separated) to form the entries internal name
|-
|align=left| B || Surname ||
|-
|align=left| C || Organisation ||
|-
|align=left| D || Destination E.164 || Destination phone number
|-
|align=left| E || Destination Name || Destination name
|-
|align=left| F || Remarks ||
|-
|align=left| G || Flags || Must be FLAG_IP for IP direct destinations, empty otherwise. Put the destination IP address into column E!
If is set and this entry is dialled, then if the active registration is registered (RAS available), the number from column D is dialled. If RAS is not available, the IP address from column E is called directly.
|-
|align=left| H || Unused ||
|-
|align=left| I || Unused ||
|-
|align=left nowrap=true| J || Ringing Tone Melody ||
|-
|align=left nowrap=true| K || Ringing Tone Rhythm ||
|-
|align=left nowrap=true| L || Ringing Tone Volume ||
|-
|align=left| M || Source E.164 ||
|-
|align=left| N || Source Name ||
|}

To enter an IP destination manually into the local phone book, you will need to enter the IP address as H.323 name and leave the E.164 empty.

==== SIP configuration ====
To allow for inbound direct sip configure for User1 a SIP protocol, User ID: number#ip, eg 22#192.168.10.17, proxy: 0.0.0.0. Second registration as normal

===Dialing IP Addresses===
'''H323 calls'''

You can dial an IP address directly from the phones keyboard. Simply dial e.g. 192*168*10*17 to call the endpoint at 192.168.10.17. If you need to dial an extension (e.g. because the destination really is a gateway), you can add this extension like #22 (assuming you want to dial extension 20), which makes 192*168*10*17#22.

Obviously, only block dialing is possible this way.

'''SIP calls'''

You can dial an IP address directly from the phones keyboard. The syntax is different to H.323, it is sip:number@ip-address. If the endpoint is e.g. 22 and the IP address e.g. 192.168.10.17, you must dial sip:22@192.168.10.17



[[Category:Howto|{{PAGENAME}}]]

Freeedit:Wiki Edit Sandbox

2013-08-26T16:59:04Z

Tomas:

Tomas '''Vcom'''

Michael Jensen '''Scantalk'''

Kai Kröger '''Feuerwehr Düsseldorf'''

Daniel Kaiser '''''GreenIT Das druckende Systemhaus GmbH''''' www.greenit-dortmund.de

Michael Peter '''Mobene GmbH & Co. KG'''

Henning '''Bechtle GmbH'''

Thorben '''Sydslesvigsk Forening'''

Frank '''Meronec'''

Gyula '''YOUNG BTS'''

Alexander '''IP Dynamics'''

Ich '''123'''

Ingo Kauf '''http://www.telecontact.at'''

Kay A. Schink '''solid IT GmbH'''

Andreas '''IP Dynamics'''

Aleksandar '''ITM GmbH'''

Adrien '''Ascom'''

Hallo Hallo '''Hallo'''

c

Danny Burisch '''Axel Springer AG'''

Felix '''Graf Holding GmbH'''

Kujtim '''inexio'''

Eberhard '''MKK'''

Stefan Haßler '''Sparkasse Bamberg'''

Tobias '''TeleSys'''

1234

Stefano '''Eksaip'''

TESt TEST '''TEST'''

K.S '''DTG'''

[CC:'''Roman''']

Thrainer Thomas '''Kufgem'''

Roberto Arletti '''DAM SISTEMI''' SRL

Lars Lerjefors '''Telmekom''' srl

Steffen Henschel '''Telcat'''

test test

Dawid '''BELL'''

iuuo

Jens '''inexio'''

Christopher '''inexio'''

R.H. '''MediaMobil'''

A.R. '''DeTeWe'''

TEsting

D.B. '''ooperon'''

Mathias Rüger '''Telcat Multicom GmbH'''
MDN '''care-call'''

'''you are crazy to ask such questions.....'''

P.K. '''CN'''

M.B. '''CW'''

Christian, '''Incotec GmbH'''

Tobias, '''TelNet GmbH'''

-thG-

Michael, '''Frank GmbH'''

Dennis, '''Bechtle'''

Bert, '''Volksbank Stuttgart eG'''

Martin, '''Inikon AG'''

Silvio, '''Orange Open Solution SRL'''

Marcin '''Emtel System'''

Łukasz '''Emtel System'''

Christophe '''e-BO Enterprises'''

Bram '''Ooperon'''

Jo-Jo '''IPD'''

Georg '''IPD'''

Franco '''Fiemme Sistemi'''

Johann Luif, '''Business Data Solutions'''

Tobias Meyer '''Computacenter'''

Torsten L. '''TNK GmbH'''

Yvonne '''MKK'''

Florian T. '''Euromicron Solutions GmbH'''

Ralph Siebert '''blue networks GmbH & Co. KG'''

Frank Boden '''LVB GmbH'''

Steffen Merzky '''IFTEC GmBH & CO.KG'''

Simon Griedelbach '''Paragon Data GmbH'''

Christoph Bär '''Ibis GmbH'''

Tarik Mustafic '''MKS d.o.o.'''

Jörg Springer '''NK Networks & Services GmbH'''

Alex '''TMG'''

Lars Eberlein '''NK Networks & Services GmbH'''

Philippe Leboisselier '''Arrowsoft'''

Denny '''Handwerkskammer Oberfranken'''

Taavet Pilvar '''Atea'''

RMU

Niko '''@byon'''

Peter Biwer '''AS AG'''

Dirk Stapel, '''ITM GmbH'''

Tiberiju Beldja, ''' MilDef AB'''

Stian Svensli, '''Tafjord Kommunikasjon'''

Thomas Nielsen, '''TDH-Net'''

Thorsten Astroth, '''Rohwer & Mehrens GmbH - MERONEC Distribution'''

Markus Luderer, '''Main-Kinzig-Kreis - Gefahrenabwehrzentrum'''

Franz Schnabk, '''Exclusive Networks Austria GmbH'''

Peter '''neofone GmbH'''

Christian Gerhards '''neofone GmbH'''

Kurt K. '''Enigmatec Berlin'''

Torsten Wolf '''Ascom Deutschland GmbH'''

Ingo Dobroch, '''Mobene GmbH'''

Aleks '''Mobene GmbH'''

Hagen Dormeyer '''Mobene GmbH'''

Niels Scheffers '''TCC The Computer Company'''

Lars Corstiaans '''Vanroey.be'''

Howto:Pcap

2013-04-29T05:57:32Z

Tomas: /* Capturing with wireshark */

With remote PCAP, network traffic can be captured directly from another network device, instead of capturing the network traffic from the own device.

==Remote PCAP==
===Requirements===

* You should have installed the latest wireshark release >= 1.6 with the latest innovaphone dll [http://www.wireshark.org/download.html Wireshark Download]
* Required and optional tools (innovaphone_winXX.dll and log2pcap.exe): open the [http://download.innovaphone.com/ice/download/p/6.00/apps/ V6 application folder] and download the tools.zip. You will just need the innovaphone_win32.dll or innovaphone_win64.dll, depending on your installed wireshark version, 32 bit or 64 bit. Older wireshark versions won't work with the latest innovaphone_winXX.dll!
* To view the standard debug output, you have to install the innovaphone_winXX.dll, which you'll find in the tools package. Just copy the dll to your wireshark plugin directory and pay attention on your currently used version (e.g.: c:\programme\wireshark\plugins\1.6.0\).
* To view ISDN LAPD/Q.931 packets, you also have to install the innovaphone.dll.
* Open the [http://wiki.innovaphone.com/index.php?title=Image:Pcap_example_isdn.zip example pcap file with lapd and q.931 packets] to check your current installation. It should look like this, if you have the innovaphone_winXX.dll correctly installed:

[[Image:Pcap_sample_isdn.jpg|center|thumb|200px|PCAP ISDN example]]

===Setting up the rpcap server===

* The rpcap server can be any innovaphone device.
* The remote pcap server is disabled per default. To enable it, just go to Diagnostics->Tracing and check the "Enable" flag in the "Remote PCAP" group. If you are experiencing problems, also enable the trace flag with "config add PCAP /trace".
* To capture all ip traffic (udp and tcp), enable the "IP (all tcp/udp traffic)" flag in the group "IP". Otherwise just enable all the trace flags on the modules you want to capture.

===Capturing with wireshark===

Open your wireshark and the capture options dialogue. Choose "remote" from the dropdown list and
Type "<IP-ADDRESS>/TRACE" into the host field.

It should look like this:
[[Image:Wireshark_1.2.2_trace_settings.PNG|center|thumb|200px|Wireshark capture options]]

Then just click on "Start" to start capturing.

===Supported protocols===

* ISDN: LAPD L2/L3 with dissector innovaphone.dll (enable Diagnostics->Tracing TELX/PRIX/PPP)
* AC DSP: dsp with dissector Ac49xPacketRecording.dll (enable Diagnostics->Tracing->VOIP DSP)
* PPPoE: flag "/pcap" on module(s) PPPOE0/PPPOE1 enables pcap tracing

* All TCP/UDP protocols which are supported by native wireshark dissectors or other dissectors which can be found searching the internet.
e.g.:
SIP
H.323
H.245

Enable the corresponding flags under Diagnostics->Tracing, if you only want to see specific UDP/TCP protocols. To see all, enable the "All TCP/UDP Traffic" flag under Diagnostics->Tracing.

==PCAP Log==

Another possibility to get a pcap log file is to open http://IP/log.pcap
This file has a limited size just as the normal log file.

==log2pcap==

You need the tool log2pcap from the tools package, if you have a log.txt file, which contains pcap packets and you want to view them in wireshark. You can find the tool in the apps tool package (see above).

Usage:
# log2pcap.exe input1 input2 ... inputX
# drag&drop one or more files on the log2pcap.exe
# use an asterix like "log2pcap c:\*.txt" to convert all txt files into pcap files. Things like c:\test*.txt are not supported.

* The resulting file name is always inputx.pcap (e.g. log.txt is converted into log.txt.pcap).

Note: if you have a trace of a little endian box (e.g. IP3000, IP21) with V6 SR1 or SR2, you have to use the "-srlefix" switch (available since 08-1007):

log2pcap.exe input1 -srlefix

==General Informations==

===Reading PCAP Traces===

Non-IP Pcap packets will nevertheless show source and destination IP addresses. 127.0.0.1 stand in for the traced device. So if for example a Q.931 SETUP messages is sent from 127.0.0.0 to 127.0.0.1, then it is an incoming setup.

===Disabling PCAP traces===

You can disable the whole pcap tracing. Just configure a /disable-pcap to the CMD0 module. This can be useful if you do not want to see pcap traces in your log file.

===Used ports===

* The debug traces are encapsulated in UDP packets with port 4.
* The isdn traces are encapsulated in UDP packets with port 4.
* The ac dsp traces are encapsulated in UDP packets with port 50001.
* Wireshark uses port 2002 to connect to the running rpcap-server
* rpcap packets are transfered over a dynamically assigned port between server and client

===Additional Remote PCAP trace===

You can trace the remote pcap protocol with adding the trace flag by "config add PCAP /trace" if you are experiencing connection issues.

===Timestamps===

Since V7 Hotfix 26 and V8 Hotfix 13, the ntp timestamp is used instead of the uptime in rpcap packages. In converted log files with log2pcap, uptime is still used.

==Known Problems==

* Converting a log from a little endian box (like IP3000 and IP21) with firmware V6 SR1 or SR2 with the tool log2pcap will only work with log2pcap 08-1007 or higher and the switch "-srlefix", see [[:#log2pcap|log2pcap]].
* Ac49xPacketRecording.dll works only with 0.99.7. Higher versions of wireshark won't start, if this dll was copied to the dll folder!
* Also some other dlls, contained in the tools package, won't work with each wireshark version. Just innovaphone.dll is always working.
* Even though ''All TCP/UDP Traffic'' is turned on, packets sent to the box acting as rpcap provider to a port that is not handled by the box (that is, where no listening socket is active) will currently not be shown
* If you use a 64-bit Windows Pc then you will need another innovaphone.dll, which is also contained in the latest tool package.
* The custom IP header from captured innovaphone packets contains dummy values for TOS (0), id (0), fragment offset (0) and TTL (128)

==Related Articles==

[[Category:Howto|{{PAGENAME}}]]

File:Wireshark 1.2.2 trace settings.PNG

2013-04-29T05:55:01Z

Tomas: Enable remote tracing on PBX with wireshark

Enable remote tracing on PBX with wireshark