VoIP calls to Mobotix IP Camera always engaged?
Pheasant Plucker®
I have set up a couple of Mobotix D22M-SEC cameras to use VoIPtalk each with
their own number.
I have also added a third VoIPtalk number to the excellent Acrobits
SoftPhone on my iPhone.
Both cameras can make calls to the iPhone and play back a pre-recorded
message and I will play around with setting alerts at a later date.
However when I try to call either of the Mobotix IP cameras from the iPhone
using the VoIPtalk account I get the engaged tone.
I believe it did ring the very first time but did not answer and since then
all I have gotten is this damn engaged tone.
Does any kind soul have any idea what might be causing this please and
better still know how to resolve the issue?
--
Thanks & regards,
-=pp=-
News Reader
"Pheasant Plucker®" <phea...@plucker.not> wrote in message
news:8oGdnQP7m7xbha_R...@giganews.com...
Hi,
Further to reading your other recent post...
... my guess(timate) would be one or more (combination or singular) of:
- ITSP - some ITSPs (VoIP service providers) are not as open standards,
flexible, adaptable or dependable as others
- Firewall, Router, Proxy - your internet access configuration for the
cameras (that the cameras are using to provide their camera services and
perform the integrated VoIP access, functions, services, etc.) is not
permitting the desired, complete, full, augmented or extensive access they
want, are seeking or require (i.e.
- multiple device configuration - if you are using multiple of the same
devices (generally - multiple VoIP systems) on the same network (local or
subnet / routed origin zone, etc.) then you might well find that they
inherently jam, block or contend / congest (with) each other. Therefore,
they may require manual configuration to have or use separate port ranges
for each device (particularly perhaps on the VoIP side [the webcam / IP
camera aspect may not require this] - certain ITSPs or configurations,
service types, performance objectives / profiles, etc. may make this more
important, necessary or applicable / required / relevant).
This may be helpful or useful...
... particularly for example regarding specific / peculiar anomalies of
given routers, etc. and (moreover?) ports to be opened / forwarded (for one
SIP / VoIP client... you would need to read more about using multiple SIP /
VoIP clients in the same network / zone source, etc. especially if you want
"full" "compliant" "standards" / what have you, etc. SIP / VoIP
implementation [or if this is required / your ITSP / VoIP providers
implementation requires this, etc.] [i.e. sequentially increase the block
ranges and matchingly re-configure your SIP / VoIP for each such SIP / VoIP
client device - e.g. device 1: 5060 and 5000-5010; device 2: 5061 and
5011-5021; device 3: 5062 and 5022-32, etc., etc.?]).
Hope that might help a bit or works!
Simplest solution or version for you might be - change your ITSP / VoIP
provider (that you are trying to use in [each of] your IP cameras). Else /
or (and perhaps necessarily depending on your internet router / access
configuration [or rather your cameras access thereat]) port forwarding, DMZ,
routing, etc.
Best wishes,
News Reader
--- news://freenews.netfront.net/ - complaints: ne...@netfront.net ---
News Reader
"News Reader" <n...@email.invalid> wrote in message
news:i1gd2f$1136$1...@adenine.netfront.net...
Hi,
...
ooopppps.... was supposed to include the third option before the wrap up....
... in fact... no... no... hold it... I made a complete hash of that post...
lets start again...
*** CORRECT VERSION !!! ***
Hi,
Further to reading your other recent post...
... my guess(timate) would be one or more (combination or singular) of:
- ITSP - some ITSPs (VoIP service providers) are not as open standards,
flexible, adaptable or dependable as others
- Firewall, Router, Proxy - your internet access configuration for the
cameras (that the cameras are using to provide their camera services and
perform the integrated VoIP access, functions, services, etc.) is not
permitting the desired, complete, full, augmented or extensive access they
want, are seeking or require (i.e. not direct IP or own proper external IP
address each, or fully independently [per device] routed / forwarded ports /
routes, etc. e.g. on your router, firewall, etc.!)
This may be helpful or useful...
... particularly for example regarding specific / peculiar anomalies of
given routers, etc. and (moreover?) ports to be opened / forwarded (for one
SIP / VoIP client... if you need to be, are or will be using more than one
SIP / VoIP client / device then you will or at least might need to a bit
more clever and go on to an extra layer / level or do some additional more
clever steps - see the "extra >>" section below the next point(!).
- multiple device configuration - if you are using multiple of the same
devices (generally - multiple VoIP systems) on the same network (local or
subnet / routed origin zone, etc.) then you might well find that they
inherently jam, block or contend / congest (with) each other. Therefore,
they may require manual configuration to have or use separate port ranges
for each device (particularly perhaps on the VoIP side [the webcam / IP
camera aspect may not require this] - certain ITSPs or configurations,
service types, performance objectives / profiles, etc. may make this more
important, necessary or applicable / required / relevant).
... extra >> you would need to read more about using multiple SIP /
VoIP clients in the same network / zone source, etc. especially if you want
"full" "compliant" "standards" / what have you, etc. SIP / VoIP
implementation [or if this is required / your ITSP / VoIP providers
implementation requires this, etc.] [i.e. sequentially increase the block
ranges and matchingly re-configure your SIP / VoIP for each such SIP / VoIP
client device - e.g. device 1: 5060 and 5000-5010; device 2: 5061 and
5011-5021; device 3: 5062 and 5022-32, etc., etc.?]).
- Device Hardware Issue / SIP / VoIP Implementation Issue: It may be that
the Mobotix camera hard / software has an either rather "custom"
implementation of SIP / VoIP, a partial implementation or a rather quirky or
particular "standards" approach to their implementation / the way they have
done their implementation. You can probably guess the work around / fix for
this (either pick a different model if they have done some other differently
or that "work" or at least "work how you would like / hope", chose a
different vendor, research or identify the specific issues with their
equipment / this model and implement your own specific / the model or
manufacturer specific "fix", etc. - lol : - ) ).
Hope that might help a bit or works!
Simplest solution or version for you might be - change your ITSP / VoIP
provider (that you are trying to use in [each of] your IP cameras). Else /
or (and perhaps necessarily depending on your internet router / access
configuration [or rather your cameras access thereat]) port forwarding, DMZ,
routing, etc. (Maybe somewhat sensible try basic testing procedure and have
just one device installed at first until you get that all fully working then
see about adding additional units and / or also don't ever forget "old
favourite" or good old modular swap out fault testing [i.e. swap out
components to determine faulty as / if where necessary - i.e. one of the
units may be behaving spuriously or anomalously, etc.! : - ) ).
Chris Davies
> I have set up a couple of Mobotix D22M-SEC cameras to use VoIPtalk each with
> their own number.
> However when I try to call either of the Mobotix IP cameras from the iPhone
> using the VoIPtalk account I get the engaged tone.
Email me and I'll try to offer help from an independent point of view
Chris
Pheasant Plucker®
I have already been into the router and disabled SIP ALG if that makes any
sense...
It'll take a little while to digest & a little longer for me to get round to
trying things out but I will give it a go...
Thanks & kind regards,
-=Glyn=-
"News Reader" <n...@email.invalid> wrote in message
news:i1gdu1$12oo$1...@adenine.netfront.net...