SIPPHONE NOT CALL

Discussion in '3CX Phone System - General' started by amygoda, Aug 20, 2007.

  1. amygoda

    amygoda Member

    Joined:
    Sep 18, 2006
    Messages:
    437
    Likes Received:
    0
    Hello
    I set the sipphone and it registerd and recive calls but donot call
    I made oubound rule 7r to sipphone
    so i dial 7 then x xxx xxxxxxx
     
  2. gbarnes

    Joined:
    Aug 3, 2007
    Messages:
    83
    Likes Received:
    0
    Outbound rule...

    Hi,

    Outbound rule should be starting with 7

    The rule should be r

    This should show on the list as

    Number Prefix 7, Mask r

    This will delete the 7 prefix and dial the number.
     
  3. amygoda

    amygoda Member

    Joined:
    Sep 18, 2006
    Messages:
    437
    Likes Received:
    0
    Hello
    thanks for your ansower
    exactl you said but it gives me can not complete the call
     
  4. Mirzab

    Mirzab Member

    Joined:
    Jul 22, 2007
    Messages:
    400
    Likes Received:
    0
    More information my friend.... Copy of logs, some info on your setup, maybe a copy of the 3CX setup page, that sort of thing. Too many possibilities right now.
     
  5. gbarnes

    Joined:
    Aug 3, 2007
    Messages:
    83
    Likes Received:
    0
    Outbound rule..

    Yes, some logs would possibly get to the problem.

    In the meantime, you could just check:

    Make outbound calls on
    VOIP PROVIDER <<< YOUR VOIP PROVIDER>>>

    is set in your rule and try that.

    We will get there! Graeme. :roll:
     
  6. amygoda

    amygoda Member

    Joined:
    Sep 18, 2006
    Messages:
    437
    Likes Received:
    0
    Hi
    this a call I made from ext 30301 at 05:23:42.578

    I think from this data you can disolve my planet 450 registartion problem
    beside sipphone problem


    05:23:50.828 StratLink::eek:nHangUp [CM104001] Call(9): Ln:40901@SIPPHONE hung up call; cause: BYE; from IP:198.65.166.131
    05:23:49.968 DBPostgressAccessor::addRegistrarContact ERROR: invalid page header in block 58 of relation "prstorage"
    05:23:49.968 DBPostgressAccessor::removeRegistrarContact ERROR: invalid page header in block 28 of relation "prstorage"
    05:23:48.515 DBPostgressAccessor::addRegistrarContact ERROR: invalid page header in block 58 of relation "prstorage"
    05:23:48.515 DBPostgressAccessor::removeRegistrarContact ERROR: invalid page header in block 28 of relation "prstorage"
    05:23:45.859 CallLegImpl::eek:nConnected [CM103001] Call(9): Created audio channel for Ln:40901@SIPPHONE (198.65.166.131:42370) with Media Server (196.202.10.226:9004)
    05:23:45.859 StratInOut::eek:nConnected [CM104005] Call(9): Setup completed for call from Ext.30301 to Ln:40901@SIPPHONE
    05:23:45.859 CallLegImpl::eek:nConnected [CM103001] Call(9): Created audio channel for Ext.30301 (172.17.99.224:8002) with Media Server (172.17.99.219:7026)
    05:23:42.578 CallConf::eek:nIncoming [CM103002] Call(9): Incoming call from 30301 (Ext.30301) to sip:717145317904@172.17.99.219
    05:23:27.125 ServRegs::eek:nAdd [CM113002] Registered: Ext.30203
    05:23:27.109 DBPostgressAccessor::addRegistrarContact ERROR: invalid page header in block 58 of relation "prstorage"
    05:23:27.109 DBPostgressAccessor::removeRegistrarContact ERROR: invalid page header in block 28 of relation "prstorage"
    05:23:26.656 DBPostgressAccessor::removeRegistrarContact ERROR: invalid page header in block 28 of relation "prstorage"
    05:23:26.656 ServRegs::checkExpiration [CM113000] Registration for sip:30203@172.17.99.219 has expired
    05:23:26.656 DBPostgressAccessor::removeRegistrarContact ERROR: invalid page header in block 28 of relation "prstorage"
    05:23:26.656 DBPostgressAccessor::removeRegistrarContact ERROR: invalid page header in block 28 of relation "prstorage"
    05:23:26.343 ServRegs::eek:nAdd [CM113002] Registered: Ext.30202
    05:23:26.343 DBPostgressAccessor::addRegistrarContact ERROR: invalid page header in block 58 of relation "prstorage"
     
  7. Mirzab

    Mirzab Member

    Joined:
    Jul 22, 2007
    Messages:
    400
    Likes Received:
    0
    I recently had a problem right after an upgrade with a very similar sequence of errors, and I was advised that the database did not upgrade correctly. The only fix in the end was a complete uninstall and a clean reinstall. I am not 100% sure but you can consider it. If you decide to, make a backup first, makes restoring a breeze.
     

Share This Page