If you are looking for support for Asterisk@home, That is not what this forum is. This forum is about the IPPBX functions at i-p-tel.com. If you are asking about classic extensions for the IP PBX functions then please do not confuse the issue with your asterisk@home.
A classic extension is a regular phone number that will get routed to a trunk following whatever dial plans are setup in your outbound routing. It will cost whatever you are billed by the trunk you use. A mobile phone could be a classic extension. Classis extensions can only receive calls... they cannot make calls through i-p-tel.
A SIP extension is a userid@sipproxy-address that will be sent an INVITE following SIP protocol to create a voice connection. No costs involved. A soft phone or ATA or IP-Phone is a SIP extension. A SIP extension that is hosted by i-p-tel (firstname.lastname@example.org) can make and receive calls. A SIP extension somewhere else (email@example.com) can only receive calls through i-p-tel.
This post has been edited 1 time(s), it was last edited by dke on 24.03.2006 at 20:11.
When creating/configuring a classic extension one has the option of setting the outbound CID (caller-id). Since a classic extension is used for inbound calls, I can't figure out when setting the outbound CID would have any effect.
Of course a SIP extension can originate an outbound call, so the outbound CID has an obvious purpose.
A classic extension is used to trigger an outbound call, using an existing trunk, selected via the appropriate outbound route.
So, if the trunk's provider (ITSP) allows you to set the CallerID for delivery to the PSTN destination, being able to set it on the Classic extension permits the flexibility to do so on an extension basis, instead of on a trunk basis.