SIP Trunk Caller ID issue

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • hussa89
    Member
    • Mar 2016
    • 7

    SIP Trunk Caller ID issue

    Avaya IP Office is connected with 3rd party call center application through SIP trunk.
    On 3rd party Agent screen it is showing Avaya IP Office IP not the caller ID of PRI Trunk. Find below System status traces for the same and suggest.

    Line Service State: In Service
    Peer Domain Name: 192.168.42.250
    Resolved Address: 192.168.42.250
    Line Number: 17
    Number of Administered Channels: 20
    Number of Channels in Use: 2
    Administered Compression: G711 A, G711 Mu, G729 A, G7231
    Silence Suppression: Off
    Media Stream: RTP
    Layer 4 Protocol: UDP
    SIP Trunk Channel Licenses: 20
    SIP Trunk Channel Licenses in Use: 2
    SIP Device Features:

    Channel URI Call Current Time in Remote Media Codec Connection Caller ID or Other Party Direction Round Trip Receive Receive Packet Transmit Transmit Packet
    Number Group Ref State State Address Type Dialed Digits on Call of Call Delay Jitter Loss Fraction Jitter Loss Fraction
    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    1 1 51081 Connected 00:00:26 192.168.42.250 G711 A VCM 192.168.42.250 Line: 1 Slot: 1 Port: 1 Channel: 13 Incoming 4ms 1.2ms 0% 0ms 0%

    2 1 51083 Incoming Alerting 00:00:00 192.168.42.250 192.168.42.250 Line: 1 Slot: 1 Port: 1 Channel: 15 Incoming

    3 Idle 00:46:50


    Trace Output - All Channels:
    3/19/18 4:51:36 PM-086ms Line = 17, Channel = 1, SIP Message = Response, Direction = From Switch, From = 192.168.42.250, To = [email protected], Response = 100 Trying
    3/19/18 4:51:36 PM-087ms Line = 17, Channel = 1, SIP Message = Invite, Direction = To Switch, From = 192.168.42.250, To = [email protected]
    3/19/18 4:51:36 PM-092ms Call Ref = 51081, Short Code Matched = System, ?
    3/19/18 4:51:36 PM-096ms Call Ref = 51081, Originator State = Dialling, Type = Trunk, Destination Type = ARS Form
    3/19/18 4:51:36 PM-198ms Call Ref = 51081, Originator State = Dialling, Type = Trunk, Destination State = Dialling, Type = Trunk
    3/19/18 4:51:36 PM-666ms Line = 1, Channel = 13, Q.931 Message = Alerting, Call Ref = 51081, Direction = To Switch
    3/19/18 4:51:36 PM-667ms Call Ref = 51081, Alerting, Line = 1, Channel = 13
    3/19/18 4:51:36 PM-671ms Call Ref = 51081, Originator State = Incoming Alerting, Type = Trunk, Destination State = Outgoing Alerting, Type = Trunk
    3/19/18 4:51:36 PM-674ms Line = 17, Channel = 1, SIP Message = Response, Call Ref = 51081, Direction = From Switch, From = 192.168.42.250, To = [email protected], Response = 180 Ringing
    3/19/18 4:51:47 PM-516ms Line = 1, Channel = 13, Q.931 Message = Connect, Call Ref = 51081, Direction = To Switch
    3/19/18 4:51:47 PM-522ms Line = 17, Channel = 1, SIP Message = Response, Call Ref = 51081, Direction = From Switch, From = 192.168.42.250, To = [email protected], Response = 200 OK
    3/19/18 4:51:47 PM-527ms Line = 17, Channel = 1, SIP Message = Ack, Call Ref = 51081, Direction = To Switch, From = 192.168.42.250, To = [email protected]
    3/19/18 4:51:47 PM-529ms Call Ref = 51081, Originator State = Connected, Type = Trunk, Destination State = Connected, Type = Trunk
    3/19/18 4:51:47 PM-529ms Call Ref = 51081, Answered, Line = 1, Channel = 13
    3/19/18 4:51:48 PM-333ms Line = 17, Channel = 2, SIP Message = Response, Direction = From Switch, From = 192.168.42.250, To = [email protected], Response = 100 Trying
    3/19/18 4:51:48 PM-334ms Line = 17, Channel = 2, SIP Message = Invite, Direction = To Switch, From = 192.168.42.250, To = [email protected]
    3/19/18 4:51:48 PM-339ms Call Ref = 51082, Short Code Matched = System, ?
    3/19/18 4:51:48 PM-343ms Call Ref = 51082, Originator State = Dialling, Type = Trunk, Destination Type = ARS Form
    3/19/18 4:51:48 PM-494ms Call Ref = 51082, Originator State = Dialling, Type = Trunk, Destination State = Dialling, Type = Trunk
    3/19/18 4:51:49 PM-037ms Line = 1, Channel = 14, Q.931 Message = Alerting, Call Ref = 51082, Direction = To Switch
    3/19/18 4:51:49 PM-038ms Call Ref = 51082, Alerting, Line = 1, Channel = 14
    3/19/18 4:51:49 PM-042ms Call Ref = 51082, Originator State = Incoming Alerting, Type = Trunk, Destination State = Outgoing Alerting, Type = Trunk
    3/19/18 4:51:49 PM-046ms Line = 17, Channel = 2, SIP Message = Response, Call Ref = 51082, Direction = From Switch, From = 192.168.42.250, To = [email protected], Response = 180 Ringing
    3/19/18 4:51:51 PM-117ms Line = 1, Channel = 14, Q.931 Message = Disconnect, Call Ref = 51082, Direction = To Switch, Cause Code = 17
    3/19/18 4:51:51 PM-118ms Line = 1, Channel = 14, Q.931 Message = Release, Call Ref = 51082, Direction = From Switch
    3/19/18 4:51:51 PM-266ms Line = 1, Channel = 14, Q.931 Message = ReleaseComplete, Call Ref = 51082, Direction = To Switch
    3/19/18 4:51:51 PM-267ms Call Ref = 51082, Originator State = Incoming Alerting, Type = Trunk, Destination State = Clearing, Type = Trunk
    3/19/18 4:51:51 PM-267ms Call Ref = 51082, Disconnect from Destination End
    3/19/18 4:51:51 PM-272ms Line = 17, Channel = 2, SIP Message = Response, Direction = From Switch, From = 192.168.42.250, To = [email protected], Response = 486 Busy Here
    3/19/18 4:52:12 PM-956ms Line = 17, Channel = 2, SIP Message = Response, Direction = From Switch, From = 192.168.42.250, To = [email protected], Response = 100 Trying
    3/19/18 4:52:12 PM-958ms Line = 17, Channel = 2, SIP Message = Invite, Direction = To Switch, From = 192.168.42.250, To = [email protected]
    3/19/18 4:52:12 PM-962ms Call Ref = 51083, Short Code Matched = System, ?
    3/19/18 4:52:12 PM-966ms Call Ref = 51083, Originator State = Dialling, Type = Trunk, Destination Type = ARS Form
    3/19/18 4:52:13 PM-101ms Call Ref = 51083, Originator State = Dialling, Type = Trunk, Destination State = Dialling, Type = Trunk
    3/19/18 4:52:13 PM-779ms Line = 1, Channel = 15, Q.931 Message = Alerting, Call Ref = 51083, Direction = To Switch
    3/19/18 4:52:13 PM-780ms Call Ref = 51083, Alerting, Line = 1, Channel = 15
    3/19/18 4:52:13 PM-784ms Call Ref = 51083, Originator State = Incoming Alerting, Type = Trunk, Destination State = Outgoing Alerting, Type = Trunk
    3/19/18 4:52:13 PM-787ms Line = 17, Channel = 2, SIP Message = Response, Call Ref = 51083, Direction = From Switch, From = 192.168.42.250, To = [email protected], Response = 180 Ringing
  • regan16
    Hot Shot
    • Mar 2018
    • 16

    #2
    Have you ran any traces from the SBC? This would probably show a bit more of what was happening.

    Comment

    Loading