Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Caller ID not passing over to SIP Provider.

Discussion in '3CX Phone System - General' started by malimar, Jan 20, 2011.

Thread Status:
Not open for further replies.
  1. malimar

    Joined:
    Oct 26, 2010
    Messages:
    10
    Likes Received:
    0
    Hi,

    We are unable to pass through our customize "Outbound Caller ID" under the "Edit VOIP Provider". We contacted the VOIP Provider Group3.ca, their support confirmed they put whatever ID they receive from our the 3CX. They said if we wanted to customize the caller ID we have to do it on your 3CX before sending the calls to them. Please see below long. I do not see anything that applies the "Outbound Caller ID" doing the connection of the call.

    Is there anywhere else we need to change for the Caller ID?

    ********** = our account info to our provider blured out.

    10:27:51.605 [CM503008]: Call(32): Call is terminated
    10:27:49.843 Currently active calls - 1: [32]
    10:27:45.116 Session 1410 of leg C:32.1 is confirmed
    10:27:45.006 [CM503007]: Call(32): Device joined: sip:**********@208.69.56.54:5060
    10:27:45.006 [CM503007]: Call(32): Device joined: sip:102@192.168.200.102:5060
    10:27:45.006 [MS210001] C:32.2:Answer received. RTP connection[unsecure]: 208.69.56.54:17624(17625)
    10:27:45.006 Remote SDP is set for legC:32.2
    10:27:36.691 [MS210003] C:32.1:Answer provided. Connection(transcoding mode[unsecure]):192.168.200.5:7110(7111)
    10:27:36.691 [MS210001] C:32.2:Answer received. RTP connection[unsecure]: 208.69.56.54:17624(17625)
    10:27:36.691 Remote SDP is set for legC:32.2
    10:27:36.691 [CM505003]: Provider:[Group3] Device info: Device Not Identified: User Agent not matched; Capabilities:[reinvite, replaces, able-no-sdp, recvonly] UserAgent: [] PBX contact: [sip:**********@Our WAN IP ADDRESS:5060]
    10:27:36.691 [CM503002]: Call(32): Alerting sip:**********@208.69.56.54:5060
    10:27:34.991 [CM503025]: Call(32): Calling VoIPline:*************16198088696@(Ln.10002@Group3)@[Dev:sip:**********@208.69.56.54:5060]
    10:27:34.991 [MS210002] C:32.2:Offer provided. Connection(transcoding mode): Our WAN IP ADDRESSS:9022(9023)
    10:27:34.944 [CM503004]: Call(32): Route 1: VoIPline:*************16198088696@(Ln.10002@Group3)@[Dev:sip:**********@208.69.56.54:5060]
    10:27:34.944 [CM503010]: Making route(s) to <sip:8088696@192.168.200.5;user=phone>
    10:27:34.944 [MS210000] C:32.1:Offer received. RTP connection: 192.168.200.102:2234(2235)
    10:27:34.944 Remote SDP is set for legC:32.1
    10:27:34.944 [CM505001]: Ext.102: Device info: Device Identified: [Man: Polycom;Mod: SoundPoint IP Series;Rev: General] Capabilities:[reinvite, replaces, unable-no-sdp, no-recvonly] UserAgent: [PolycomSoundPointIP-SPIP_550-UA/3.3.1.0769] PBX contact: [sip:102@192.168.200.5:5060]
    10:27:34.929 [CM503001]: Call(32): Incoming call from Ext.102 to <sip:8088696@192.168.200.5;user=phone>
    10:27:34.929 [CM500002]: Info on incoming INVITE:
    INVITE sip:8088696@192.168.200.5:5060;user=phone SIP/2.0
    Via: SIP/2.0/UDP 192.168.200.102;branch=z9hG4bK6c75d7583FF50D6D
    Max-Forwards: 70
    Contact: <sip:102@192.168.200.102>
    To: <sip:8088696@192.168.200.5;user=phone>
    From: "Denny Lasaath"<sip:102@192.168.200.5>;tag=93EC0DB5-C5EF05DE
    Call-ID: 2d280571-df3e900a-efc5f127@192.168.200.102
    CSeq: 2 INVITE
    Accept-Language: en
    Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, INFO, MESSAGE, SUBSCRIBE, NOTIFY, PRACK, UPDATE, REFER
    Proxy-Authorization: Digest username="102",realm="3CXPhoneSystem",nonce="414d535c03490f9659:2bdd8ad1172f7be4a24d8574846a2a5d",uri="sip:8088696@192.168.200.5:5060;user=phone",response="4157547db7981a02f40079c4a9d97e3f",algorithm=MD5
    Supported: 100rel, replaces
    User-Agent: PolycomSoundPointIP-SPIP_550-UA/3.3.1.0769
    Allow-Events: talk, hold, conference
    Content-Length: 0
     
  2. mhanson

    mhanson New Member

    Joined:
    Nov 6, 2008
    Messages:
    186
    Likes Received:
    1
    You need to ask exactly what SIP field they pull the caller ID from. How can you expect to edit your sent caller ID settings without knowing exactly what they are looking for.

    Find out whether they want the caller ID in one of the From Fields, or URI etc. I can tell you how to edit for that.

    Also, what is currently passing? What is showing up right now? Did the Provider say waht they were getting and why it was wrong? All of the answers to these questions will help figure out what setting you need to change in your outbound parameters.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
Thread Status:
Not open for further replies.