Voiptalk CallerID issue

Discussion in 'UK VOIP' started by paul123, Aug 26, 2006.

  1. paul123

    paul123 Guest

    Calling out via voiptalk (with a Cambridge geographic number), the
    person receiving the call sees my caller ID as an 02071062924 number,
    which is nothing to do with my numbers....

    Configuring my brother-in-law's voiptalk (Bristol) account into my
    trixbox and then dialling out on that produces the same Caller ID being
    sent to the person receiving the call, ie 02071062924.

    Anyone else getting the same?
     
    paul123, Aug 26, 2006
    #1
    1. Advertising

  2. "paul123" <> wrote in message
    news:...
    > Calling out via voiptalk (with a Cambridge geographic number), the
    > person receiving the call sees my caller ID as an 02071062924 number,
    > which is nothing to do with my numbers....
    >
    > Configuring my brother-in-law's voiptalk (Bristol) account into my
    > trixbox and then dialling out on that produces the same Caller ID being
    > sent to the person receiving the call, ie 02071062924.
    >
    > Anyone else getting the same?
    >


    DOH! This is the caller ID from the VIP provider to the ITU no. 7 world.

    I would say that this was on a WorldCom Exchange located in central London.
     
    R. Mark Clayton, Aug 26, 2006
    #2
    1. Advertising

  3. paul123

    paul123 Guest

    Re: Voiptalk CallerID issue - or is it?

    R. Mark Clayton wrote:
    > "paul123" <> wrote in message
    > news:...
    > > Calling out via voiptalk (with a Cambridge geographic number), the
    > > person receiving the call sees my caller ID as an 02071062924 number,
    > > which is nothing to do with my numbers....
    > >
    > > Configuring my brother-in-law's voiptalk (Bristol) account into my
    > > trixbox and then dialling out on that produces the same Caller ID being
    > > sent to the person receiving the call, ie 02071062924.
    > >
    > > Anyone else getting the same?
    > >

    >
    > DOH! This is the caller ID from the VIP provider to the ITU no. 7 world.
    >
    > I would say that this was on a WorldCom Exchange located in central London.


    Strange things happening....

    It seems that it may not be a voiptalk issue, but a betamax issue
    (maybe) - as the numbers I was trying to call via voiptalk were all
    betamax numbers (voipstunt and sipdiscount).

    If I call a sipgate number from voiptalk the ID is passed correctly.
    Also, if I call the betamax numbers via wengo, ID is passed correctly.

    So, it would seem, this issue is only seen when calling from voiptalk
    to betamax. Calling from betamax to voiptalk is OK:

    Is anyone on the group with both of these providers getting the same
    results?
     
    paul123, Aug 26, 2006
    #3
  4. Re: Voiptalk CallerID issue - or is it?

    "paul123" <> wrote in message
    news:...
    >
    > R. Mark Clayton wrote:
    >> "paul123" <> wrote in message
    >> news:...

    >
    > Strange things happening....
    >
    > It seems that it may not be a voiptalk issue, but a betamax issue
    > (maybe) - as the numbers I was trying to call via voiptalk were all
    > betamax numbers (voipstunt and sipdiscount).
    >
    > If I call a sipgate number from voiptalk the ID is passed correctly.
    > Also, if I call the betamax numbers via wengo, ID is passed correctly.


    Because it never goes into the telephone network. In the UK (BT at least)
    the calling number ID has to be the same as one allocated to the line the
    call originates on. (otherwise you will get huge problems with spoofing).

    >
    > So, it would seem, this issue is only seen when calling from voiptalk
    > to betamax. Calling from betamax to voiptalk is OK:
    >
    > Is anyone on the group with both of these providers getting the same
    > results?
    >
     
    R. Mark Clayton, Aug 26, 2006
    #4
  5. paul123

    paul123 Guest

    Re: Voiptalk CallerID issue - or is it?

    R. Mark Clayton wrote:
    > "paul123" <> wrote in message
    > news:...
    > >
    > > R. Mark Clayton wrote:
    > >> "paul123" <> wrote in message
    > >> news:...

    > >
    > > Strange things happening....
    > >
    > > It seems that it may not be a voiptalk issue, but a betamax issue
    > > (maybe) - as the numbers I was trying to call via voiptalk were all
    > > betamax numbers (voipstunt and sipdiscount).
    > >
    > > If I call a sipgate number from voiptalk the ID is passed correctly.
    > > Also, if I call the betamax numbers via wengo, ID is passed correctly.

    >
    > Because it never goes into the telephone network.


    What, the BT network? surely, voiptalk to betamax and voiptalk to
    sipgate are the same scenario - they don't touch BT. but they're not
    behaving the same. Also, to add, they were behaving properly a week
    ago. (I test call all my numbers once a week)

    > In the UK (BT at least) the calling number ID has to be the same as one allocated
    > to the line the call originates on. (otherwise you will get huge problems with
    > spoofing).


    I'm not trying to spoof the callerID

    A further addition to this issue is that calling from voiptalk to my
    Spanish landline - no callerID is passed and I'm getting diverted into
    my "no ID - go to voice message IVR" (designed to not have to deal with
    those endless sales calls) - so in this case no ID is being passed at
    all! Calling from voipstunt, it behaves normally.

    .....confused
     
    paul123, Aug 26, 2006
    #5
  6. Re: Voiptalk CallerID issue - or is it?


    >>
    >> Because it never goes into the telephone network.

    >
    > What, the BT network? surely, voiptalk to betamax and voiptalk to
    > sipgate are the same scenario - they don't touch BT. but they're not
    > behaving the same.


    The call never enters the telephone network (or even BT's bit of it), which
    is what I think I already said; the call stays in TCP/IP on the internet.

    > Also, to add, they were behaving properly a week
    > ago. (I test call all my numbers once a week)
    >
    >> In the UK (BT at least) the calling number ID has to be the same as one
    >> allocated
    >> to the line the call originates on. (otherwise you will get huge
    >> problems with
    >> spoofing).

    >
    > I'm not trying to spoof the callerID


    I didn't say you were, but stating why one can't just make it up (in the UK)
    >
    > A further addition to this issue is that calling from voiptalk to my
    > Spanish landline - no callerID is passed and I'm getting diverted into
    > my "no ID - go to voice message IVR" (designed to not have to deal with
    > those endless sales calls) - so in this case no ID is being passed at
    > all! Calling from voipstunt, it behaves normally.
    >
    > ....confused
    >


    I can't say exactly why the CID is not being passed here, but some telco
    carriers will pass calls out via other networks to save charges. For
    instance IME Tele2 used to pass off peak calls to mobiles via mobile phones
    with large free call allowances rather than via the network and pay
    termination charges. The give away was that the CID was suppressed when
    they did this (otherwise you would see the number of their mobile phone),
    but was passed at other times.
     
    R. Mark Clayton, Aug 26, 2006
    #6
  7. paul123

    paul123 Guest

    Re: Voiptalk CallerID issue - or is it?

    R. Mark Clayton wrote:

    > I can't say exactly why the CID is not being passed here, but some telco
    > carriers will pass calls out via other networks to save charges. For
    > instance IME Tele2 used to pass off peak calls to mobiles via mobile phones
    > with large free call allowances rather than via the network and pay
    > termination charges. The give away was that the CID was suppressed when
    > they did this (otherwise you would see the number of their mobile phone),
    > but was passed at other times.


    ** Bear with me on this one Mark, I'm just an ignorant amateur who's
    trying to understand what might be going on....**

    So, if some telcos outsource some off peak calls, or whatever, and if
    this IS the case here, would they distinguish between different geo
    numbers (or certain numbers/ranges and hence the networks that those
    numbers belong to - ie betamax or sipgate) bearing in mind that
    voiptalk to sipgate works OK, but voiptalk to betamax doesn't? I would
    have thought they'd have the same termination rate to all geo numbers,
    irrespective of the network the number "belongs" to.

    However, if this is the case, then it would seem a possible plausible
    explanation for the scenario that I'm experiencing (it sounds like a
    funky asterisk dialplan).

    Could there be other explanations?
     
    paul123, Aug 26, 2006
    #7
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Francesco

    CallerId and Dial-up

    Francesco, Aug 29, 2004, in forum: Cisco
    Replies:
    2
    Views:
    522
    Francesco
    Aug 30, 2004
  2. TheBoy

    Cisco ATA 186 CallerID

    TheBoy, May 13, 2005, in forum: UK VOIP
    Replies:
    4
    Views:
    2,598
    TheBoy
    May 15, 2005
  3. Ron Wellsted

    SIPDiscount CallerID

    Ron Wellsted, Aug 23, 2006, in forum: UK VOIP
    Replies:
    2
    Views:
    1,532
    Philippe Deleye
    Aug 23, 2006
  4. JoeH
    Replies:
    2
    Views:
    585
    Andrew Gabriel
    Apr 21, 2007
  5. TheDragon

    Voipcheap & CallerID

    TheDragon, Sep 13, 2007, in forum: UK VOIP
    Replies:
    25
    Views:
    1,922
Loading...

Share This Page