we have a small issue ,cust has an existing SIP trunk 100 DID #s.Cust had a main number at site A 7601234567
and fwd that number to site B main number 7603001000 and it worked .But cust published all advertisement with 7601234567
and now ported that number to SIP trunk .With saying that we prog a incoming route and also sip uri but provider said line was not correct
it wouldnt ring into system. so we put it in line 18 which is the DID incoming group and it worked . 2nd day cust called that it wasnt working , message said line is no longer in service . ATT points trouble to IPO. we moved it to incoming line 17 and its been working
all tech support engineers confirm that prog is correct and trouble lies on ATT .ATT cant explain why 7601234567 fails and the other 100 doesn't.we can supply screen shots if needed. side note when it failed we did get a screen monitor file and it did hit the ipo but message said line is no longer in service or has been disconnected .
this is the file that was failing prior to moving number to line 18
and fwd that number to site B main number 7603001000 and it worked .But cust published all advertisement with 7601234567
and now ported that number to SIP trunk .With saying that we prog a incoming route and also sip uri but provider said line was not correct
it wouldnt ring into system. so we put it in line 18 which is the DID incoming group and it worked . 2nd day cust called that it wasnt working , message said line is no longer in service . ATT points trouble to IPO. we moved it to incoming line 17 and its been working
all tech support engineers confirm that prog is correct and trouble lies on ATT .ATT cant explain why 7601234567 fails and the other 100 doesn't.we can supply screen shots if needed. side note when it failed we did get a screen monitor file and it did hit the ipo but message said line is no longer in service or has been disconnected .
this is the file that was failing prior to moving number to line 18