FreeSWITCH

Early callstate is missing on incoming calls

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Patch Patch
  • Resolution: Incomplete
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Platform:
    Linux x86/gcc
  • FreeSWITCH GIT Revision:
    2010-12-16
  • Reproduced with GIT HEAD?:
    yes

Description

I don't know, is it a bug or should it act like this, but:
The Early callstate is missing when az incoimng call occured from outside

Ext-to-ext call:
caller Ringing > caller Early > calee Ringing

Outgoing call:
caller ext Ringing > trunk Ringing > trunk Early > caller ext Early

BUT incoming call:
trunk Ringing > called ext Ringing


I attach a drawing about this.
(The connected boxes (without border between) couse directly each other's callstate change, in order.
The colors act like more or less blf states, but don't care them.)


So is this a bug or, is this works right this way?

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Peter Olsson added a comment -
I'm not really sure I fully understand what your problem is. But it sounds like your provider has something to do with this, not FS.

/Peter
Show
Peter Olsson added a comment - I'm not really sure I fully understand what your problem is. But it sounds like your provider has something to do with this, not FS. /Peter
Hide
Permalink
Robert Toth added a comment -
As i see the logic is: caller asks FS to ring callee [ring-event on legA]. When FS is ready to originate legB to callee, it sends and early to caller [early-event on legA], then ring the callee [ring-event on legB]. Then the callee phone will be ringing.

On outgoing call the caller asks FS to call the callee [ring-event on legA]. Because callee is behind the provider, FS asks the provider to make a call to the callee [ring-event on legB]. When the provider is ready to call the callee, it sends an early to FS [early-event on legB]. Now FS knows the provider is ready to make the call, so FS sends an early to the caller [early-event on legA]. Then the callee phone will be ringing.

On incoming call the provider says it has a caller [ring-event on legA] who wants a call with us. When FS is ready to ring our phone, it says this to the provider [**early-event on legA**], the ring the callee phone [ring-event on legB].

** This early is missing, at least by this logic. And all event is by FS on the calls different states.
So is my logic wrong, or does not FS make this event by some reason?
Show
Robert Toth added a comment - As i see the logic is: caller asks FS to ring callee [ring-event on legA]. When FS is ready to originate legB to callee, it sends and early to caller [early-event on legA], then ring the callee [ring-event on legB]. Then the callee phone will be ringing. On outgoing call the caller asks FS to call the callee [ring-event on legA]. Because callee is behind the provider, FS asks the provider to make a call to the callee [ring-event on legB]. When the provider is ready to call the callee, it sends an early to FS [early-event on legB]. Now FS knows the provider is ready to make the call, so FS sends an early to the caller [early-event on legA]. Then the callee phone will be ringing. On incoming call the provider says it has a caller [ring-event on legA] who wants a call with us. When FS is ready to ring our phone, it says this to the provider [**early-event on legA**], the ring the callee phone [ring-event on legB]. ** This early is missing, at least by this logic. And all event is by FS on the calls different states. So is my logic wrong, or does not FS make this event by some reason?
Hide
Permalink
Marc Olivier Chouinard added a comment -
I'm actually confused my self on the problem... I know I had a problem where I had to call ring_ready and that before any app that pre_answer the channel so the ringing to be sent... maybe it related ?
Show
Marc Olivier Chouinard added a comment - I'm actually confused my self on the problem... I know I had a problem where I had to call ring_ready and that before any app that pre_answer the channel so the ringing to be sent... maybe it related ?
Hide
Permalink
Jeff Lenk added a comment -
please reopen if you can followup in a timely manor. Also specifiy exactly what you are looking for that is missing - I dont think anyone understands what the issue is here.
Show
Jeff Lenk added a comment - please reopen if you can followup in a timely manor. Also specifiy exactly what you are looking for that is missing - I dont think anyone understands what the issue is here.
Hide
Permalink
Robert Toth added a comment -
The Early callstate is missing on incoming (from trunk) calls. It would be useful if i can know when the call can be built, and the phone starts to ringing.

Because the Ringing callstate only say that somebody wants to call me. And the Early callstate wil say that the call can be built (e.g. there is an extension online, not busy, etc, what can accept the call.)

In Ringing state i do not know which extension(s) will be ringing, because the dialplan is not executed yet, so there is not any/enough data what for example can be saved in log, or can be writen on an admin monitor, etc...
Show
Robert Toth added a comment - The Early callstate is missing on incoming (from trunk) calls. It would be useful if i can know when the call can be built, and the phone starts to ringing. Because the Ringing callstate only say that somebody wants to call me. And the Early callstate wil say that the call can be built (e.g. there is an extension online, not busy, etc, what can accept the call.) In Ringing state i do not know which extension(s) will be ringing, because the dialplan is not executed yet, so there is not any/enough data what for example can be saved in log, or can be writen on an admin monitor, etc...
Hide
Permalink
Jeff Lenk added a comment -
So you are looking for an event here? Can you give a complete example of a working outgoing scenario and then show the non working (incoming) scenario again please.
Show
Jeff Lenk added a comment - So you are looking for an event here? Can you give a complete example of a working outgoing scenario and then show the non working (incoming) scenario again please.
Hide
Permalink
Robert Toth added a comment -
In my case i would use it to save the details of the call to DB. This DB is used for logging, and to write the datas of ringing phones, the caller, etc, to other phone. This way they know should they pickup or do something. I look for the caller infos from the national phone register, and save it too.

In Ringing callstate i only have the caller number, without the called extensions, the caller infos, etc. Then in the dialplan i look for some of these datas. And other datas are ready when the Early callstate event would be fired, so i would know that this point is point when i could collect all datas from the channel.

I hope i explained this in understandable way.
Show
Robert Toth added a comment - In my case i would use it to save the details of the call to DB. This DB is used for logging, and to write the datas of ringing phones, the caller, etc, to other phone. This way they know should they pickup or do something. I look for the caller infos from the national phone register, and save it too. In Ringing callstate i only have the caller number, without the called extensions, the caller infos, etc. Then in the dialplan i look for some of these datas. And other datas are ready when the Early callstate event would be fired, so i would know that this point is point when i could collect all datas from the channel. I hope i explained this in understandable way.
Hide
Permalink
Anthony Minessale II added a comment -
Are you talking about sip presence events?
The outside calls have no presence id and a subscription has to be made to that id so they are not going to trigger any events.
Show
Anthony Minessale II added a comment - Are you talking about sip presence events? The outside calls have no presence id and a subscription has to be made to that id so they are not going to trigger any events.
Hide
Permalink
Jeff Lenk added a comment -
Closed for lack of followup
Show
Jeff Lenk added a comment - Closed for lack of followup
Hide
Permalink
Auto Admin added a comment -
Due to a long period of inactivity (13 or more days), this issue is due to be automatically close within 24 hours.
If this issue is not actually resolved, please reopen it and add appropriate comments to help developers fix the issue.

Thanks,
  Jira Admin
Show
Auto Admin added a comment - Due to a long period of inactivity (13 or more days), this issue is due to be automatically close within 24 hours. If this issue is not actually resolved, please reopen it and add appropriate comments to help developers fix the issue. Thanks,   Jira Admin
Hide
Permalink
Auto Admin added a comment -
Since there has been no change to the status of this issue, it is being closed for inactivity

Thanks,
  Jira Admin


FreeSWITCH Support Contracts and Consulting Services available!

Contact us:
Email: consulting@freeswitch.org
Web: http://www.freeswitch.org
Phone: +1-918-420-9266
Tollfree: +1-877-742-2583
Fax: +1-918-420-9267
iNum: +883 5100 1420 9266


Come To ClueCon in August to learn more about FreeSWITCH and Internet Telephony!
http://www.cluecon.com

Show
Auto Admin added a comment - Since there has been no change to the status of this issue, it is being closed for inactivity Thanks,   Jira Admin FreeSWITCH Support Contracts and Consulting Services available! Contact us: Email: consulting@freeswitch.org Web: http://www.freeswitch.org Phone: +1-918-420-9266 Tollfree: +1-877-742-2583 Fax: +1-918-420-9267 iNum: +883 5100 1420 9266 Come To ClueCon in August to learn more about FreeSWITCH and Internet Telephony! http://www.cluecon.com

People

  • Assignee:
    Anthony Minessale II
    Reporter:
    Robert Toth
Vote (0)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved: