Tony, Did you check the scenario? Thanks...

Regards,
Kumaran T

On 11/2/2012 5:22 PM, Kumaran wrote:
Thanks Tony....I found this behavior so I posted in Dev-list....Just to know why this behavior is seen..

Regards,
Kumaran T

On 11/2/2012 5:17 PM, Tony Graziano wrote:
I do have a 4.6 (nov. 1 build). I will try it. I am not sure what you are trying to point out.

On Fri, Nov 2, 2012 at 7:33 AM, Kumaran <[email protected] <mailto:[email protected]>> wrote:

    Tony,
      I think misunderstood the scenario I'm calling internal
    extension to internal extension user who doesn't have phone and
    VM permission...If you have 4.6 setup, you can give a try my
    scenario...Just  create a user without VM permission and phone
    registered...Also have dial plan with gateway which allows any
    number and call newly created ext with registered phone users..

    Regards,
    Kumaran T


    On 11/2/2012 3:30 PM, Tony Graziano wrote:
    if the user is not registered, the call is not authorized by the
    system. it will however be able to call "into" the system but
    whether the call works or not (contact header) is another thing
    altogether.

    To call INTO a system, you do not need permissions. I don't
    think we'd want to block incoming sip calls. That's a self
    defeat mechanism. Phone systems should accept calls.

    On Fri, Nov 2, 2012 at 5:22 AM, Kumaran
    <[email protected]
    <mailto:[email protected]>> wrote:

        On 11/2/2012 2:35 PM, George Niculae wrote:
        On Fri, Nov 2, 2012 at 11:03 AM, Kumaran
        <[email protected]
        <mailto:[email protected]>> wrote:

            On 11/2/2012 2:26 PM, George Niculae wrote:
            On Fri, Nov 2, 2012 at 10:51 AM, Kumaran
            <[email protected]
            <mailto:[email protected]>> wrote:

                On 11/2/2012 1:19 PM, George Niculae wrote:
                On Fri, Nov 2, 2012 at 9:32 AM, Kumaran
                <[email protected]
                <mailto:[email protected]>>
                wrote:

                    On 11/2/2012 12:56 PM, George Niculae wrote

                    I checked in 4.6 George...No issues with
                    other extension..Only user extension is
                    having issue...If VM or phone  is enabled
                    then  Registrar consider this as a valid
                    internal Extension so call will directed
                    particular user..But if user doesn't have
                    phone and vm then registrar not considering
                    as internal extension and process it through
                    local dial plan because it has permission for
                    allow calls with any number...


                When you say "user 201 without phone" this means
                without phone registered?

                George
                Yes George...No phone assigned to user 201...


            Please bare with me - there's a difference between no
            phone assigned to user 201 (which could mean no phone
            configured in sipXconfig) and no phone registered for
            that user (you can register phones that are not
            managed by sipxecs). So if no phone registered, where
            is this call established in step 5 of your scenario?

             5.user 200  call established with FXO

            Thanks
            George
            I mean registered and assigned are same meaning(no
            phone configured or register in sipXconfig for user
            201)...Consider 201 is newly created user without VM
            permission...Wrt pt-5 Local dial plan allow any numbers
            so register is sending contact  in 302 moved temp as --
            Contact: <sip:201@*176.25.3.31*(FXO ip
            
address);user=phone;sipxecs-lineid=1;sipXecs-CallDest=LOCL?expires=7200&ROUTE=%3Csip%3Asipx-test.ttplservices.com
            <http://3Asipx-test.ttplservices.com>%3Blr%3E>;q=0.9
            and establish the call


        So call between 200 and 201 is established but 201 doesn't
        have phone registered?

        George
           Yes George but  201 will be considered as outside number
        and not internal number...

        Regards,
        Kumaran T

        _______________________________________________
        sipx-dev mailing list
        [email protected]
        <mailto:[email protected]>
        List Archive: http://list.sipfoundry.org/archive/sipx-dev/




-- ~~~~~~~~~~~~~~~~~~
    Tony Graziano, Manager
    Telephone: 434.984.8430
    sip: [email protected]
    <mailto:[email protected]>
    Fax: 434.465.6833
    ~~~~~~~~~~~~~~~~~~
    Linked-In Profile:
    http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
    Ask about our Internet Fax services!
    ~~~~~~~~~~~~~~~~~~

    Using or developing for sipXecs from SIPFoundry? Ask me about
    sipX-CoLab 2013!
    <http://sipxcolab2013.eventbrite.com/?discount=tony2013>


    LAN/Telephony/Security and Control Systems Helpdesk:
    Telephone: 434.984.8426
    sip: [email protected]
    <mailto:[email protected]>

    Helpdesk Customers: http://myhelp.myitdepartment.net
    Blog: http://blog.myitdepartment.net


    _______________________________________________
    sipx-dev mailing list
    [email protected]  <mailto:[email protected]>
    List Archive:http://list.sipfoundry.org/archive/sipx-dev/




--
~~~~~~~~~~~~~~~~~~
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected] <mailto:[email protected]>
Fax: 434.465.6833
~~~~~~~~~~~~~~~~~~
Linked-In Profile:
http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!
~~~~~~~~~~~~~~~~~~

Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013!
<http://sipxcolab2013.eventbrite.com/?discount=tony2013>


LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected] <mailto:[email protected]>

Helpdesk Customers: http://myhelp.myitdepartment.net <http://myhelp.myitdepartment.net>
Blog: http://blog.myitdepartment.net



_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to