Jump to content

cei66

Members
  • Posts

    48
  • Joined

  • Last visited

Posts posted by cei66

  1. That's great info, thanks for your help!

     

    I can noodle through it myself of course, but for the benefit of the community would it be possible for Snom to provide a suggested Custom Header syntax that mimics the previous "default" header behavior? I can imagine that it would be helpful to many people who may experience breakage when attempting to upgrade.

     

    Thanks again!

    I have the same problem and i lost 2 hours finding the right header for OVH , it's true that a previous "default" header behavior would be usefull for the people who upgrade 4.3 to 4.5

  2. I ve done some more test and the result is :

    with SNOM M9 (45 ext) no pb

    with snom 320(40 ext) no pb

    with snom 870 or 821(41 ext) pb when a second call ring when i m on line the first peoople who call me don't hear me when the 2 call stop ringing it's ok again

     

    the problem is also with a client who have 4.3 and patton 4638 or in our office with 4.5 + SIP OVH TRUNK the codec who is used is G711a

     

    thanks

    log snomone.txt

  3. Do you have any firewalls in the middle that may be blocking ports on the pbx?

    it sounds like your having a one-way-audio issue. Can you provide with a sip-trace from the pbx?

     

     

    follow these instruction so you capture the trace.

     

    http://wiki.snomone.com/index.php?title=Retrieving_SIP_logging

     

    Thanks

     

    I ve got one way audio only when a second call arived when it stop ringin everything is ok.

     

    My config is snom one blue (192.168.1.200) + 30 snom phones (300 , 821 and M9 a lot of pb with M9) network 192.168.1.0 + one Patton 4638 (192.168.1.201)

     

    Tomorrow i capture the trace

  4. Looks like reply was not very clear. Let me try it in a different way.

     

    1. Run 4.3 version.
    2. Enable SIP logging
    3. Make a outbound call on the trunk in question
    4. Gather the SIP INVITE log.

     

    Now, upgrade the PBX to 4.5

     

    1. Make a outbound call on the trunk in question
    2. Gather the SIP INVITE log.
    3. See what is different from v4.3 log.
    4. cleanup the differences based on http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers to match 4.3 INVITE

     

    If you still can't understand, please open a ticket with v4.3 logs, v4.5 logs and login info to the PBX

     

    Thanks

    with this configuration it works like in 4.3 version

     

    # Trunk 2 in domain pbx.company.com

    Name: OVH 39

    Type: register

    To: sip

    RegPass: ********

    Direction:

    Disabled: false

    Global: false

    Display: 0468621111

    RegAccount: 0033411930139

    RegRegistrar: sip.ovh.net

    RegKeep: 360

    RegUser: 0033411930139

    Icid:

    Require:

    OutboundProxy: 91.121.129.20

    Ani:

    DialExtension: !([0-9]{4}$)!!t!700!

    Prefix:

    Trusted: false

    AcceptRedirect: false

    RfcRtp: false

    Analog: false

    SendEmail:

    UseUuid: false

    Ring180: true

    Failover: always

    HeaderRequestUri: {request-uri}

    HeaderFrom: {trunk}

    HeaderTo: {request-uri}

    HeaderPai:

    HeaderPpi:

    HeaderRpi:

    HeaderPrivacy:

    HeaderRpiCharging: icid-value={icid-value};icid-generated-at={ip-address};orig-ioi={domain}

    BlockCidPrefix:

    Glob:

    RequestTimeout:

    Codecs: 8

    CodecLock: true

    DtmfMode:

    Expires: 3600

    FromUser:

    Tel: true

    TranscodeDtmf: false

    AssociatedAddresses:

    InterOffice: false

    DialPlan:

    UseEpid: false

    CidUpdate:

    Ignore18xSDP: false

    UserHdr:

    Colines:

    DialogPermission:

  5. Unfortunately, we have seen issues after upgrading the PBX from 4.3 to 4.5. :rolleyes: Fortunately, it is not the end of the road :)

    The simplest way to resolve this issue is to place a call on 4.3 version, look at the SIP INVITE that is going out the trunk provider(or save the log), upgrade to 4.5, then adjust the "custom headers" to match the 4.3 behavior.

     

    Ex: Some providers want 'from' header and 'P-Asserted' header content to be same. Then you can choose the same drop-down option for both 'from' header and 'P-Asserted' headers under "custom headers" section on the trunk. Some providers do not like the Privacy header or the P-charging vector headers. You can select "Don't use this header' option.

     

    Thanks ,

    is it in text based that you should custom and is it the red part

     

     

    # Trunk 2 in domain pbx.company.com

    Name: OVH 39

    Type: register

    To: sip

    RegPass: ********

    Direction:

    Disabled: false

    Global: false

    Display: 0033468621111

    RegAccount: 0033411930139

    RegRegistrar: sip.ovh.net

    RegKeep: 360

    RegUser: 0033411930139

    Icid:

    Require:

    OutboundProxy: 91.121.129.20

    Ani:

    DialExtension: !([0-9]{4}$)!!t!700!

    Prefix:

    Trusted: false

    AcceptRedirect: false

    RfcRtp: false

    Analog: false

    SendEmail:

    UseUuid: false

    Ring180: true

    Failover: always

    HeaderRequestUri: {request-uri}

    HeaderFrom: {trunk}

    HeaderTo: {request-uri}

    HeaderPai:

    HeaderPpi:

    HeaderRpi:

    HeaderPrivacy: id

    HeaderRpiCharging: icid-value={icid-value};icid-generated-at={ip-address};orig-ioi={domain}

    BlockCidPrefix:

    Glob:

    RequestTimeout:

    Codecs: 8

    CodecLock: true

    DtmfMode:

    Expires: 3600

    FromUser:

    Tel: true

    TranscodeDtmf: false

    AssociatedAddresses:

    InterOffice: false

    DialPlan:

    UseEpid: false

    CidUpdate:

    Ignore18xSDP: false

    UserHdr:

    Colines:

    DialogPermission:

  6. Hello ,

    i ve got the problem with the second trunk who is completely create with the 4.5 version , with the same trunk created with the 4.3 version i only have to retype the password when i launch the 4.5 version and then it's ok.

    the log file is with :

    first OVH39 trunk(created with 4.3+ retype password)ok

    second OVH4139 trunk (created with 4.5) error

  7. 4.5 has a lot more flexibility with the SIP header presentation than all previous version. We tried to keep it backwards compatible, but it seems there is something special for you. http://wiki.snomone.com/index.php?title=Trunk_Custom_Headers has the information what is possible. Maybe you can just post the INVITE packet here along with the name of the service provider, so that we can find a solution also for those who use the same service provider.

     

    here is the log file the provider is OVH France

     

    error "SIP/2.0 403 Wrong login or password"

     

    the call who is ok is whith the trunk who was create with the odl version (but i was obliged to retype the password and save the trunk config )

    log-2012-01-31.txt

  8. Can you revert back to 2011-4.5.0.1016 and change your sip password? Maybe somethings has changed after the update.

    Hello , the trunk was registred but that true when i type again the same password and save it works.

    Not other problem like that when you update to the new version ?

    David

     

    NB : The adress book button of the 821 and 870 that was with an url action for displaying the address book is in ldap mode again so i should put back the url action

  9. Also sometimes the problem is that the PBX latches on to the wrong interface if you have multiple. Windows has its own preference which interface should join the multicast as far as I know.

     

     

    I ve tried the same config on the other network interface and everything work fine

     

    Thanks DAVID

  10. The log looks scattered only thing that caught my was the following.

     

    [6] 20120123190302: Call hold from trunk

    [6] 20120123190302: Different Codecs (local pcmu/8000, remote pcma/8000), callid 5l5um9chha, falling back to trans-coding.

     

    To avoid transconding you will have to make use of g711a you can change this in the port section choose only g711a and on the trunk section use g711a Also I also noticed that you have ports 30000 to 40000 ports open in the "port section" there is field called "RTP" we are using ports 49152-64512 to receive RTP can you open these ports on your router, just to be on the safe side or you can add 30000 to 40000 on the RTP section and restart the service as well.

    Thanks MR X with g711a on both trunk and port section and i also open UDP 49152-64512 it WORKS .

    Iv got client that have OVH trunk and PATTON trunk did i put G711a everywhere and for fax with AT box (cisco SPA2102) no problem ?

     

    thanks David

    log-2012-01-23-a.txt

  11. hello i ve got a snom one on a xp pro with 2 M9 , 1 870 and 1 320

    when i called an ovh number or whe somebody call me no problem but when i call a number who is not OVH ( mobile , fix telephone ) i hear the called people but he don't hear me.

    i ve open the ports (5060 ,5962 , 30000 to 40000) for this PC.

    But if i stop snom one and i install a softphone on this pc with the same OVH account there is no problem

     

    thanks

    David

×
×
  • Create New...