Author Topic: Connid incase of call transfer/conference  (Read 5084 times)

Gururaj S

  • Guest
Connid incase of call transfer/conference
« on: June 30, 2008, 07:45:41 AM »
I would like to know the maximum connids a call can have.
For ex: If a call is transferred to another agent or conferenced, will the connid of the call change? or will Tserver attach the same connid to the call?

Offline jbobinsk

  • Jr. Member
  • **
  • Posts: 87
  • Karma: 1
Re: Connid incase of call transfer/conference
« Reply #1 on: July 07, 2008, 01:58:27 PM »
  • Best Answer
  • ConnID changes only in case of new leg of the call eg. consult connection. When the call is transferred Connid remain the same. Of course you have to monitor all the objects involved during call propagation in the switch - if not call after passing through such object call will be recognized as new one and you will get second ConnID.

    Regards
    jbobinsk

    gururaj s

    • Guest
    Re: Connid incase of call transfer/conference
    « Reply #2 on: July 08, 2008, 07:52:43 AM »
  • Best Answer
  • Hi jbobinsk,

    Thanks for your reply. I tested the same scenario and found that
    connid doesnot change incase of transfer or conference.

    Regards,
    Gururaj S

    Offline Dionysis

    • Sr. Member
    • ****
    • Posts: 408
    • Karma: 8
    Re: Connid incase of call transfer/conference
    « Reply #3 on: September 10, 2008, 02:07:55 PM »
  • Best Answer
  • If you look at the connid at the very beginning of the call and at the very end this is true.

    However.  Each leg of the call has it's own connid.

    So:
    External Call to Extension A
    connid:xxxx

    Extension A transfers to Extension B
    connid:yyyy
    transfer connid:xxxx

    Extension A leaves the call and External call is not to Extension B
    connid: xxxx

    So there are in fact 2 conn id's in the call (xxxx and yyyy in this case), but the original connid follows the original call until that leg is disconnected.

    :)