Hi All,
        
        While verifying issue http://track.sipfoundry.org/browse/XX-7342
and issue http://track.sipfoundry.org/browse/XX-6944, I observe the
following deviations from the previous results:
        
        Case(i):
        -----------
        When a dialplan for a SIP Trunk is added or any other dialplan
was modified, the SIP Trunking service was asking for a service restart
along with Proxy and Registrar restart request, with a message in Job
Status page after restarting SIP Trunk as --> Restarting:
sipXbridge-1/Internal SBC 1/4/10 1:28 PM 1/4/10 1:28 PM Completed
(---->as per issue XX-7342)
        
        Now, when verified this scenario in SCS 4.1.6-018102, following
are the results observed:
        --> SIP Trunking service is NOT asked for restart and only SIP
Proxy and SIP Registrar services are asked for restart.
        --> But, after restarting Proxy and Registrar, in Job Status
page, Projection for: bandwidth/SIP trunk 2/25/10 1:57 PM 2/25/10 1:57
PM Completed  is seen, though sipxbridge is NOT restarted(--->sipxbridge
pid value is not changed and remained the same as before)
        
        My query ----> Is this the expected behavior ?
         

I think that's OK, when changing the dialplan the sipxbridge.xml didn't
change so the SIP Trunking service didn't need to re-read the xml file.
The ITSP SIP Trunk gateway did a projection, but no SIP Trunking restart
was required as a result of that.

         
        Case(ii)
        ---------
        When  'Server behind NAT'  is enabled and clicked Apply, under
System >> Internet Calling >> Nat Traversal page, services for Media
Relay ,SIP Proxy and SIP Trunking are asked for restart . But, after
restarting Proxy and Registrar, in Job Status page, only File
replication: nattraversalrules.xml 2/25/10 2:08 PM 2/25/10 2:08 PM
Completed   is shown. 
        
        My query ---> Since sipxbridge is restarted, Job Status should
have information about Job completion. Can I raise a JIRA for this?
        
        Thank you in advance,
        
        -- 
        Regards, 
        Shruthi Prashanth Sarpamale  

In order to restart the SIP Trunking service immediately sipxbridge is
now being treated more like a service and less like a device.
That is the reason you don't see sipxbridge in the Job Status report.
 
Dave.
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to